The work around suggested by Keith would work - the issue is that there is a single lock for each connection, and the lock is held for the duration of the time the thread is within onMessage(). Separate connections would use separate locks and thus not face this issue.
In terms of a timeline for the new JMS client, I'll defer to Robbie and Tim who are the ones working on that, Cheers, Rob On 30 January 2015 at 11:45, Erik Aschenbrenner <[email protected]> wrote: > Hi Rob, > > thanks for this information. > > Is there a plan when the proton based JMS AMQP 1.0 client will be > available? > > Do you think, that the workaround suggested by Keith (using a dedicated > connetion for each message listener) would work? > > Regards, > Erik > > > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Qpid-JMS-Message-listener-blocks-other-message-listener-on-different-session-tp7618696p7619216.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] > >
