JMS Server Failover Not Working When Setting inactive-connection-timeout-seconds on Datasource Associated with JDBC Store
(Doc ID 2097840.1)
Last updated on JUNE 12, 2024
Applies to:
Oracle WebLogic Server - Version 12.1.2.0.0 to 12.2.1.0.0 [Release 12c]Information in this document applies to any platform.
Goal
You are using the JDBC Datasource harvesting setting <inactive-connection-timeout-seconds>300</inactive-connection-timeout-seconds> and this Datasource is associated with a JDBC Store.
You are then getting:
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 |