|-----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
|the real question has to do with whether the JMS drivers
|are XA-enabled and obtained through a container-defined
|resource manager. If so, the container is going to try to
|coordinate any transaction in progress across the JDBC and
|JMS resources. Usually, that is what you want. In this
This is just plain false. There is a reason the JMS spec defines the method
signature to obtain a session object to take a boolean indicating whether
the session should be transactionally aware. If you specify that the
session should not be transactionaly aware when obtaining from the jms
connection, then the container is not going to try to register it with the
TransactionManager (or if it does you have much larger problems then just
whether your app logging is happening or not).
|case, you want the logging to happen regardless of the
|transaction outcome. Fundamentally, the JMSAppender needs
|to obtain its JMS resources from a source other than the
|container so that the container is not aware of them and
|doesn't enlist them in the transaction.
|
|Jim
|
|-----Original Message-----
|From: Benary Klaus [mailto:[EMAIL PROTECTED]]
|Sent: Friday, September 06, 2002 8:16 AM
|To: '[EMAIL PROTECTED]'
|Subject: AW: JMSAppender in Container Managed Transactions
|
|
|Hi Steven, hi Ceki,
|
|There is a listener bean durably subscribed to the topic.
|The crucial part of the deployment descriptor is:
|
|<message-driven>
| <display-name></display-name>
| <ejb-name>ListenerBean</ejb-name>
| <ejb-class>com.jcoffee.base.sl.ListenerBean</ejb-class>
| <transaction-type>Container</transaction-type>
| <acknowledge-mode>Auto-acknowledge</acknowledge-mode>
| <message-driven-destination>
| <destination-type>javax.jms.Topic</destination-type>
| <subscription-durability>Durable</subscription-durability>
| </message-driven-destination>
| <resource-ref>
| <res-ref-name>jdbc/DS</res-ref-name>
| <res-type>javax.sql.DataSource</res-type>
| <res-auth>Container</res-auth>
| </resource-ref>
|</message-driven>
|
|But, I think that the consumer cannot be the reason for
|this behavior. The
|producer side
|would behave the same way even if there was no consumer
|subscribed at all.
|Besides: It is BEA 7.00 and WebLogic JMS according to JavaSoft JMS
|specification version 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-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]>
|>
|
|--
|To unsubscribe, e-mail:
|<mailto:[EMAIL PROTECTED]>
|For additional commands, e-mail:
|<mailto:[EMAIL PROTECTED]>
|
|
|<font size="1">Confidentiality Warning: This e-mail
|contains information intended only for the use of the
|individual or entity named above. If the reader of this
|e-mail is not the intended recipient or the employee or
|agent responsible for delivering it to the intended
|recipient, any dissemination, publication or copying of
|this e-mail is strictly prohibited. The sender does not
|accept any responsibility for any loss, disruption or
|damage to your data or computer system that may occur
|while using data contained in, or transmitted with, this
|e-mail. If you have received this e-mail in error,
|please immediately notify us by return e-mail. Thank you.
|
|
|--
|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]>
