2 Replies Latest reply on Nov 18, 2011 4:40 AM by ankgoel

    java.lang.NoSuchMethodError: org.jboss.remoting.Client.connect(Lorg/jboss/remoting/ConnectionListener;Ljava/util/Map;)

    ankgoel
    ankgoel Nov 17, 2011 10:14 AM

      We have the following configuration -

      JBoss version is 4.2.3 GA

      JBoss messaging: 1.4.5 GA

      Remoting version: 2.2.3

       

      We are trying to consume JBoss JMS topic messages from Oracle iAS 10.1.3.5 using 3rd party configurations.

      We included the JBoss jars into Oracle iAS library. And we get the following exception -

       

      java.lang.NoSuchMethodError: org.jboss.remoting.Client.connect(Lorg/jboss/remoting/ConnectionListener;Ljava/util/Map;)V

      at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:374)

      at java.security.AccessController.doPrivileged(Native Method)

      at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:368)

      at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:165)

       

      I looked at jboss-messaging-client.jar and jbossall-client.jar for the classes involved in above exception. It seems the method connect(Lorg/jboss/remoting/ConnectionListener;Ljava/util/Map) is not available in Client.class which JMSRemotingConnection is trying to invoke !

       

      Is it an issue with JBoss jars not being compatible ?

      Do we have standars set of JBoss messaging jars to be used for Oracle iAS 10g.

       

      Thanks,

      Ankit

      • 2730 Views
      • Tags:
        • 1. Re: java.lang.NoSuchMethodError: org.jboss.remoting.Client.connect(Lorg/jboss/remoting/ConnectionListener;Ljava/util/Map;)
          ankgoel
          ankgoel Nov 17, 2011 11:48 AM (in response to ankgoel)

          We tried one thing - I put jboss-remoting.jar before jbossall-client.jar in the shared lib on SOA server. Now the below error is gone. These 2 jars have a common Client.class.

           

          But now another exception is coming -

           

          LeasePinger[a002u-e1x66y-gv3zkvyb-1-gv3zm6rv-f:SocketClientInvoker[79de1d, bisocket://WM9.chlcore.com:4657](a002u-e1x66y-gv3zkvyb-1-gv3zm6qx-e)] failed to ping to server

          java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is:

          java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment

          at org.jboss.remoting.transport.socket.SocketClientInvoker.handleException(SocketClientInvoker.java:131)

          at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.handleOtherException(MicroSocketClientInvoker.java:812)

          at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:725)

          at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:458)

          at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:143)

          at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:375)

          at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:177)

          at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:518)

          at org.jboss.remoting.Client.setupClientLease(Client.java:1923)

          at org.jboss.remoting.Client.connect(Client.java:1803)

          at org.jboss.remoting.Client.connect(Client.java:655)

          at org.jboss.jms.client.remoting.JMSRemotingConnection$1.run(JMSRemotingConnection.java:374)

            • Actions
          • 2. Re: java.lang.NoSuchMethodError: org.jboss.remoting.Client.connect(Lorg/jboss/remoting/ConnectionListener;Ljava/util/Map;)
            ankgoel
            ankgoel Nov 18, 2011 4:40 AM (in response to ankgoel)

            We also notice following logs on JBoss server -

             

            08:59:00,226 WARN  [Lease] Lease[61c6408d:a002u-x00g4y-gv4x0i5y-1-gv4yjc6m-im:a0

            02u-x00g4y-gv4x0i5y-1-gv4yjc7u-in] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4yjc6m-ik, but no collection of clients have been set.

            08:59:04,641 WARN  [Lease] Lease[5d1af4ba:a002u-x00g4y-gv4x0i5y-1-gv4yjfm5-iq:a0

            02u-x00g4y-gv4x0i5y-1-gv4yjfmc-ir] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4yjfm5-io, but no collection of clients have been set.

            08:59:30,665 WARN  [Lease] Lease[2a2b1ca9:a002u-x00g4y-gv4x0i5y-1-gv4yjzox-iu:a0

            02u-x00g4y-gv4x0i5y-1-gv4yjzpf-iv] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4yjzox-is, but no collection of clients have been set.

            09:00:01,091 WARN  [Lease] Lease[585515e7:a002u-x00g4y-gv4x0i5y-1-gv4ykmvg-iy:a0

            02u-x00g4y-gv4x0i5y-1-gv4ykmvo-iz] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4ykmvg-iw, but no collection of clients have been set.

            09:00:31,122 WARN  [Lease] Lease[3b372c26:a002u-x00g4y-gv4x0i5y-1-gv4ylacx-j2:a0

            02u-x00g4y-gv4x0i5y-1-gv4ylad2-j3] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4ylacx-j0, but no collection of clients have been set.

            09:01:01,143 WARN  [Lease] Lease[338d9133:a002u-x00g4y-gv4x0i5y-1-gv4ylxj1-j6:a0

            02u-x00g4y-gv4x0i5y-1-gv4ylxj6-j7] Tried to terminate lease for session id a002u

            -x00g4y-gv4x0i5y-1-gv4ylxj1-j4, but no collection of clients have been set.

             

            These logs come due to connection trials from SOA server only. If we stop SOA server, these messages do not come on JBoss logs. Looks to be an issue while reading message from the Jboss JMS topic.

             

            Thanks,

            Ankit

              • Actions