message in context:
http://old.nabble.com/guaranteed-message-processing-question...-tp26202573p26376095.html
Sent from the Camel - Users mailing list archive at Nabble.com.
as
>> - duplicates allowed
>> - at most one
>> - etc.
>>
>> Try to see if that can help, looks as if duplicates allowed is the
>> kind of mode you run with.
>>
>>
>
>
> -
> Ben - Senior Consultant
>
> --
> View this message
> such as
> - duplicates allowed
> - at most one
> - etc.
>
> Try to see if that can help, looks as if duplicates allowed is the
> kind of mode you run with.
>
>
-
Ben - Senior Consultant
--
View this message in context:
http://old.nabble.com/guaranteed-message-
t;> Hi
>>
>> Do you use persistent queues? Then make sure the queues are empty when
>> testing. Maybe deleting the AMQ data folder before testing.
>>
>
>
> -
> Ben - Senior Consultant
>
> --
> View this message in context:
> http://old.nabble.co
ure I
understood the intended behavior first...
thanks in advance
-
Ben - Senior Consultant
--
View this message in context:
http://old.nabble.com/guaranteed-message-processing-question...-tp26202573p26206508.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yeah as Christian says you need to use transactions for that.
On Wed, Nov 4, 2009 at 8:23 PM, Christian Schneider
wrote:
> As far as I know the transactional client aproach is the only good way to
> guarantee that no message is lost.
> You can take a look at these pages:
> http://camel.apache.or
As far as I know the transactional client aproach is the only good way
to guarantee that no message is lost.
You can take a look at these pages:
http://camel.apache.org/jms.html section: Enabling Transacted Consumption
http://camel.apache.org/transactional-client.html section: Camel 2.0 -
JMS
e a transactional client approach (if so, how exactly)? I
tried this briefly but haven't been able to get it to work. Is there
another option like using the JMS acknowledgement mode or something?
thanks
-
Ben - Senior Consultant
--
View this message in context:
http://old
