RE: JMSAppender in Container Managed Transactions

2002-09-10 Thread Benary Klaus
: Freitag, 6. September 2002 17:33 An: [EMAIL PROTECTED] Betreff: RE: JMSAppender in Container Managed Transactions And this was my point, on which you vehemently contradicted me. The question was about PRODUCING messages, not about CONSUMING them. And the producing was to be done

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ebersole, Steven
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

Re: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ceki Gülcü
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

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ebersole, Steven
|-Original Message- |From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] |Sent: Friday, September 06, 2002 8:02 AM |To: Log4J Users List |Subject: Re: JMSAppender in Container Managed Transactions | | | |What is your architecture? Which App Server are you

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ceki Gülcü
:[EMAIL PROTECTED]] |Sent: Friday, September 06, 2002 8:02 AM |To: Log4J Users List |Subject: Re: JMSAppender in Container Managed Transactions | | | |What is your architecture? Which App Server are you using? |Which version of |the JMS spec? | |ps

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Cakalic, James
1.0.2. Klaus -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED]@GEHE Gesendet: Freitag, 6. September 2002 14:49 An: [EMAIL PROTECTED] Betreff: RE: JMSAppender in Container Managed Transactions JMSAppender opens its session to the JMS server in AUTO_ACKNOWLEDGE, non

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ebersole, Steven
|-Original Message- |From: Cakalic, James [mailto:[EMAIL PROTECTED]] |Sent: Friday, September 06, 2002 8:24 AM |To: Log4J Users List |Subject: RE: JMSAppender in Container Managed Transactions | | |As you say, the problem is on the producer side. I think

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ebersole, Steven
| An: [EMAIL PROTECTED] | Betreff: RE: JMSAppender in Container Managed Transactions | | 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

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Ebersole, Steven
: [EMAIL PROTECTED]@GEHE | Gesendet:Freitag, 6. September 2002 15:53 | An: [EMAIL PROTECTED] | Betreff: RE: JMSAppender in Container Managed Transactions | | I have nearly the same exact setup, except that: | 1) I am still on WL 6.1; | 2) I use a custom log4j

RE: JMSAppender in Container Managed Transactions

2002-09-06 Thread Cakalic, James
LogSessionBean from another EJB, the container would put all its work in a separate transaction from the one in progress. Jim -Original Message- From: Ebersole, Steven [mailto:[EMAIL PROTECTED]] Sent: Friday, September 06, 2002 10:04 AM To: 'Log4J Users List' Subject: RE: JMSAppender in Container