Translate

Tuesday, June 2, 2015

BEA-000450 Socket xxxx internal data record unavailable


(probable closure due idle timeout), event received 0 - Even After Applying The Patch 12319435 (Doc ID 1564161.1)

We often see this error messages in weblogic instance logs & These makes difficult for developer/support engineer to while debugging the issues which actually impacting application functionality and response.

However these messages/warnings are harmless.

<Jun 12, 2012 12:07:32 PM EDT> <Warning> <Socket> <mydomain.com> <MyServer> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1339517252171>   <BEA-000450> <Socket 525 internal data record unavailable (probable closure due idle timeout), event received 0> 
<Jun 12, 2012 12:07:52 PM EDT> <Warning> <Socket> <mydomain.com> <MyServer> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1339517272172> 
  <BEA-000450> <Socket 519 internal data record unavailable (probable closure due idle timeout), event received 0> 
<Jun 12, 2012 12:10:37 PM EDT> <Warning> <Socket> <mydomain.com> <MyServer> <ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <> <1339517437176>



Here is Error trace from production logs:

bash-3.2$ <May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.228.12.29:62,720 during the configured idle timeout of 5 secs> 
<May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.228.12.29:62,721 during the configured idle timeout of 5 secs> 
<May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 387 internal data record unavailable (probable closure due idle timeout), event received -32> 
<May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 402 internal data record unavailable (probable closure due idle timeout), event received 0> 
<May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it on 10.228.12.29:62,719 during the configured idle timeout of 5 secs> 
<May 1, 2015 9:24:26 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 292 internal data record unavailable (probable closure due idle timeout), event received -32> 
<May 1, 2015 9:24:31 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 291 internal data record unavailable (probable closure due idle timeout), event received -32> 
<May 1, 2015 9:24:31 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 382 internal data record unavailable (probable closure due idle timeout), event received 0> 


SOLUTION :

BEA-000450 is a harmless message displayed by WebLogic Server.

There are 2 patches for unpublished bugs 11873369 and 16193754 that can be applied to mitigate this issue.

You can apply 11873369 or 16193754 or both depending on your Operating System as follows:

1. Patch for unpublished defect 11873369: this patch is intended to reduce the severity of BEA-000450 to debug. This applies to any Operating System.

2. Patch for bug 16193754: this is a fix that fixes the pollset minimizing the chances of this message getting logged. This applies to Solaris and HP UX environments.

Patches are available for unpublished defects 11873369 and 16193754:

Apply patch 16193754 in a Solaris environment

Please download patch 16193754 from MyOracleSupport > Patches and Updates > Patch number or bug number (enter your weblogic version)

For Reference :

876004.1 How to Apply WebLogic Server (WLS) Patches Using Smart Update [Video]


-- Srikanth Govada

No comments:

Post a Comment