Weblogic JMS Bridge Connections Are Not Refreshing After a Database Failure And Recovery
(Doc ID 955941.1)
Last updated on NOVEMBER 14, 2018
Applies to:Oracle WebLogic Server - Version 9.2 to 10.3
Information in this document applies to any platform.
The WebLogic JMS adapter is being used for JMS bridge configuration. When the JMS source/destination is restarted, the adapter is not able to reconnect to the restarted instance.
Only a redeployment of the JMS resource adapter resolves the problem.
We suspect that the connections in the resource adapter connection pool are never being refreshed since WebLogic is not able to detect the invalid connections.
In order to make the resource adapter detect invalid connections, we need to make the resource adapter connections testable.
For this to happen, the JMS adapter's ManagedConnectionFactory should implement the javax.resource.spi.ValidatingManagedConnectionFactory.
This is as per the following documentation on resource adapters:
However, it seems that the JMS adapter has not changed since WLS 8.1. So, we are not implementing any of the new features of JCA1.5 spec. Even though "Detecting Invalid Connections" is an optional requirement in the specification, WebLogic's implementation has added this feature since WLS 9.1. So, users are expecting this capability with the JMS adapter also.
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