Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Tue, 4 Sep 2012 09:24:54 -0700 (PDT)
From: gdulus <pawel.gdula@kaufda.de>
To: users@activemq.apache.org
Message-ID: <1346775894240-4656028.post@n4.nabble.com>
Subject: Idempotent consumer problem
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hey 

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

watcher.queue.source
watcher.queue.sink
watcher.queue.used

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
fast
2) Consumers read with no problem from watcher.queue.sink, but camel is
ultra slow

this is AMQ config: 
http://activemq.2283324.n4.nabble.com/file/n4656028/activemq.xml
activemq.xml 

Any hint?


--
View this message in context: http://activemq.2283324.n4.nabble.com/Idempotent-consumer-problem-tp4656028.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.