There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • WebLogic JMS Production Timeout
    via by Dave Barton,
  • BytesMessage problem revisited
    via by Anamitra,
  • PeerGoneException in WLS6.1 JMS application
    via by Jon Wynett,
  • TextMessage max size limitation
    via by Paul,
  • connecting to BEA
    via by 3004,
    • at weblogic.rjvm.BasicOutboundRequest.sendReceive( at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke( at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke( at com.bea.ld.Server_ydm4ie_EOImpl_815_WLStub.executeFunction(Unknown Source) at com.bea.dsp.dsmediator.client.XmlDataServiceBase.invokeFunction( Caused by: at weblogic.rjvm.t3.T3JVMConnection.endOfStream( at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup( at weblogic.socket.SocketMuxer.deliverEndOfStream( at weblogic.socket.SocketMuxer.readReadySocketOnce( at weblogic.socket.SocketMuxer.readReadySocket( at weblogic.socket.JavaSocketMuxer.processSockets( at weblogic.socket.SocketReaderRequest.execute( at weblogic.kernel.ExecuteThread.execute( at
    No Bugmate found.