E-WL: WebLogic 8.1 and 9.2: Repeatedly Logs Message "Connection failure. java.io.IOException: A complete message could not be read on socket"

(Doc ID 646636.1)

Last updated on JANUARY 02, 2014

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.44 to 8.49 [Release 8.4]
Information in this document applies to any platform.

This document was previously published as Customer Connection Solution 201006895



***Checked for relevance on 02-Jan-2014***


Symptoms

The following exception is being written repeatedly to the WebLogic log files:

####<Jun 29, 2004 11:03:37 AM EDT> <Error> <HTTP> <qdcws0173> <PIA2> <ExecuteThread: '2' for queue: 'weblogic.kernel.System'> <> <> <BEA-101083> <Connection failure.
java.io.IOException: A complete message could not be read on socket: 'weblogic.servlet.internal.MuxableSocketHTTP@8b30ae - idle timeout: '30000' ms, socket timeout: '30000' ms', in the configured timeout period of '60' secs
at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.javANSWER:775)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.javANSWER:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.javANSWER:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.javANSWER:118)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.javANSWER:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.javANSWER:223)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.javANSWER:49)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.javANSWER:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.javANSWER:170)

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms