JMS Server Failover Not Working When Setting inactive-connection-timeout-seconds on Datasource Associated with JDBC Store
Last updated on DECEMBER 05, 2016
Applies to:Oracle WebLogic Server - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 12c]
Information in this document applies to any platform.
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:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms