JMSAppender opens its session to the JMS server in "AUTO_ACKNOWLEDGE",
non-transacted mode. Basically, this means the message should be
"delivered" no matter what. So the JMSAppender is already set up to operate
outside of currently running transactions.
How are you processing the messages from the topic? MessageDrivenBean
MessageListener implementation? What is the set up of this consumption
piece?
|-----Original Message-----
|From: Benary Klaus [mailto:[EMAIL PROTECTED]]
|Sent: Friday, September 06, 2002 7:21 AM
|To: '[EMAIL PROTECTED]'
|Subject: JMSAppender in Container Managed Transactions
|
|
|How can I decouple logging via JMSAppender from the
|contrainer transaction
|in a stateless session EJB?
|I want the JMSAppender to deliver logs even when I call
|SessionContext.setRollbackOnly(). As a default,
|JMS committs a message to the queue or topic only when the
|contrainer
|transaction committs. As a side
|effect, a log within a failing contrainer transaction
|shows up only in those
|appenders that do not use JMS.
|Am I missing something?
|Any help would be appreciated.
|
|Klaus
|
|
|--
|To unsubscribe, e-mail:
|<mailto:[EMAIL PROTECTED]>
|For additional commands, e-mail:
|<mailto:[EMAIL PROTECTED]>
|
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
