My Http Tunnels don’t work anymore after upgrading to Servoy 5.0 final. Is tunneling still supported in current version or there’s another way to achieve the same effect?
Have used the same guidelines such as:
To enable the Servoy HTTP Tunnel option on Windows / Linux / Unix:
Open /server/conf/server.xml.
Change the connector protocol as described at the top of the file.
(You might wish to change the port number as well.)
Open /server/webapps/ROOT/WEB-INF/web.xml
Uncomment the two blocks labeled tunnel servlet
(located at the top of the document and also halfway down).
Open /servoy.properties and add the following command line:
SocketFactory.rmiServerFactory=com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory
[Re]start Servoy.
You can enable tunneling by setting the SocketFactory.rmiServerFactory on the admin page (under Network Settings) to “com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory”.
No need to alter anything in properties or config files.
This didn’t help, at least for now - my XXX.jnlp files open only to blank pages,that is,after enabling SocketFactory.rmiServerFactory under my Admin-page-Network-Settings-pages with “com.servoy.j2db.server.rmi.tunnel.ServerTunnelRMISocketFactoryFactory”. The blank pages only have the 3 menu items, File,Edit and Help active.
There are also no traceable error(s) thereafter on the Admin-page-Server-log-page.
So servoy.allowSolutionBrowsing has to be set to “true” to allow HTTP -tunneling on Servoy 5.0 final.
Holy Kaw, our Servoy-clients work fine once again .
Last question, when are the Servoy 5.0 final Server-Admin-Guide(docs) going to be available?
I couldn’t find the above Http-tunneling’s settings anywhere documented apart from this thread.
bobpee:
I couldn’t find the above Http-tunneling’s settings anywhere documented apart from this thread
do you mean the ‘servoy.allowSolutionBrowsing’ settting?
This doesn’t have anything to do with tunneling. This is simply a bug in 5.0.0 final, that will be fixed in 5.0.1.
The tunnel settings are to be found under the “?” button in the servoy admin pages, that’s all you need for the guide…
mboegem:
do you mean the ‘servoy.allowSolutionBrowsing’ settting?
This doesn’t have anything to do with tunneling. This is simply a bug in 5.0.0 final, that will be fixed in 5.0.1.
The tunnel settings are to be found under the “?” button in the servoy admin pages, that’s all you need for the guide…
Then I was right after all - I landed a “bug”!
We had no issues with http-tunneling even in Servoy 5.0 RC3.
Sorry Guys, my http-tunneling issue is not yet over.
The first tests that I made after following Paul’s directions (and Marc’s), were made on local servers, running within my LAN - these worked fine.
I have done a similar settings on a remote server, restarted it and, when I try to access that server per servoy-client (like http://mydomain/servoy-client/XXX.jnlp ),
The servoy-client starts and then I do get the following error msg.:
“Cannot find dataservice, it may not be running on server”
or
“Kan geen verbinding maken met dataservice op server” in Dutch
FYI, the firewall settings on my remote server has not change - and this allows http-tunneling when running Servoy 4.1.3.
Do I need some more settings on the server’s admin-page?
@Robert
We’re using Sybase and it is running as a service. We are also able to access our remote solution per servoy-webclient. It is the servoy-client which doesn’t kick-in.
4.1.4 and 5.0 do have pretty much exactly the same code for tunneling.
So are you saying that in exactly the same setup the latest version of 4.1.x does work for you but 5.0 doesnt?
What you can play with is the rmi hostname, is that filled in? Try just 127.0.0.1 or the outside public dns name of your server. (the same thing you type in your browser)
else what it could be is that there are firewalls or proxies in between the client and the server that are somehow blocking the tunnel.
jcompagner:
4.1.4 and 5.0 do have pretty much exactly the same code for tunneling.
So are you saying that in exactly the same setup the latest version of 4.1.x does work for you but 5.0 doesnt?
That’s right, in the same setup and, running Servoy 4.1.3 server and using the old http-tunneling setting.
jcompagner:
What you can play with is the rmi hostname, is that filled in? Try just 127.0.0.1 or the outside public dns name of your server. (the same thing you type in your browser)
The rmi hostname was already filled in with the default 127.0.0.1 on installing the server 5.0 - this is what throws the “Cannot find dataservice, it may not be running on server” error . I have changed the hostname to my public dns server name, saved setting and restarted the AS - I get the same error.
jcompagner:
else what it could be is that there are firewalls or proxies in between the client and the server that are somehow blocking the tunnel.
For this particular remote installation we don’t use proxies - there’s a firewall alright, but it is a non NAPT/NAT firewall.
even in 4.1.3 we dont ship the old tunnel code. Thats really old code that isnt used for quite some time
Are you sure that you only have altered the new setting? (so only set the rmi factory? and nothing more? so no other configuration file changes)?
But i dont know what currently goes wrong in your setup if a local network setup works fine.
do you have an url where we can connect on to see what goes wrong?
jcompagner:
Are you sure that you only have altered the new setting? (so only set the rmi factory? and nothing more? so no other configuration file changes)?
That is right, we haven’t change any other setting apart from the rmi factory setting and, then setting the “servoy.allowSolutionBrowsing” to true on the admin page, even though I understand this last setting has nothing to do with the tunnel setting.
jcompagner:
But i dont know what currently goes wrong in your setup if a local network setup works fine.
do you have an url where we can connect on to see what goes wrong?
Yes, I am sending you urls to 2 remote servers, one running Servoy 4.1.3 and the other Servoy 5.0 final
jcompagner:
It could be an some ssl problem can you check it with and without it enabled?
I have just tried that: disable the SocketFactory.useSSL on the “Network Settings Howto” page,saved setting and restarted the AS.
Remote http-tunnel access to this server (that is server running Servoy 5.0 final) after disabling SocketFactory.useSSL throws a “You are disconnected from server. Trying to reconnect” dialogue when the servoy-client is started , followed by a series of “The client could not be registered” error dialogues.
As you may have already verified, the same firewall setup with 2 different server versions (vers. 4.1.3 and 5.0 final) running behind it. As mentioned earlier remote tunnel to the server 4.1.3 works fine whilst a similar tunnel access to the server 5.o final doesn’t.
FYI, you may use the same login details I sent earlier on to access the servoy-admin pages of the 2 different servoy installations for further investigation.
I have meanwhile filed case 259928 in the support system, nevertheless, if there’re other parameters that you’d like me to verify on our remote machines, pls. let me know.
I am following your problem, because I’m surprised…
I just activated a fresh 5.0 install WITH http-tunneling enabled and there was not the smallest problem.
The only extra thing I changed was setting an extra port to connect to (port 80) by extending the server.xml file with