Hi Erik Can you tell us a little more about your software stack?
Which Broker/version are you using (Qpid Cpp, Qpid Java, something else non-Qpid)? There are two distinct Qpid JMS clients at the moment, the 0-8..0-10 client (i.e. qpid-client-x.xx-bin.tar.gz) and the AMQP 1.0 client (i.e. qpid-amqp-1-0-client-jms-x.xx-bin.tar.gz)? I guess from your previous list interactions that it is the latter. Can you confirm? Do you have a thread dump (jstack -l) when the problem occurs? Kind regards, Keith On 22 January 2015 at 08:48, Erik Aschenbrenner <[email protected]> wrote: > > 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? > > Regards, > Erik > > > > > -- > 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: [email protected] > For additional commands, e-mail: [email protected] >
