If the Client has connected to other Servoy Servers in the past it would be a good idea to get rid of old servoy-client.properties files that are no longer needed. Have a client on OSX and seems to cure problem for him
As I understand it, Servoy runs Webstart and client download and update and initiating client over http using port 8080.
Once the client is downloaded and starts up it then uses RMI through port 1099 to connect to the server.
RMI is the communications method between client and server which will not run unless port 1099 is open on the firewall - and, yes, this means that it will not find the repository if it isn’t open as the request sent will not reach the server !
Also this does assume that it is using the default port of 1099 as you can change it if required
Harry Catharell:
Once the client is downloaded and starts up it then uses RMI through port 1099 to connect to the server.
RMI is the communications method between client and server which will not run unless port 1099 is open on the firewall - and, yes, this means that it will not find the repository if it isn’t open as the request sent will not reach the server !
What is confusing is that I can connect with Developer the same repository… so if 1099 is blocked, does that mean Developer is using a different port?
grahamg:
If the Client has connected to other Servoy Servers in the past it would be a good idea to get rid of old servoy-client.properties files that are no longer needed.
I assume that developer is working with the backend database(s) via JDBC using the standard ports per DBMS - and this includes interaction with the repository.
So Sybase is port 2638, MySQl is port 3306 etc etc