+

Search Tips   |   Advanced Search

Manage message delivery for MDBs deployed as message endpoints



Overview

This section discusses management of message delivery for message-driven beans (MDBs) deployed as message endpoints.

The message endpoints are managed beans (MBeans) for inbound resource adapters compliant with JCA v1.5.

The appserver provides message endpoint MBeans to assist you in managing the delivery of a message to the MDBs acting as listeners on specific endpoints, which are destinations, and in managing the enterprise information system (EIS) resources utilized by these MDBs.

With message endpoint MBeans, we can activate and deactivate specific endpoints within the applications to ensure that messages are delivered only to listening MDBs interacting with healthy EIS resources. This capability allows you to optimize the performance of the JMS applications in situations where an EIS resource is not behaving as expected. Message delivery to an endpoint typically fails when the message driven bean that is listening invokes an operation against a resource not healthy.

For example, a messaging provider, which is an inbound resource adapter that is JCA V1.5 compliant, might fail to deliver messages to an endpoint when its underlying MDB attempts to commit transactions against a database server not responding.

Design the MDBs to delegate business processing to other enterprise beans. Do not access the EIS resources directly in the MDB, but do so indirectly through a delegate bean.

Message endpoint MBeans alleviate two problems inherent to applications that provide message endpoints that access resources:

The capability to deactivate (pause) and reactivate (resume) a specific message endpoint alleviates these problems by enabling the administrator to deactivate the endpoint from processing messages that are destined to fail. When the message endpoint is deactivated, we can repair the resource that is causing the problems and reactivate the endpoint to resume handling message requests. In the course of troubleshooting, you will not affect the resource adapter or the application that is hosting the endpoint.

 

Procedure

  1. From the admin console, navigate to the Message Endpoints panel for the application that is hosting the message endpoint.

    Applications | Application Types | Websphere enterprise apps | application_name | Runtime panel | Message Endpoints

    The panel lists the set of message endpoints hosted by the application.

  2. Deactivate the message endpoint by selecting the appropriate endpoint and clicking Pause.

  3. When the message endpoint is inactive, diagnose and repair the underlying cause of the delivery failures.

  4. Reactivate the message endpoint by selecting the appropriate endpoint and clicking Resume.

 

Results

The behavior you will observe when you deactivate a message endpoint using the message endpoint MBean is dependent upon a variety of factors, including...

Some specific examples...


Manage message endpoints

 

Related tasks

Manage the message endpoint lifecycle using scripting