java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs

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
A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs
via Oracle Community by 3004, 1 year ago
A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff 3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
via Oracle Community by 3004, 1 year ago
A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff 3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
via Oracle Community by 666705, 1 year ago
A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@13704c7 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
via Oracle Community by 3004, 1 year ago
A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1c94ff 3 - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
via Oracle Community by 3004, 1 year ago
A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@1871db 1 - idle timeout: '60000' ms, socket timeout: '5000' ms', in the configured timeout period of '60' secs
java.io.IOException: A complete message could not be read on socket: 'weblogic.rjvm.t3.T3JVMConnection@11a5fd0', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:776)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
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.