![]() |
The extended messaging service can handle messages read from JMS destinations within the scope of a transaction. If transaction handling is specified for a JMS destination, the JMS Listener starts a global transaction before it reads any incoming JMS message from that destination. When the message bean processing has finished, the JMS Listener commits or rolls back (using JTA transaction control) the transaction.
To configure WebSphere to provide transactional support for the extended messaging service, you complete the following stages:
Notes:
If messages are queued to be sent within a global transaction they are sent when the transaction is committed. If the processing of a message causes the transaction to be rolled back, then the message that caused the bean instance to be invoked is left on the JMS destination.
You can use the MaxRetries configuration option for the destination to define the maximum number of times the JMS Listener attempts to read a message from the destination. When MaxRetries has been reached, the JMSListener for that destination is stopped. When you have resolved the problem, you must then stop and restart the given message bean's EJB module from Systems Management.
Related tasks... | |
Configuring the extended messaging service | |
Developing a message bean to use extended messaging | |