java.io.IOException

Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuration for this error.

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 web30659

  • via Oracle Community by 666705, 11 months ago
    Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuration for this error.
  • via Oracle Community by 3004, 2 weeks ago
    Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuration for this error.
  • via Oracle Community by 666705, 11 months ago
    Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio n for this error.
  • Stack trace

    • java.io.IOException: Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuration for this error. at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(ServerInfoManager.java:111) at weblogic.rmi.cluster.ServerInfoManager.readUpdate(ServerInfoManager.java:95) at weblogic.cluster.MemberAttributes.readExternal(MemberAttributes.java:103) 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.cluster.HTTPExecuteRequest.execute(HTTPExecuteRequest.java:91) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    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.