Application Takes 6 Minutes to Undeploy from JDeveloper Integrated WebLogic Server (Doc ID 1194823.1)

Last updated on AUGUST 04, 2016

Applies to:

Oracle JDeveloper - Version 11.1.1.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 19-Nov-2013***

Symptoms

TOO MANY CONNECTION TIMEOUT MESSAGES DURING/AFTER UNDEPLOY

When undeploying an application being run in ADRS the user will see several of the following messages in the WebLogic console:

<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,094 during the configured idle timeout of 5 secs>
<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,095 during the configured idle timeout of 5 secs>
<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,099 during the configured idle timeout of 5 secs>
<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,096 during the configured idle timeout of 5 secs>
<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,097 during the configured idle timeout of 5 secs>
<Jul 21, 2010 2:46:56 PM PDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 127.0.0.1:53,098 during the configured idle timeout of 5 secs>



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