Hello all,
I am having a rather major issue with the webstart servoy client and servoy server – clients cannot load solutions.
I have done the following:
downloaded Servoy 2.1.2 installer, installed locally
configured this install with the repository as a Sybase database using the iAnywhere server provided with Servoy
configured PostgreSQL on the remote server (angua) which holds the database for the solution, specifically created a new user, then locally dumped the db and restored it to angua
tested the solution locally to make sure it works
copied the entire servoy directory to the remote server
From within the Servoy directory, I try to run the servoy_server.sh shell script, however it fails with connection refused. I then “export LD_LIBRARY_PATH=sybase_db” and start Sybase with “sybase_db/dbsrv9 @sybase_db/sybase.config”; then I can successfully run servoy_server.sh, which starts as it should do.
I can connect fine to http://server:8080/servoy-admin/, and I get the Servoy client splash screen that links to a .jnlp file at http://server:8080. But once the jar files have downloaded, Servoy client opens, and freezes at “Opening Solution”; the ‘progress bouncer’ at the bottom right of the window freezes, if I cover the Servoy client window it isn’t redrawn after uncovering, and it eventually closes after popping up a dialog saying “Could not register client”.
I have tried the following to fix it:
on the server, changing the two-way-sockets and SSL settings on the network-settings page of servoy-admin, as well as changing the RMI server hostname to the main internet-facing IP of the server, 127.0.0.1, and leaving it blank
telnetting to port 1099 on the server; the connection is established, then closed after about five seconds
emptying the java webstart cache
pulling out large clumps of hair
Nothing seems to be working for me.
However, I also cannot run the demo.servoy.com:8080 solution; the exact same thing happens, it freezes at the Opening Solution stage.
I am behind a NAT which allows me to make any outgoing connections. However, someone who is directly connected to the net can connect and open the solution successfully. Unfortunately, this is not the person that the solution is written for. Also, the remote server is not running another instance of tomcat.
Any suggestions?
Thanks,
lee