Last updated on NOVEMBER 05, 2016
Applies to:Oracle Containers for J2EE - Version 10.1.2.0.2 and later
JDBC - Version 10.1.0.5 and later
Information in this document applies to any platform.
When there is a network cut between database tier and application server tier the JMS/MDB connection to the database are correctly lost, but when the network connection is reestablished, the JMS/MDB connection to database is not reestablished
When these two parameters are configured:
dequeue-retry-interval and dequeue-retry-count the reconnection to database is not even attempted anymore
However, if there is a database shutdown or there is a kill of the session, the two parameters dequeue-retry-interval and dequeue-retry-count work correctly and try the reconnection.
How to overcome this?
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