3 Replies Latest reply on Nov 16, 2007 6:18 AM by wolfc

jbossall-client.jar incompatible between 421 and 422

herculesx Nov 16, 2007 3:20 AM

I have an stateless EJB3 deployed in jboss-4.2.2GA, when I use jbossall-client.jar from jboss-4.2.1 to call this EJB, then I found:

javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.remoting.BaseRemoteProxy; local class incompatible: stream classdesc serialVersionUID = -2711693270411201590, local class serialVersionUID = 1126421850898582900]
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:724)
 at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
 at javax.naming.InitialContext.lookup(InitialContext.java:351)
......

After I replaced the jbossall-client.jar with jboss-4.2.2, it works fine. And I tested the case for call jboss-4.2.1 EJB3 by jbossall-client.jar from jboss-4.2.2, the same exception occured.
My question is, I need to make EJB3 call for two version of jbossAS in one Application, is that possible to use a single jbossall-client.jar?

1. Re: jbossall-client.jar incompatible between 421 and 422

itsme Nov 16, 2007 5:24 AM (in response to herculesx)

You can try to use the newer jars within the old jboss as by copying these jars to the old jboss as lib dir.
The conflict comes from compiling the sources for each appserver release (see serialVersionUID).

Regards
\sandor\
Actions
2. Re: jbossall-client.jar incompatible between 421 and 422

herculesx Nov 16, 2007 5:41 AM (in response to herculesx)

Thanks to sandor, but I can not modify the files in the 2 AS. What I need is making a client to call them, and I don't know how can achieve this by a single jbossall-client.jar. If I use older clientjar, I can't call newer EJB, and failed to call older EJB by newer client jar. :-(
Actions
3. Re: jbossall-client.jar incompatible between 421 and 422

wolfc Nov 16, 2007 6:18 AM (in response to herculesx)

http://jira.jboss.com/jira/browse/EJBTHREE-1118
Actions

Go to original post