Hi Rob, We are considering the JMS AMQP 1.0 client to be of high importance and central to the success of our project. We have found that the Qpid jms amqp 1.0 was indeed slow from a performance perspective.
Is there a timeline for shifting work toward the jms amqp 1.0 implementation on Proton? Thank you, Cory -----Original Message----- From: Rob Godfrey [mailto:[email protected]] Sent: Tuesday, August 26, 2014 3:40 AM To: [email protected] Subject: Re: Experiences with Qpid AMQP 1.0 JMS client in production Hi Erik, I'm pretty sure there are people using the JMS 1.0 client in production, as it is the client that Microsoft points users of their Azure Service Bus offering to if they want to connect using Java applications. I'm not sure how many of these users are subscribed to this list however. In terms of the client itself, it's obviously less mature than the 0-8/9/-9-1/-10 client (though almost definitionally it's as mature as that client was when that client was the same age :-) ), and doesn't have some of the features that the older client does (such as automatic failover support). Moreover the JMS AMQP 1.0 client was written before the Proton effort at a single AMQP 1.0 protocol engine was started - and as a result we are aiming to eventually replace the current JMS 1.0 client with one that is built around Proton so that overall our AMQP 1.0 effort is easier to maintain (Robbie Gemmell is leading this) . Until that work is completed we'll still try to address any issues that arise (there are a number of fixes for the JMS 1.0 client in the upcoming 0.30 release), and also look at introducing new features where they are in line with the work on the standardised JMS mapping to AMQP that is going on at OASIS. By keeping to standard JMS and the OASIS mapping there should be minimal impact in moving from the current JMS AMQP 1.0 client to the one based on Proton when it arrives. As was mentioned in another thread, the JMS AMQP 1.0 client has certainly not been tuned for performance, so if you are looking to send millions of message per second or guarantee nanosecond latency, then it may not be for you. Overall all I can really say is that you should test it to see if it meets your particular functional and non-functional requirements. Hope this helps, Rob On 26 August 2014 08:17, Erik Aschenbrenner <[email protected]> wrote: > Dear Qpid users, > > so nobody has experiences with Qpid AMQP 1.0 JMS client in production > so far? > > Regards, > Erik > > > > -- > View this message in context: > http://qpid.2158936.n2.nabble.com/Experiences-with-Qpid-AMQP-1-0-JMS-c > lient-in-production-tp7611393p7612537.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
