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)