set jms.useAsyncSend=false in
> > connection URI (connection to embedded broker) instead of
> > jms.useAsyncSend=true.
> >
> >
> > Best regards, Ivan
> >
> >
>
> --
> View this message in context:
> http://old.nabble.com/ActiveMQ-RA-and-client-acknow
AsyncSend=false in
> connection URI (connection to embedded broker) instead of
> jms.useAsyncSend=true.
>
>
> Best regards, Ivan
>
>
--
View this message in context:
http://old.nabble.com/ActiveMQ-RA-and-client-acknowledge-in-a-message-driven-bean-tp28311771p28746878.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello
2010/4/21 Gary Tully :
> Use a transacted delivery in your endpoint activation and throw an exception
> from onMessage. if you have the source, take a peek at this test:
> org.apache.activemq.ra.MDBTest.testMessageExceptionReDelivery
Thanks a lot, it works like a charm now!
Another thing
Use a transacted delivery in your endpoint activation and throw an exception
from onMessage. if you have the source, take a peek at this test:
org.apache.activemq.ra.MDBTest.testMessageExceptionReDelivery
On 21 April 2010 06:02, Ivan Pechorin wrote:
> Hello!
>
> I use JBoss, ActiveMQ resource a
Hello!
I use JBoss, ActiveMQ resource adapter (RA), and a message-driven bean
(MDB) with a persistent queue.
I need to be able to leave a message in queue if something bad
happened inside method onMessage() of my MDB.
The question is how to achieve it?
I looked into the source of ActiveMQ RA, and
