But the exception is that it cant connect to that port on the server.
Can you telnet to it from that client? or can you telnet to 1099 on the server itself to its own port?
It is not a login error it fails much earlier at creating the connection to the server.
Good point.
On further investigation, there’s nothing listening on 1099
netstat -tlpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN 2499/nrpe
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN 2357/mysqld
tcp 0 0 0.0.0.0:2638 0.0.0.0:* LISTEN 14731/dbsrv10
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 2267/vsftpd
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 2412/postmaster
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2571/master
tcp 0 0 :::993 :::* LISTEN 798/imap-login
tcp 0 0 :::995 :::* LISTEN 767/pop3-login
tcp 0 0 :::2638 :::* LISTEN 14731/dbsrv10
tcp 0 0 :::110 :::* LISTEN 767/pop3-login
tcp 0 0 :::143 :::* LISTEN 798/imap-login
tcp 0 0 :::8080 :::* LISTEN 10187/java
tcp 0 0 :::80 :::* LISTEN 300/httpd
tcp 0 0 :::22 :::* LISTEN 2195/sshd
tcp 0 0 :::443 :::* LISTEN 10187/java
I think I’m missing something basic. I have servoy_server and dbsrv10 running on the remote site. What else?
An application server should also startup RMI and it does that default on port 1099
in servoy-admin/network-settings you can see the start port where it will begins with. (if that fails it will try +1 and so on)
then the server should also listen on 1099 (if it isnt blocked by something else on that port)
Does the log of the server tell you anything?
It also could be ssl. Can you try without ssl? Or even without 2 way socket? (then set the rmi host name to the servers own ip)
Hi
I am the network engineer who helped set this up and I can confirm that we are using HTTP-tunnel config becuase using non-standard ports (ie anything other than 80 and/or 443) causes us huge ammounts of grief in supporting clients through various firewalls. http-tunnel has overcome all those problems and works perfectly but I have just read (p 314 in servoy-admin manual) that http-tunnel is not supported for developer
Will this be changed? It really lowers the value of http-tunnel (which is great!) if we can’t use it when connecting developer to remote solutions.
Any thoughts when this might happen?
Thanks
Al.
this is already supported with 4.0 developer if you just use SVN as your team provider.
Then the checkout just goes over http(s)/webdav
For other kinds of setups this is not likely to be changed/supported
jcompagner:
this is already supported with 4.0 developer if you just use SVN as your team provider.Then the checkout just goes over http(s)/webdav
For other kinds of setups this is not likely to be changed/supported
So, if I’ve got this right, a single developer working on a remote server who wants to use HTTP-tunnel config to get through firewalls can’t use Eclipse to develop on that server, unless they go to the trouble of installing SVN. Having read this post http://forum.servoy.com/viewtopic.php?f=38&t=11897 I’m hesitant to try
what do you mean with a single developer?
you mean 1 developer from a team that works outside and the rest of the team inside?
for bigger teams you should really go to svn, there are many people working with svn (me included)
And it works fine. it has way more better pro features like merging of “semi” conflicts and so on.
Thanks Johan, I mean 1 developer working alone, who doesn’t need SVN. I just want to know if it’s possible to connect from Servoy 4/Eclipse on a local machine to the repository on the remote server, to checkout solutions. It must be a reasonably common scenario. The remote is using tunneling and from the above posts, it sounds like the only workaround is to install SVN. This seems like a bit of overkill.
if you are just 1 developer why not keep the repo local?
Or check it out when you have access to it (when you are on the internal network)
You dont have to have a connection to it constantly so you could sync up in at other times
Thanks Johan, I guess I’m looking for advice on the best and easiest way to do this.
What I want to avoid is developing locally, exporting to a .servoy file, importing that to the remote server via servoy-admin.
I was hoping that I could connect directly to the remote repository, create a new release there, develop on that with Eclipse, then when it’s ready just activate it.
Grateful if you could outline the best practice for someone in my shoes.
you shouldnt mix production with development.
Those are 2 different things.
Also, I work from a couple of different places, so there’s an advantage in having the repository on a remote server rather than on my desktop computer.
jcompagner:
you shouldnt mix production with development.
Ok, but there are times when one might need to make a minor change to a form on the production site. One of the attractions of servoy is the ability to roll back a solution to release n-1, make changes to release n, then roll it forward. If the server was in house this is what I’d do. I’d like that ability on the remote repository.
Possible?
and if I tuned off tunneling on the remote, I probably could do it.
But then we;d lose the advantages of tunneling
