Timeouts until error notification

Yeah! With build number 245 the mystic ports have gone. Thanks a lot!

But now (sorry for that) another problem has arised regarding the host behind the second firewall. I try to explain the problematic situation:

The master ist running in a network A (172.26.0.0/16), the agent is running in another network B (10.136.98.0/24). So far so good.
To allow access from master to agent the two firewalls are configured with NAT's for the agent host from masters point of view.

Masters ip-view to the agent is 172.25.25.200 (this is a NAT'ed ip on the firewall which points to 10.136.98.249 (the real agent ip address).

The simple "telnet 172.25.25.200 10000" gets a connection (agent port configured is 10000). But then the agent seems to tell the master "hey, my ip is 10.136.98.249" (which is of course true from agents standpoint but not from masters standpoint). So I find the following message in the master's debug log:

2007-07-18 12:15:39,406 [AWT-EventQueue-0] DEBUG com.softtreetech.jscheduler.business.agent.remote.AgentServerImpl - testConnection
java.rmi.ConnectException: Connection refused to host: 10.136.98.249; nested exception is:
java.net.ConnectException: Connection timed out

although remote agent is of course configured with ip 172.25.25.200!

master --> firewall1 --> firewall2 (nat'ing 172.25.25.200 to 10.136.98.249 allowing port 10000) --> agent listening on 10000

From my point of view the master has to use the local DNS name and not the transferred (?) ip of the agent's listener
Is there a way to change this behavior? And please don't ask why we got such a complex infrastructure :-) It is as it is...

Thanks a lot in advance.

Hmmm... this could be a tuff case...

Try setting java.rmi.server.hostname property for the agent to make it resolve to the required IP address. This should help JVM which is exporting remote objects. In other words, modify agent startup command line (edit agent.bat or agent.sh depending on the host environment) and add -Djava.rmi.server.hostname=10.136.98.249

I think you meant -Djava.rmi.server.hostname=172.25.25.200 - this is the correct agent ip from master's standpoint.

But either I use this or that - this parameter seems to have no effect. The debug file still reads that it wants to connect to 10.136.98.249 and not 172.25.25.200..

But I had an idea on our own locally managed firewall1 : I added a NAT-rule that all packets to destination 10.136.98.249 are translated to destination 172.25.25.200 and voila - it's working! Not the smartest solution - but I can live with that.

Many thanks for your efforts!

Best regards
Joerg Redemann

Thanks for the update. Hope this works for you.