activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From gdulus <>
Subject Idempotent consumer problem
Date Tue, 04 Sep 2012 16:24:54 GMT

We have strange problem with Jdbc based idempotent consumer. We have three


we populate watcher.queue.source queue form which Camel IC is reading
messages and populate them to watcher.queue.sink. Consumers read from
watcher.queue.sink and when they finish processing of the message they send
to watcher.queue.used queue message id. On watcher.queue.used we registered
bean which listening on incoming messages (plain string which is id of
consumed message) and we remove entry from Camel IC. 

For some reason we hit in two bad scenarios.

1) Consumers don't read from watcher.queue.sink queue, but camel is blazing
2) Consumers read with no problem from watcher.queue.sink, but camel is
ultra slow

this is AMQ config:

Any hint?

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message