JMSAppender in Container Managed Transactions

[Benary Klaus <Kl...@GEHE.DE>]

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:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: JMSAppender in Container Managed Transactions

[Ceki Gülcü <ce...@qos.ch>]

What is your architecture? Which App Server are you using? Which version of 
the JMS spec?

ps: I doubt AUTO_ACKNOWLEDGE mode has anything to do with transactions in 
the session.

At 14:20 06.09.2002 +0200, you wrote:
>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

--
Ceki

TCP implementations will follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from
others. -- Jon Postel, RFC 793



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>