-
1. Re:
peterj Jan 10, 2007 5:16 PM (in response to cjlogan)Are you getting any errors on the server? I got this same error yesterday on the client, and it was in response to an error on the server (in my case I was setting up SSL, and had misconfigured one of the remoting mbeans). Fixing the problem on the server solved thep roblem.
-
2. Re:
cjlogan Jan 10, 2007 5:30 PM (in response to cjlogan)Yes, this is the error that I am getting on the remote server:
2007-01-10 16:36:30,699 ERROR [org.jboss.remoting.transport.socket.ServerThread] failed to process invocation.
java.io.IOException: Can not read data for version 3. Supported versions: 1,2
at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:383)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:435)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:516)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:253)
I am suspecting that I need to created a scoped EAR as specified in Ovidiu's document http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMessagingUser_Deploying_a_scoped_MDB_container
Currently, I am including the jboss-messaging-client.jar in my EAR (in which the client is running). -
3. Re:
ovidiu.feodorov Jan 28, 2007 12:38 AM (in response to cjlogan)A messaging installation on any 4.0.x server HAS to be scoped, because we're using newer (and unfortunately, incompatible) dependecies. There is no way around this.
This situation will be corrected in 4.2 and 5.0, where we will keep our dependencies in sync.
And btw, why are you using CR3? That's an ancient version ...