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.

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 666705, 1 year 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, 1 year ago
Reference to server no longer exists. Possible reasons for failure include having servers with duplicate names runnin g on a cluster. Please check your configuration for this error.
via Oracle Community by 666705, 1 year 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.
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:129)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.