Example 1: Handling a planned outage of an MDB application external resource
You can configure the system so that, if there is a problem with a dependent external system resource, the enterprise or business-level application can continue.
Before you begin
About this task
The JCA MBean emits JMX notifications to indicate that the MDB is paused, and that the MDB has resumed. Consider registering a message listener on the JCA MBean to receive the JMX notifications.
Procedure
- Navigate to the deployed enterprise application that contains the MDB.
- From the MDB, navigate to its JMS activation specification. Click and click Pause on the administrative panel for the MDB.
- When you receive a JMX notification and a log entry indicating that the MDB is paused, stop the database and apply the maintenance level. While the MDB is paused, no messages are sent to the exception destination and no error messages appear in the console related to the stopped database.
- Restart the database and test that it is working as expected.
- Log on to the administrative console again, navigate to the same enterprise or business-level application and click Resume on the administrative panel for the MDB. You can also resume the MDB by using scripting and the JCA MBean. The initial JMX notification and log entry indicate which MBean to use to resume the MDB. The MDB begins to be driven with the messages that are on the destination.