Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-14 Thread Robbie Gemmell
The client sets the routing key for you, based on the Queue or Topic name you use. Message persistence isn't a function of the destination string, it is [optionally] controlled using the appropriate parameter on the expanded MessageProducer.send(..) operations defined by JMS. If you dont use the e

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-14 Thread k.madnani84
Thanks Robbie. Most of the format works for me. Just a question as to how do we set the routing key for message and make messages persistent in the BURL format? -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126p759945

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-13 Thread Robbie Gemmell
The 0-9-1 client path (which you are using by connecting to RabbitMQ) only understands the 'BindingURL' (BURL) destination syntax, and the client defaults to using the 'Address' (ADDR) syntax. When using the "destination. = " format in the properties file, if you dont specify a prefix to the destin

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-13 Thread k.madnani84
Hi Robie, First of all Thanks for the quick changes!!! It worked fine with the following modification in the properties file of the example provided along with the client: destination.queue = BURL:direct://myExchange//myQueue?autodelete='false'&durable='true'&internal='false'&routingkey='testRou

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-13 Thread Robbie Gemmell
I have made some changes via https://issues.apache.org/jira/browse/QPID-5224to enable basic consumer creation to succeed against RabbitMQ. I also tested the earlier producer-related changes from https://issues.apache.org/jira/browse/QPID-5184 and made some further change via https://issues.apache.o

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-09 Thread Robbie Gemmell
I had a look at this, and unfortunately it looks to be the result of the JMS client making use of a Qpid extension to AMQP which RabbitMQ doesn't support, leading it to close the connection when it is enountered. The particular usage of this extension causing the problem was added to the client in

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-07 Thread k.madnani84
Even using the above format throws me the exception: Destination Created: 'topic:'/'/amq.topic'; None java.lang.NullPointerException Therefore i tried to use queue and to my surprise i could see the queue got created in RabbitMQ broker but its not binded to the RabbitMQ Exchange 'amq.direct' and m

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-07 Thread Rajith Attapattu
Yes the older versions (pre 0-10) only works with Binding URL format. Rajith On Mon, Oct 7, 2013 at 1:35 PM, Gordon Sim wrote: > On 10/07/2013 05:51 PM, k.madnani84 wrote: > >> Hi, >> >> I am trying to use Qpid Java client 0.24 with RabbitMQ 3.1.5.I am getting >> a >> null pointer exception an

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-07 Thread Gordon Sim
On 10/07/2013 05:51 PM, k.madnani84 wrote: Hi, I am trying to use Qpid Java client 0.24 with RabbitMQ 3.1.5.I am getting a null pointer exception and i understand its because exchangeName is getting generated as null when i debug.But whats the reason? Is there something i need to mention extra i

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-07 Thread k.madnani84
Adding a print statement for Destination as well.Here is the stack trace: Destination Created: 'amq.topic'/None; None java.lang.NullPointerException at org.apache.qpid.client.BasicMessageProducer_0_8.declareDestination(BasicMessageProducer_0_8.java:61) at org.apache.qpid.client.Bas

Re: Null Pointer exception in Qpid Java CLient 0.24

2013-10-07 Thread Gordon Sim
On 10/07/2013 05:51 PM, k.madnani84 wrote: I am trying to use Qpid Java client 0.24 with RabbitMQ 3.1.5.I am getting a null pointer exception and i understand its because exchangeName is getting generated as null when i debug.But whats the reason? Do you have the backtrace of the exception? -