Problem in Calling Weblogic 8.1 EJB from a standalone client

Discussions

EJB programming & troubleshooting: Problem in Calling Weblogic 8.1 EJB from a standalone client

  1. Hi,
         I am facing a strange problem the below given is the exception. when i try to call a EJB which is deployed in the weblogic 8.1 from a stand allone client this is the exception I am getting. The server is running on the sun vertual machine not on "jrockit". Can anybody tell me what excatly the problem and solution.

    Thanks in advance.

    Ashok.
    ------------------------------------------------------------
    weblogic.rjvm.PeerGoneException: ; nested exception is:
    java.io.EOFException
    at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at com.polaris.orbionecore.facade.charges.calculator.ChargesCalculator_re93ww_EOImpl_813_WLStub.getCharges(Unknown Source)
    at SampleStub.main(SampleStub.java:82)
    Caused by: java.io.EOFException
    at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:856)
    at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:563)
    at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:513)
    at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:671)
    at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:618)
    at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:282)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    Exception in thread "main"
    -----------------------------------------------------------

    <h2>The below given is the application server console message</h2>
    ============================================ java.io.InvalidClassException: com.polaris.orbionecore.vo.charges.ChargesVO; local class incompatible: stream classdesc serialVersionUID = -5028538618673114162, local class serial
    VersionUID = 7410207045229243265
    java.io.InvalidClassException: com.polaris.orbionecore.vo.charges.ChargesVO; local class incompatible: stream classdesc serialVersionUID = -5028538618673114162, local class serialV
    ersionUID = 7410207045229243265
            at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:463)
            at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1521)
            at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
            at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264)
            at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
            at weblogic.rjvm.ClassTableEntry.readExternal(ClassTableEntry.java:33)
            at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1686)
            at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1644)
            at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
            at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
            at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:65)
            at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:37)
            at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:209)
            at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:232)
            at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:733)
            at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:742)
            at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
            at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
  2. What has happened here, it seems, is that the stub on the stand-alone client is incompatible with the actual class on the server. Apparently you have recompiled your server-side classes since you put the stub on the client. Try redeploying the server-side code and making sure the (new) client-side stubs are properly installed in the client classpath.
  3. This could also be related to the server losing its connection with its client. Try to restart the server and you should be able to invoke the EJB.