2 Replies Latest reply on Feb 1, 2008 6:10 AM by jaikiran

    org.jboss.ejb3.remoting.BaseRemoteProxy serialid exception

    ycindepalle

      Hello

      I am deploying my application in jboss 4.2.2GA version. The application accesses ejb services from another application deployed in jboss 405.

      I tried using the jboss 405 ejb lib jars along with the deployment.(jboss-annotations-ejb3.jar, jboss-ejb3-client.jar, jboss-ejb3x.jar)

      I am getting the following exception when deploying my application.

      ==========================
      org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityManager' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Cannot resolve reference to bean 'securityServiceRemote' while setting bean property 'securityServiceRemote'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityServiceRemote' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.remoting.BaseRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 1126421850898582900, local class serialVersionUID = -2711693270411201590]
      Caused by:
      org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'securityServiceRemote' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.remoting.BaseRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 1126421850898582900, local class serialVersionUID = -2711693270411201590]
      Caused by:
      javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.remoting.BaseRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 1126421850898582900, local class serialVersionUID = -2711693270411201590]
      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 org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:123)
      at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
      at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
      at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
      at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:93)
      at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:105)
      at org.springframework.jndi.JndiObjectFactoryBean.lookupWithFallback(JndiObjectFactoryBean.java:197)
      at org.springframework.jndi.JndiObjectFactoryBean.afterPropertiesSet(JndiObjectFactoryBean.java:184)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1198)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1167)
      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:427)
      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:249)

      ====================


      Any help is greatly appreciated. I see some issues with this serialid in the bugs list and looks like they are fixed but i am unable to proceed.

      thanks very much in advance
      Yugandhar

        • 1. Re: org.jboss.ejb3.remoting.BaseRemoteProxy serialid excepti
          jimmycallaghan

          We're getting an identical error when an application deployed on JBoss422 tries to get a remote interface to an ejb that's deployed on JBoss404. I suspect that there has been a change in the org.jboss.ejb3.remoting.BaseRemoteProxy. We have an isolated class loader as default on our JBoss servers and if we put the jboss-ejb3-client.jar that is deployed on JBoss404 into the ear that is deployed on JBoss422 we no longer get the error.

          However, now we can't access 422 specific classes and get "JBossProxy not visible from the classloader" errors when trying to access the objects on the 422 server.

          It would seem that if you want to move from JBoss404 to 422, you will need to update ALL of the servers at the same time because of these incompatibilities.

          There doesn't seem to be any problem with using remote queues however.

          If anyone out there can tell me I'm wrong I'd be most pleased to know because for now I'm going to have to revert those servers running on 422 back to 404 until we can upgrade all at once.

          Thanks JBoss.