You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Simone Maletta <si...@alice.it> on 2008/02/29 08:40:51 UTC
Blocking consumer and transaction
Hi guys,
I've got a question: I'm using JMS transport to develope my work and I need that only an instance of my process will be on listining on the queue and that the queue as lenght one.
May I obtain this using servicemix-jms settings deploying with the wsdl?
May I also define a container-transaction with servicemix-jsr181 component?
And if this is possible, how I may do this?
Thank you for your time, regards
Simone
Re: Blocking consumer and transaction
Posted by Guillaume Nodet <gn...@gmail.com>.
On Fri, Feb 29, 2008 at 8:40 AM, Simone Maletta <si...@alice.it> wrote:
> Hi guys,
> I've got a question: I'm using JMS transport to develope my work and I need that only an instance of my process will be on listining on the queue and that the queue as lenght one.
> May I obtain this using servicemix-jms settings deploying with the wsdl?
<jms:consumer concurrentConsumers="1" synchronous="true" ... />
Only a single JMS message will be processed in the bus at a given time.
> May I also define a container-transaction with servicemix-jsr181 component?
> And if this is possible, how I may do this?
If you want a transaction that also span on the JMS side, use:
<jms:consumer concurrentConsumers="1" synchronous="true" transaction="xa" ... />
The jsr181 call will be enlisted inside the transaction started by the
jms component.
> Thank you for your time, regards
> Simone
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/