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]>
