Sunday, October 16, 2011

Getting "DispatcherListener:2 * ERROR : gslsflAcceptConnAndSend : OS 2 : Unable to accept New TCP connection"

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com

Problem: Getting "DispatcherListener:2 * ERROR : gslsflAcceptConnAndSend : OS 2 : Unable to accept New TCP connection"

Symptoms:

Oracle Single Sign-On is highly availability. The OID is load balanced with Cisco CSM.
Getting "Unable to accept New TCP" error in the oid log file.
As per metalink 275712.1 the CSM should be configured to use FIN method for TCP connection closure rather than default of RST.
If we implement this change the load will be increased (FIN can take up to four packets) on the CSM and it will affect other applications.

if we leave this without applying any solution/workaround the connections will not be timed out nor closed, and may leave them open for days/weeks. This will become an issue over the period of time in terms of load and security.

Solution:


As per metalink note 451896.1 apply the following resolution/workaround? If so, what we should consider and what is the impact on OID

* Reconfigure the Load Balancer to send LDAP, rather than TCP, pings to OID.

* Turn off the ping on the LDAP port and simply ping the server. It is actually sufficient to monitor that the OPMN server process is active.

* Create a monitor process that leverages opmn to monitor OID or does a proper LDAP bind to check connectivity. Have the LDAP-unaware Load Balancer ping the monitor process. If monitor process detects the OID server is down it stops responding to the ping.

References:
NOTE:451896.1 -oidldapd01s Log Shows "Hard error on read, OS error =..."
NOTE:275712.1 - Oidldapd01.Log Fills Up With Error: DispatcherListener: Unable to accept New TCP connection
Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: