java.io.IOException

The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@1701ba3 - id: '77875006513513221S:144.92.8.135:[7029,-1,-1,-1,-1,-1,-1]:myuser:WebLogicAdmin' connect time: 'Thu Dec 04 09:34:57 CST 2008'' has already been shut down

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web26021

  • via Coderanch by Thaya Thava, 8 months ago
    The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@1701ba3 - id: '77875006513513221S:144.92.8.135:7029,-1,-1,-1,-1,-1,-1:myuser:WebLogicAdmin' connect time: 'Thu Dec 04 09:34:57 CST 2008'' has already been shut down
  • via Oracle Community by Thaya-Oracle, 11 months ago
    The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@1701ba3 - id: '77875006513513221S:144.92.8.135:[7029,-1,-1,-1,-1,-1,-1]:myuser:WebLogicAdmin' connect time: 'Thu Dec 04 09:34:57 CST 2008'' has already been shut down
  • via Oracle Community by 2607497, 1 year ago
    The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@1ea79c5 - id: '-8482198073647225410S:128.0.0.118:[7003,7003,-1,-1,-1,-1,-1 ]: ManagedServer ManagedServer ' connect time: 'Mon Oct 05 14:34:20 IST 2015'' has already been shut down
  • Stack trace

    • java.io.IOException: The connection manager to ConnectionManager for: 'weblogic.rjvm.RJVMImpl@1701ba3 - id: '77875006513513221S:144.92.8.135:[7029,-1,-1,-1,-1,-1,-1]:myuser:WebLogicAdmin' connect time: 'Thu Dec 04 09:34:57 CST 2008'' has already been shut down at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1706) at weblogic.rjvm.ConnectionManager.createHeartbeatMsg(ConnectionManager.java:1649) at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg(ConnectionManager.java:611) at weblogic.rjvm.RJVMImpl$HeartbeatChecker.timerExpired(RJVMImpl.java:1540) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:265) at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    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

    You’re the first here who have seen this exception.