Talikng to Remote EJBs in 4.2.1 from 4.0.5

[gumnaam]

I have 2 jboss server instances , one is running 4.2.1, and has certain stateless session EJB3s.
The other is 4.0.5, which calls these SLSBs. The 4.0.5 has been installed using the JEMS installer, and selecting the EJB3 option. (so it has all the necessary ejb3 related jar files).

But when code running in 4.0.5 calls SLSBs in 4.2.1 I get the following exception trace.

javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.session.BaseSessionRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 8310915813626447181, local class serialVersionUID = 2609262789016232311]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:722)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at
....

If instead of 4.2.1 , I run 4.0.5 for the SLSBs , then every thing works perfectly.

I tried running 4.2.1 with -Djboss.remoting.pre_2_0_compatible=true & jboss.remoting.version=1 as per 4.2.x release notes, for compatibility between 4.2.x and 4.0.x, but no luck.

Any clues as to how I can make 4.0.5 ejb3 client talk to 4.2.x ejb3 ?

thanks

[lavh]

Did you resolve your problem?

I have the same problem.

I have an application running in jboss 4.0.4GA using EJB 3 and other application running in jboss 4.2.1GA using EJB3 too.

Tkz.

[wolfc]

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

[lavh]

I´d like to know when the 4.2.3 version will be available?

Tkz

[acefrehley]

I can confirm this solution. In my JBoss IDE, I had a 4.2.2 server installed. When I ran a JUnit test case to look up an EJB running inside the server, I received the same exception mentioned above. I then installed a version of the 4.2.3 server onto my local file system in a different directory. After this, I went into my IDE settings: Window -> Preferences -> Server -> Installed runtimes -> Edit -> and pointed the home directory to the 4.2.3 server. After the IDE resolved it's references to the new server path, I was able to run my JUnit test case successfully. (It goes without saying that I had to deploy my project as an ejb jar to the 4.2.3 server, and then start the 4.2.3 server before running the test case)