Client TCP KEEPALIVE TIMEOUT Impact (Doc ID 2357821.1)

Last updated on FEBRUARY 06, 2023

Applies to:

JDBC - Version 11.2.0.4.0 and later
Oracle Net Services - Version 19.14.0.0.0 to 19.14.0.0.0 [Release 19.0]
Information in this document applies to any platform.

Goal

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 11.2.0.3

Will there be any negative impact on this parameter TCP KEEP ALIVE TIMEOUT change ?

Solution

	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

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Client TCP KEEPALIVE TIMEOUT Impact (Doc ID 2357821.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!