Have your speed issues been sorted out since 3.5.5? My server is now hosted, but i a still testing it, so the volume of users isnt that large, so i cannot really tell regarding its speed.
I take it the problem with rebooting the server from the admin console is not just me configuring it badly, is it the same with other?
The new version of Servoy (3.5.6) has a new tunnel implementation.
This implementation is now the same speed as plain RMI. Due to the built in bandwidth management though, sometimes the total time (start of first operation to end of last operation) of a group of operations is faster than with plain RMI, giving a smoother feel to the client.
Has the bug that doesnt let you restart the server from the web control panel been fixed in this release?
I think i posted here about it, it seemed to be related to the extra line of Java that had to be added to the bottom of the server.sh startup script on the mac which i think was necessary with the tunel
The tunnel should work fine without any modifications to servoy_server.sh.
In any case, it should not have any affect on restartability of the server from the admin pages. If it still does, the best thing to do is from the command prompt run:
servoy_server.sh 1> mylogfile 2> mylogfile
and then restart from the admin pages and see if there is any info in mylogfile (if you post it here, I will have a look at it). If you are using a csh related shell, use
servoy_server.sh >& mylogfile
instead.
Again, it should all work just fine, but just in case there is a problem I’m sure we can sort it out!
Yes, I would definitely use a fresh install. While it is possible to run from a 3.5.5 and update and possibly change a few config files manually, I think to avoid problems a fresh install is better!
I am confident that the problems are gone: internally at Servoy we’ve been using the new tunnel for several weeks now, and all is going smoothly.
I have done a fresh install and made those changes.
I am on OS X 10.5.3
Basically the server continues to start but remains on Port 8080, not port 80.
I am thinking that i am just missing something that i need to change to Port 80?
if I go to server.xml and change the following to Port 80 then it appears to then work on Port 80. I must therefore assume that this makes the tunnel work, its just a matter of continuing to manual change the Port that remains and not the unchecking of other lines?
Define a non-SSL HTTP/1.1 Connector on port 8080
-->
<Connector port="80"
protocol="HTTP/1.1"
maxThreads="400" connectionTimeout="60000"
redirectPort="8443" />
Sorry for hassling you, I am just keen to get rid of my increasing firewall issues
The port does not matter for the tunnel. If you want to run the tunnel on port 80, then you have to make tomcat run on port 80 (as you did above). Otherwise the tunnel will simply work on port 8080.
To enable the tunnel you need to add the following line to your servoy.properties:
If you are running tomcat behind apache you need to use mod_proxy with AJP (and the flushpackets=on option), otherwise the connection will not work properly.
Finally, you shouldn’t post your encrypted passwords in a public location unless you have your own private/public keypair in the keystore (and you are not using the default ones).
If you have any other questions, don’t hesitate to ask!
Normally you would configure your webserver to proxy requests for the tomcat which is embedded in Servoy. Note that if you have a webserver running in front of tomcat it is in general not necessary to change the port of the tomcat to 80, because you can just as easily proxy to 8080.
When proxying it is important that the proxy does not buffer. When using apache + mod_proxy this means that you have to use AJP with the flushpackets on option. To be specific, in apache you would need something like this: