sending to message-queue from external client fails
greeneagle Sep 18, 2008 9:03 AMHello,
I use jbossas 4.2.3 with jboss-messaging 1.4.0.SP3-CP02 and I have the following problem:
For testing-purposes i connect to message-queue with an external client (on same machine) I run from inside eclipse. Up to now I have used jbossmq and with jbossmq this worked fine.
With jboss-messaging I get an error on the server side
ERROR [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] received new control socket for unrecognized listenerId: 3j011-lx8qkq-fl83c2tx-1-fl83c3i8-9
and an exception on the client-side
org.jboss.jms.exception.MessagingNetworkFailureException at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:245) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:187) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81) at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205) at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:87) at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:82) at com.abc.ejb.processor.MessagingClient.doJms(MessagingClient.java:59) at com.abc.ejb.processor.MessagingClient.main(MessagingClient.java:68) Caused by: org.jboss.remoting.ConnectionFailedException: Timed out trying to create control socket at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.handleConnect(BisocketClientInvoker.java:272) at org.jboss.remoting.MicroRemoteClientInvoker.connect(MicroRemoteClientInvoker.java:242) at org.jboss.remoting.Client.connect(Client.java:1522) at org.jboss.remoting.Client.connect(Client.java:462) at org.jboss.remoting.callback.ServerInvokerCallbackHandler.connect(ServerInvokerCallbackHandler.java:161) at org.jboss.remoting.ServerInvoker.getCallbackHandler(ServerInvoker.java:1799) at org.jboss.remoting.ServerInvoker.handleInternalInvocation(ServerInvoker.java:1433) at org.jboss.remoting.transport.bisocket.BisocketServerInvoker.handleInternalInvocation(BisocketServerInvoker.java:641) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:796) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.addCallbackListener(Client.java:1619) at org.jboss.remoting.Client.addListener(Client.java:913) at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:230) at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:340) at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154) ... 10 more
The problem seems very low-level to me....
My first idea was, that maybe jar-version on server and client are different but that is not the case.
When I connect to message-queue from inside jboss (with same JNDI-properties) everything works fine.
Does anyone have an idea?
Regards,
Michael