qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Aschenbrenner <easch...@icubic.de>
Subject Qpid JMS: Message listener blocks other message listener on different session
Date Thu, 22 Jan 2015 08:48:54 GMT
Dear Qpid Users,

I have an application where I'm using different message listeners to process
data from different topics.

For example I have a message listener which processes reference data
received via a broadcast topic and another message listener which processes
market data like trades and orders received on another broadcast topic.

Both message listeners are created by a dedicated JMS session (one session
for each message listener).

Because the market data can only be processed if all the reference data was
processed initially, the message listener for the market data should wait
and block if the reference data was not received completely.

So here the problem: if the thread of the message listener for market data
is blocked, the receiving of the reference data is also blocked an no other
data is received on the reference data listener.

Why are there dependencies between message listeners on different session?
As far as I understand each session should have it´s on thread?


View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-Message-listener-blocks-other-message-listener-on-different-session-tp7618696.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

View raw message