EM 11g: Enterprise Manager 11.1.0.1 Grid Control OMS Hangs with Warnings: BEA-000449 Closing socket as no data read from it during the configured idle timeout of 5 secs (Doc ID 1365628.1)

Last updated on MARCH 20, 2017

Applies to:

Enterprise Manager Base Platform - Version 11.1.0.1 to 11.1.0.1 [Release 11.1]
Information in this document applies to any platform.
Checked for relevance on 13-May-2014

Symptoms

The Enterprise Manager (EM) 11.1.0.1 Grid Control OMShangs and becomes unresponsive ; restarting the OMS is successful.

emoms.trc

2011-10-04 00:27:21,717 [JobWorker 161484:Thread-121] WARN jdbc.ConnectionCache _getConnection.354 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
2011-10-04 00:27:37,917 [JobWorker -2:Thread-58] WARN jdbc.ConnectionCache _getConnection.353 - Io exception: Connection reset
java.sql.SQLRecoverableException: Io exception: Connection reset
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)


2011-10-04 00:27:37,919 [JobWorker -2:Thread-58] WARN jdbc.ConnectionCache _getConnection.354 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
2011-10-04 00:27:59,821 [JobWorker 161434:Thread-67] WARN jdbc.ConnectionCache _getConnection.353 - Io exception: Connection reset
java.sql.SQLRecoverableException: Io exception: Connection reset


EMGC_OMS1.OUT

<Oct 4, 2011 12:17:38 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
<Oct 4, 2011 12:21:00 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
<Oct 4, 2011 12:21:10 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
<Oct 4, 2011 12:21:10 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>
<Oct 4, 2011 12:21:10 AM EDT> <Warning> <Socket> <BEA-000449> <Closing socket as no data read from it during the configured idle timeout of 5 secs>


Also verify the following logs as well:

At problematic time stamp:

No error messages logged in admin logs.
No error messages logged in nodemanager.log.
No errors of OMS crash in emctl.msg at the problematic time stamp.
No errors of Database crash or restart in the alert.log.

Changes

 

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