My Oracle Support Banner

Invalid DataSource Connections in Connection Pool due to Firewall - Timeout or Failover (Doc ID 399643.1)

Last updated on FEBRUARY 13, 2024

Applies to:

Oracle Containers for J2EE - Version 10.1.2.0.0 to 10.1.3.5.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.

Symptoms

Setup:

 

  1. During resilient test of firewall (firewall failover) the connection pool becomes invalid
    • Application is using Sticky Session
    • So on firewall failover end users loose their sessions
  2. For performance reasons applications (BPEL) need to maintain about 25 minimum connections in OC4J managed connection pool.


When application is not used for a while (for example not used overnight), the physical connection to Database through firewall is terminated by firewall timeout settings and the pooled connections becomes invalid.

Cause

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
Symptoms
Cause
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.