0 Replies Latest reply on Jan 11, 2012 9:48 AM by max Shestopalov

    unable to call EJB3 services in 4.0.5 installation from 5.1

    max Shestopalov Newbie

      Hi,

       

      For a while we had 2 instances of 4.0.5 running where instance A was calling EJB services of instance B. We upgraded instance A to 5.1 and at that point started getting the InvokationException with the serial number mismatch between classes in the 2 different versions of jbossas-client.jar.

       

      After doing a little research I started bringing up instance A with the property -Djboss.remoting.pre_2_0_compatible=true and the error I started seeing was

       

      java.lang.Exception: Can not make remoting client invocation due to

      not being connected to server.

             org.jboss.remoting.Client.invoke(Client.java:1729)

             org.jboss.remoting.Client.invoke(Client.java:629)

             org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55)

             org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

             org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61)

             org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

             org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)

             org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

             org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)

             org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)

             org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)

             $Proxy351.searchForExperiments(Unknown Source)

             gov.nih.nci.caintegrator2.external.caarray.CaArrayUtils.getExperiment(CaArrayUtils.java:168)

       

      When I googled this I found a seemingly helpful thread speaking about

      the new req in remoting 2.x that connect() be called before invoke()

      and how this did not use to be required in remoting 1.x

       

      here is the thread: http://community.jboss.org/message/368917#368917

       

      but I actually can't figure out how we are doing this since

      we aren't writing a client and invoking from the container.

       

      also, fyi, as a test upgrading instance B to 5.1 as well... everything works fine.

       

      Any help would be greatly appreciated.