[jboss-user] [JBoss Messaging] - Re: Remote JMS server

jeanbobby do-not-reply at jboss.com
Tue Oct 31 10:48:04 EST 2006


Hi guys,

Im trying to setup a remote-standalone JBossMessaging 1.1 Instance.
The 'hosting' standalone server is 4.0.4.GA.

The client(s) are 4.0.4.GAs, with the jms RAR and jms-ds defined as indicated in the remote-messaging wiki.

I want my applications to be able to send/receive msgs first 'programatically',  and maybe later with 3.0 MDBs.

My main application is a spring-based war, for my tests it intializes a simple bean injecting a jms template which is based on the JmsXA bound in the private internal namespace.

when sending the test message I first got classpath pbs, included messaging-client to server/myserver/lib,  and then got into :

java.lang.RuntimeException: Failed to config client side AOP
  | 
  | 15:43:39,643 ERROR [SocketClientInvoker] Got marshalling exception, exiting
  | java.io.EOFException
  |         at java.io.DataInputStream.readByte(DataInputStream.java:243)
  |         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.jav
  | a:279)
  |         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)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.invoke(ClientConnectionFact
  | oryDelegate.java:199)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$getClientAOPConfig_86975327
  | 01842707646.invokeNext(ClientConnectionFactoryDelegate$getClientAOPConfig_8697532701842707646.java)
  |         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.getClientAOPConfig(ClientCo
  | nnectionFactoryDelegate.java)
  |         at org.jboss.jms.client.JBossConnectionFactory.ensureAOPConfigLoaded(JBossConnectionFactory.
  | java:233)
  |         at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFacto
  | ry.java:196)
  |         at org.jboss.jms.client.JBossConnectionFactory.createXAQueueConnection(JBossConnectionFactor
  | y.java:144)
  |         at org.jboss.jms.ConnectionFactoryHelper.createQueueConnection(ConnectionFactoryHelper.java:
  | 147)
  |         at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:709)
  |         at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:184)
  | 
  |         at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsMan
  | agedConnectionFactory.java:106)
  |         at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventL
  | istener(InternalManagedConnectionPool.java:539)
  |         at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(Internal
  | ManagedConnectionPool.java:228)
  |         at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JB
  | ossManagedConnectionPool.java:417)
  |         at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConn
  | ectionManager2.java:324)
  |         at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectio
  | nManager.java:301)
  |         at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnec
  | tionManager2.java:379)
  |         at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.alloca
  | teConnection(BaseConnectionManager2.java:812)
  |         at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactory
  | Impl.java:389)
  |         at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactory
  | Impl.java:144)
  |         at org.springframework.jms.core.JmsTemplate102.createSession(JmsTemplate102.java:166)
  |         at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:424)
  |         at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:486)
  |         at com.digiplug.repository.JmsTest.afterPropertiesSet(JmsTest.java:27)


On the client and on the messaging server :

15:58:00,611 ERROR [ServerThread] failed to process invocation.
  | java.io.IOException: Can not read data for version 6.  Supported versions: 1,2
  |         at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:394)
  |         at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:446)
  | 
  |         at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527)
  |         at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261)


which seems to show a conflict between jboss-remoting versions between client and server... but I saw no directive concerning jboss-remoting in the wiki.

Any help would be appreciated,
Best Regards

Olivier Cuzacq

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982116#3982116

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982116



More information about the jboss-user mailing list