Timeout looking up jms/RemoteConnectionFactory
Hi
I have a small client program connecting to a Wildfly 8.2 message queue and sending messages, this all works perfectly!
Now I have a memory leak somewhere (yes I know), and I am therefore starting wildly using a profiler, this also works!
But I need to send the messages to trigger the memory leak and when wildfly is running with the profiler I get this exception:
Caught: javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://localhost:8000 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS]
javax.naming.CommunicationException: Failed to connect to any server. Servers tried: [http-remoting://localhost:8000 (Operation failed with status WAITING after 5000 MILLISECONDS)] [Root exception is java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS]
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:240)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingStore(HaRemoteNamingStore.java:149)
at org.jboss.naming.remote.client.HaRemoteNamingStore.namingOperation(HaRemoteNamingStore.java:130)
at org.jboss.naming.remote.client.HaRemoteNamingStore.lookup(HaRemoteNamingStore.java:272)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:87)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:129)
at switch_on_switch_off.run(switch_on_switch_off.groovy:57)
Caused by: java.net.ConnectException: Operation failed with status WAITING after 5000 MILLISECONDS
at org.jboss.naming.remote.protocol.IoFutureHelper.get(IoFutureHelper.java:97)
at org.jboss.naming.remote.client.HaRemoteNamingStore.failOverSequence(HaRemoteNamingStore.java:198)
... 6 more
I expect it to be a simple case of Wildfly simply responding slower because of the profiler, so my question is where can I change this 5000 msec timeout?
I'm guessing it is configurable somehow in my InitialContext properties which by the way look like this:
properties.put(Context.URL_PKG_PREFIXES, "org.jboss.ejb.client.naming");
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
properties.put(Context.PROVIDER_URL, "http-remoting://localhost:8000");
properties.put(Context.SECURITY_PRINCIPAL, "abc");
properties.put(Context.SECURITY_CREDENTIALS, "123");
Hope some of you guys have the insight
Best
Søren
