ConnectException in Webstart clients

We have a Swing client downloaded with Webstart that connects to a JBoss server.

At some locations the application runs just fine, at others the client hangs for several methods and then throws a java.rmi.ConnectException.

Any idea what's causing this?

Details:

* JBoss started with

-Djava.rmi.server.hostname=mail.fpc.be

-Djava.rmi.server.useLocalHostname=false

* Webstart JNLP has <property name="java.naming.provider.url" value="jnp://mail.fpc.be:1099"/>

* Full stacktrace:java.rmi.ConnectException: Connection refused to host: mail.fpc.be; nested exception is:

java.net.ConnectException: Connection timed out: connect

at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)

at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)

at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)

at sun.rmi.server.UnicastRef.invoke(Unknown Source)

at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)

at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)

at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:331)

at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:194)

at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61)

at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)

at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184)

at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)

at $Proxy1.create(Unknown Source)

at com.fpc.nokeos.core.client.security.NokeosClientSecurity.login(NokeosClientSecurity.java:58)

at com.fpc.nokeos.core.client.launch.Launcher.checkLogin(Launcher.java:193)

at com.fpc.nokeos.core.client.launch.Launcher.doLogin(Launcher.java:94)

at com.fpc.nokeos.core.client.launch.Launcher.main(Launcher.java:85)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.sun.javaws.Launcher.executeApplication(Unknown Source)

at com.sun.javaws.Launcher.executeMainClass(Unknown Source)

at com.sun.javaws.Launcher.continueLaunch(Unknown Source)

at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)

at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)

at com.sun.javaws.Launcher.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Caused by: java.net.ConnectException: Connection timed out: connect

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(Unknown Source)

at java.net.PlainSocketImpl.connectToAddress(Unknown Source)

at java.net.PlainSocketImpl.connect(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at java.net.Socket.<init>(Unknown Source)

at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)

at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)

... 28 more

[3501 byte] By [NickDGa] at [2007-10-3 3:51:14]
# 1

It's all there:

java.rmi.ConnectException: Connection refused to host: mail.fpc.be; nested exception is:

java.net.ConnectException: Connection timed out: connect

This means that mail.fpc.be didn't respond to the connection request within about 70 seconds. This would tend to suggest that either the host was down or the intermediate network had a fault.

ejpa at 2007-7-14 21:48:51 > top of Java-index,Core,Core APIs...
# 2
eevn i am facing the same problem....
Ravijia at 2007-7-14 21:48:51 > top of Java-index,Core,Core APIs...
# 3
The ISP at the location that can't connect has blocked the ports needed by JBoss. That was the cause of the timeout.
NickDGa at 2007-7-14 21:48:51 > top of Java-index,Core,Core APIs...