How to Setup Exception Listeners/Handler to Have a Failure Recovery Code
(Doc ID 1386894.1)
Last updated on APRIL 14, 2023
Applies to:Oracle WebLogic Server - Version 10.3 to 10.3.5
Information in this document applies to any platform.
In a HA setup, it is expected for all the services/setup is up and running in all the possible scenarios. In some cases like network instability or a JVM crash for the dependent resources (like a remote queue), etc. the setup becomes unavailable, thus need to make sure that the application is able to recover from these scenarios without complete downtime.
In case of JMS services, use a Distributed destination targeted to a WLS cluster, in order to achieve the HA, along with the implementation of the server/service level migration.
In case there are clients which are doing a JNDI look-up for the JMS resource (Distributed Destination Member), on the remote server instance/host and due to the hosting server failure, the member destination migrates to a different JVM (see service migration/migratable targets for more information). In this scenario, the reconnection logic is used, once encountering any exception with the running client, there is an attempt made to reconnect to the destination.
Thus this document shares the requirement for the Exception Handlers and simple sample clients for Java as well as for .Net that can be referred for setting/coding the exception handler in the application code.
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