Datasource Declared Unhealthy After Transaction Timeouts And Thus Refusing Any Further Calls Using XA (Doc ID 1481356.1)

Last updated on JULY 25, 2022

Applies to:

Symptoms

A WLS 10.3.4+ datasource connection is returned to the pool but has an invalid state after the second timeout, which we can see in the log after the third call was done. We get the error SQLException Ocurred:Invalid or Stale Connection found in the Connection. It looks like the root of the problem is that when our call is timed out, the connection is returned to pool with some inappropriate state.

Future calls in WLS 10.3.2 and WLS 10.3.3 are responded to appropriately. In WLS 10.3.4 and higher, after 1 or 2 transaction timeouts using an XA datasource, subsequently all the requests fail with SQLException Ocurred:Invalid or Stale Connection found in the Connection Cache

Changes

Cause

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