JMS/MDB Reconnection after Losing a Network Connection (Doc ID 343325.1)

Last updated on FEBRUARY 14, 2025

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.

Goal

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?

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

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

JMS/MDB Reconnection after Losing a Network Connection (Doc ID 343325.1)

Applies to:

Goal

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!