We just did.
Disabling the compress option we have been able to connect: BUT ONLY from the developer on the server, not from the rest.
So the only way to work is through remote sessions on the server…
that is very weird, if you disable compressing in both dev and server then there is not really a change in the network layer
and you say that developers that are local can connect but others cant? That looks a lot then that something else is blocking stuff between those
because if localhost’:1099 works for a local developer why shouldnt ip:1099 fail for a remote one?
jcompagner:
That looks a lot then that something else is blocking stuff between those
because if localhost’:1099 works for a local developer why shouldnt ip:1099 fail for a remote one?
Moving back to Servoy 3.5.9 works fine.
I don´t really understand what’s the deal with ip:1099 and 3.5.10…
we have upgraded the multi-dev server to 3.5.10 and upgraded the developers to 3.5.10
(licenses are oke, multidev option is set)
we un-selected the compress option, and can’t start a remote developer. (on the same LAN)
we CAN start java webstart client over the same RMI port!!
the company where this is, is using proxy servers, but we by-passes this, with all java on: direct connection.
Downgrading to Servoy 3.5.9 works out of the box…
if you de-select the compress option in multideveloper admin-page, than afterwards, you have to SHUTDOWN the server first (and not just restart)
than the compress option is really written to the property file and seen by remote developers…