Okay, thanks, that looks like something in the right direction, though I
think it will take me some time to understand camel and how to use it with
activemq.
Thanks again,
Marko
James.Strachan wrote:
>
> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>
>>
>>
>>
James.Strachan wrote:
>
> 2008/12/11 mmocnik <[EMAIL PROTECTED]>:
>>
>>
>> James.Strachan wrote:
>>>
>>>> [...]
>>> though I think putting redelivered messages at the tail of the queue
>>> (so its dispatched last) is
James.Strachan wrote:
>
>> [...]
> though I think putting redelivered messages at the tail of the queue
> (so its dispatched last) is what you want - so resending the message
> rather than rolling back & closing is probably more suitable
>
Yes, that is what I want to achieve, but if I do it tha
James.Strachan wrote:
>
>>[...]
> Normally redelivery of the last message occurs - to avoid breaking
> order. Is that what you need?
>
> If you are not seeing this - are you closing & recreating the
> MessageConsumer on rollback?
>
Oh, okay, that is what I am seeing.
But its not what I want
Hi,
James.Strachan wrote:
>
> 2008/12/10 mmocnik <[EMAIL PROTECTED]>:
>>
>> Hi,
>>
> [...]
>> So:
>> Is there any way to just rollback one message?
>
> Sure - so long as you do a commit/rollback on each message :). i.e. if
> you do a comm
Hi,
I'm using ActiveMQ 5.1.0 to asynchronously send mail via an unrelyable mail
server.
I'm using session.rollback() if a delivery attempt failed, since I couldn't
get redelivery done any other way.
(I'm using vm://localhost by the way)
Problem: Poison Messages. If a message really isn't deliver
