Hi Erik, due to the nature of this JMS client I don't think it will be possible for us to easily fix the locking issue.
The client is built upon an initial non-JMS API I put together for initial proving out of the AMQP 1.0 protocol. I later wrote a wrapper around that non-JMS API to provide JMS functionality. Unfortunately it's unlikely we could change the locking model without a fairly major rewrite since the locking assumptions are in that underlying non-JMS part. As Keith has already mentioned, there is already work underway to write a new JMS AMQP 1.0 client built on top of the Qpid Proton library which will (when complete) replace the existing JMS AMQP 1.0 client. In the meantime we'll continue to support the existing JMS AMQP 1.0 with small enhancements and bug-fixes, however for larger changes like this I think it's better to invest the time in the new Proton-based solution. Apologies, Rob On 30 January 2015 at 08:33, Erik Aschenbrenner <[email protected]> wrote: > Hi Keith, > > thanks for your answer. I changed my application code so that messages > listeners are not blocking anymore and delegating the message processing as > fast as possible to other threads. > > Maybe I raise a Jira ticket if I notice still problems with this issue. > > Regards, > Erik > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Qpid-JMS-Message-listener-blocks-other-message-listener-on-different-session-tp7618696p7619207.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] > >
