OK. The client app has a durable consumer C has connected to Topic T, and
while it is active, messages X, Y, and Z are eventually delivered by the
broker and consumed by C. Then, C disconnects and then reconnects
(sometimes immediately). When C reconnects, sometimes messages X, Y, and Z
are rede
There's no mechanism to request that the broker send you everything it has;
if that is going to happen, it happens when the client connects.
In your testing, are you saying that if topic T has messages A, B, and C
that have not yet been consumed by offline durable consumer C1, and
consumer C2 conn
Yeah, I knew I was forgetting something. I have the message delivery setup
as a durable Topic with retroactive set to true.
Mark
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Redelivery-of-messages-already-consumed-tp4721576p4721578.html
Sent from the ActiveMQ - User m
On 02/03/2017 09:36 AM, fenbers wrote:
My application consumes messages, which light up certain status indicators.
While this works fine, I have a problem in that if the user exits and
restarts my application, sometimes the messages are redelivered and
sometimes they are not. I want all non-expi
redelivery blocks its consumer, the implementation is in
org.apache.activemq.ActiveMQMessageConsumer#rollback
The blocking it so preserve message order for that consumer.
Have a peek at: https://issues.apache.org/jira/browse/AMQ-2710 to find
a strategy and test camel route for resubmitting message
You may want to try the camel or servicemix user lists for this one.
2009/5/7 Sanjay Jain
>
> Can anybody please help me out to resolve this issue?
>
> Thanks,
> Sanjay
>
>
> Sanjay Jain wrote:
> >
> > Hi All,
> >
> > I tried hard to get the redelivery working when route is transacted. But
> > s
Can anybody please help me out to resolve this issue?
Thanks,
Sanjay
Sanjay Jain wrote:
>
> Hi All,
>
> I tried hard to get the redelivery working when route is transacted. But
> so far no luck with redelivery at all. I am using camel-1.5.0 in
> servicemix 3.2.2.
>
> This is how my camel-co
