Cannot connect to JMS from Service MBean

[chipschoch]

I have a service that uses JMS and I have tested it stand alone and it works fine. However, when I wrapped it in the StandardMBean interface and deploy it, it loads and begins to execute. Then I get an exception when it calls ConnectionFactory.createConnection(). Part of the stack:

java.io.IOException: Can not read data for version 4. Supported versions: 1,2
at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:387)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:439)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:520)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:257)
13:14:11,559 ERROR [SocketClientInvoker] Got marshalling exception, exiting
java.io.EOFException
at java.io.DataInputStream.readByte(Unknown Source)
at org.jboss.serial.io.JBossObjectInputStream.readByte(JBossObjectInputStream.java:227)
at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:411)
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)

also:

13:14:11,606 ERROR [JBossConnectionFactory] Failed to config client side AOP
java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:
java.io.EOFException
at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
at org.jboss.remoting.Client.invoke(Client.java:525)
at org.jboss.remoting.Client.invoke(Client.java:488)

Any ideas anyone? I don't even know what this means. I am using JBoss Messaging 1.01 CR4.

[ovidiu.feodorov]

Deploy your service in the same classloading domain as Messaging:

 <loader-repository>jboss.messaging:loader=ScopedLoaderRepository
 <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
 </loader-repository>

[oleznew]

Hi,

did this work? I have the same error messages when deploying a sar in deploy.last. I used the loader-repository tag as described by ovidiu. Does not work. What else could I try?

[ovidiu.feodorov]

Can you please attach your deployment descriptors, your deployment archive's topology, and the error message you're getting?

[kazama2002uk]

Hello,
I have a similar problem. I cannot attach my topology as it is highly sensitive.

I have 2 servers, a jboss-mq server and a jboss-messaging server. I deploy an EAR in the JBOSS-MQ server which should connect to the queues on the Jboss Messaging server. I already have the same configurations you have suggested but I have the same problem.