Client TCP KEEPALIVE TIMEOUT Impact
(Doc ID 2357821.1)
Last updated on JULY 23, 2019
Applies to:JDBC - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
WebSphere is being used with 2 Instances of JVM running on two different nodes. Messaging Engine ( ME ) is configured in ACTIVE/ PASSIVE mode. Whenever JVM instance is going down , ME is getting failed over to another node.
However, database connectivity is not getting through after this failover.
Application vendor recommended to review the parameter TCP KEEP ALIVE TIMEOUT.
Current value is 7200000 ( 2 Hours ) and the suggestion is to change it to 5 minutes.
Database is 2 node RAC on Solaris 5.11.
Database Version is 184.108.40.206
Will there be any negative impact on this parameter TCP KEEP ALIVE TIMEOUT change ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document