java.io.EOFException

This exception has no message.

Solutions on the web4531

  • via Terracotta by ihrytsyuk, 3 weeks ago
    This exception has no message.
  • This exception has no message.
  • This exception has no message.
  • Stack trace

    • java.io.EOFException at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237) at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223) at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source) at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146) at weblogic.security.Security.runAs(Security.java:61) at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916) at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1017) at com.avaya.reporting.bi.config.MBeanTransaction.invoke(MBeanTransaction.java:374) at com.avaya.reporting.bi.config.MBeanTransaction.invoke(MBeanTransaction.java:349) at com.avaya.reporting.bi.config.MBeanTransaction.doDomainCall(MBeanTransaction.java:314) at com.avaya.reporting.bi.config.MBeanTransaction.lockDomain(MBeanTransaction.java:290) at com.avaya.reporting.bi.config.MBeanTransaction.execute(MBeanTransaction.java:200) at com.avaya.reporting.bi.config.MBeanConfigExecutor.execute(MBeanConfigExecutor.java:147) at com.avaya.reporting.bi.config.RunBIConfig.runXmlTransaction(RunBIConfig.java:127) at com.avaya.reporting.bi.config.RunBIConfig.runConfig(RunBIConfig.java:99) at com.avaya.reporting.bi.config.RunBIConfig.main(RunBIConfig.java:84) Caused by: java.io.EOFException at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:345) at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:827) at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:761) at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:958) at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:889) at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:339) at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29) at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago