Re: Documentation questions on qpid dispatch router

Thanks Ted, this is very helpful. cheers Noel On Wed, Jun 3, 2015 at 12:52 AM Ted Ross wrote: > On 06/02/2015 07:09 AM, Noel OConnor wrote: > > Hi, > > I'm going through the docs for the dispatch router and I've a few basic > > questions around entries the qdrouterd.conf file > > > > [1] In the

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Hi Robbie, yes my application uses a string generated with UUID.randomUUID().toString() as JMSCorrelationID for the generated request messages. The AMQP broker sets this ID to the response messages and so that my application can link the both messages. My current workaround is to remove the prefix

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Hi Erik, The difference comes about in part due to the new client implementing the AMQP JMS Mapping work progressing at the AMQP Bindings & Mappings TC at OASIS, while the old client does not. We aimed to allow the JMSMessageID and JMSCorrelationID handling to be able to handle the 4 different me

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Dear Qpid users, here is another difference I noticed between the old and the new client API: The correlation ID of a received message which can be obtained via (JMS) Message.getJMSCorrelationID() now has the prefix "ID:". So I had to change my code because my application uses this ID to map betw

Re: AmqpErrorException when receiving broadcast data

Great! I'm slightly curious as to what exactly the error was with the old client... but if the new client is working fine then I'd just stick with that. -- Rob On 4 June 2015 at 12:37, Erik Aschenbrenner wrote: > Dear Qpid users, > > if have tried the new proton based client and there seems to

Re: AmqpErrorException when receiving broadcast data

Dear Qpid users, if have tried the new proton based client and there seems to be no problems with decoding the received messages until now. Regards, Erik -- View this message in context: http://qpid.2158936.n2.nabble.com/AmqpErrorException-when-receiving-broadcast-data-tp7625647p7625825.html

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Dear Qpid users, thanks @all for helping. Regards, Erik -- View this message in context: http://qpid.2158936.n2.nabble.com/Changing-from-old-Qpid-JMS-client-to-Qpid-JMS-0-2-0-tp7625652p7625824.html Sent from the Apache Qpid users mailing list archive at Nabble.com.

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

On 4 June 2015 at 10:28, Robbie Gemmell wrote: > On 4 June 2015 at 08:01, Erik Aschenbrenner wrote: >> Ok thanks, >> >> I created my connection URI by using the new options now. >> >> First of all, I had to find out, that the URI option for the client ID has >> to be "jms.clientID" instead of "j

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

On 4 June 2015 at 08:01, Erik Aschenbrenner wrote: > Ok thanks, > > I created my connection URI by using the new options now. > > First of all, I had to find out, that the URI option for the client ID has > to be "jms.clientID" instead of "jms.clientId" which gives following > exception: > Nabbl

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

On 4 June 2015 at 10:12, Erik Aschenbrenner wrote: > Ok, if found out, that the problem is the the servers certificate doesn't > match is host name as described in this stackoverflow question >

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Ok, if found out, that the problem is the the servers certificate doesn't match is host name as described in this stackoverflow question . The CN (Common Name ) of the servers certificate is

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

Ok thanks, I created my connection URI by using the new options now. First of all, I had to find out, that the URI option for the client ID has to be "jms.clientID" instead of "jms.clientId" which gives following exception: This should be corrected in the client configuration documentation.