Re: Null Pointer exception in Qpid Java CLient 0.24
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-tp7599126p7599450.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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 expanded send operations in order to control that, JMS messages are persistent by default. Queue durability is a function of the destination string, and will default to true when using queue. definitions and can't be set otherwise, and default false when using destination. definitions where you must set it true if you need. For regular Topic subscriptions, the backing queues will always be non durable temporary queues tied to the lifecycle of the subscriber. DurableSubscriptions from the client wont work against the RabbitMQ broker as that functionality has always been dependant on the AMQP extension which caused the earlier problem creating regular consumers, and making it do otherwise would require breaking the JMS spec. /goes back to being on vacation Robbie On 14 October 2013 15:35, k.madnani84 k.madnan...@gmail.com wrote: 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-tp7599126p7599450.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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.org/jira/browse/QPID-5223. I gave the updates a test against RabbitMQ 3.1.5 and they seemed to do the trick. If you want to try them out, you can either give a fresh trunk checkout a try, find the relevant commits linked from the JIRAs to backport to an earlier release, or alternatively I made the nightly build job to run early so you can find the changes included there: https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/lastSuccessfulBuild/artifact/trunk/qpid/java/client/release/qpid-client-0.25.tar.gz Robbie On 9 October 2013 11:51, Robbie Gemmell robbie.gemm...@gmail.com wrote: 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 the 0.24 release, so using an older client release should rmeove that issue with the consumer. That said, if you are using a recent 3.x release of RabbitMQ you will likely then run into a different issue with producers, due to RabbitMQ now interpreting the message 'expiry' header in a different way than Qpid had for some time, instead using it as a ttl value. Coupled with the Qpid client sending an empty value for expiry rather than not setting it, this results in failure when sending messages. See https://issues.apache.org/jira/browse/QPID-5184 for more detail and changes that were commited to try and work around the issue, which you could backport to an older release. I will tro to take a look at removing use of the AMQP extension when connected to RabbitMQ in order to try and restore basic consumer capability, but I'm not likely to get to it until the weekend. Robbie On 7 October 2013 22:28, k.madnani84 k.madnan...@gmail.com wrote: 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 messages not getting published to it.I get the below error and its probably at createCOnsumer call Destination Created: direct://amq.direct/myqueue/myqueue?routingkey='myqueue'durable='true' javax.jms.JMSException: Error registering consumer: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.AMQSession.toJMSException(AMQSession.java:3494) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2039) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:1991) at org.apache.qpid.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:333) at org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.java:624) at org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102) at org.apache.qpid.client.AMQSession.createConsumerImpl(AMQSession.java:1989) at org.apache.qpid.client.AMQSession.createConsumer(AMQSession.java:939) at org.apache.qpid.example.Hello.runTest(Hello.java:59) at org.apache.qpid.example.Hello.main(Hello.java:40) Caused by: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:202) at org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:122) at org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:698) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:719) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:713) at org.apache.qpid.client.AMQSession_0_8.sendExchangeBound(AMQSession_0_8.java:428) at org.apache.qpid.client.AMQSession_0_8.access$100(AMQSession_0_8.java:62) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:410) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:407) at org.apache.qpid.client.failover.FailoverNoopSupport.execute(FailoverNoopSupport.java:67) at org.apache.qpid.client.AMQSession_0_8.isBound(AMQSession_0_8.java:405) at org.apache.qpid.client.AMQSession.registerConsumer(AMQSession.java:2873) at
Re: Null Pointer exception in Qpid Java CLient 0.24
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='testRoute'. The topic exchange that is this property: destination.topicExchange = amq.topic or destination.topicExchange = topic://amq.topic Still gives me null pointer.How are we going to deal with topics?What exchange have you used in your properties file for testing? Thanks Regards, Kuldip Madnani -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126p7599434.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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.lookupName = destination string format in the properties file, if you dont specify a prefix to the destination string the client will assume it is the default, i.e ADDR. For the first, you specified a BURL prefix. For the other two examples where you didnt specify any prefix which means it used the ADDR syntax, which as mentioned earlier in the thread is why it didn't work. You either have to specify the BURL prefix in your desintation strings, or you can change the default client-wide by setting a system property qpid.dest_syntax to the value BURL, i.e -Dqpid.dest_syntax=BURL, which would mean you wont need to specify it in the properties when using the destination. definitions. Depending on what you are actually trying to do you could use simpler queue. and topic. defiitions (which are treated as BURLs) in the properties. E.g: queue.queueLookupName = queuename This would cause the client to use a (durable) queue called 'queuename' bound to the 'amq.direct' exchange with 'queuename' as the binding key. topic.topicLookupName = topicname This would cause the client to use an auto-delete temporary queue called tmp_generated segment bound to the 'amq.topic' exchange with 'topicname' as the binding key (which might include a subscription pattern). It is probably worth noting that the 0-9-1 client path has historically been rather fixed in its use of the amq.direct exchange for queues, and the amq.topic exchange for topics. If you still can't get things working as you would like, in order to help us advise you it would be good if you outlined what messaging topology you are actually trying to achieve. Robbie On 14 October 2013 00:12, k.madnani84 k.madnan...@gmail.com wrote: 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='testRoute'. The topic exchange that is this property: destination.topicExchange = amq.topic or destination.topicExchange = topic://amq.topic Still gives me null pointer.How are we going to deal with topics?What exchange have you used in your properties file for testing? Thanks Regards, Kuldip Madnani -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126p7599434.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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 the 0.24 release, so using an older client release should rmeove that issue with the consumer. That said, if you are using a recent 3.x release of RabbitMQ you will likely then run into a different issue with producers, due to RabbitMQ now interpreting the message 'expiry' header in a different way than Qpid had for some time, instead using it as a ttl value. Coupled with the Qpid client sending an empty value for expiry rather than not setting it, this results in failure when sending messages. See https://issues.apache.org/jira/browse/QPID-5184 for more detail and changes that were commited to try and work around the issue, which you could backport to an older release. I will tro to take a look at removing use of the AMQP extension when connected to RabbitMQ in order to try and restore basic consumer capability, but I'm not likely to get to it until the weekend. Robbie On 7 October 2013 22:28, k.madnani84 k.madnan...@gmail.com wrote: 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 messages not getting published to it.I get the below error and its probably at createCOnsumer call Destination Created: direct://amq.direct/myqueue/myqueue?routingkey='myqueue'durable='true' javax.jms.JMSException: Error registering consumer: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.AMQSession.toJMSException(AMQSession.java:3494) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2039) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:1991) at org.apache.qpid.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:333) at org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.java:624) at org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102) at org.apache.qpid.client.AMQSession.createConsumerImpl(AMQSession.java:1989) at org.apache.qpid.client.AMQSession.createConsumer(AMQSession.java:939) at org.apache.qpid.example.Hello.runTest(Hello.java:59) at org.apache.qpid.example.Hello.main(Hello.java:40) Caused by: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:202) at org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:122) at org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:698) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:719) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:713) at org.apache.qpid.client.AMQSession_0_8.sendExchangeBound(AMQSession_0_8.java:428) at org.apache.qpid.client.AMQSession_0_8.access$100(AMQSession_0_8.java:62) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:410) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:407) at org.apache.qpid.client.failover.FailoverNoopSupport.execute(FailoverNoopSupport.java:67) at org.apache.qpid.client.AMQSession_0_8.isBound(AMQSession_0_8.java:405) at org.apache.qpid.client.AMQSession.registerConsumer(AMQSession.java:2873) at org.apache.qpid.client.AMQSession.access$400(AMQSession.java:98) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2016) ... 8 more Caused by: javax.jms.JMSException: Exception thrown against AMQConnection: Host: zldv0434.vci.att.com Port: 5672 Virtual Host: Client ID: zldv0434.vci.att.com Active session count: 1: org.apache.qpid.AMQDisconnectedException: Server closed connection and reconnection not permitted. at org.apache.qpid.client.AMQConnection.exceptionReceived(AMQConnection.java:1285) at org.apache.qpid.client.protocol.AMQProtocolHandler.closed(AMQProtocolHandler.java:270) at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.qpid.AMQDisconnectedException: Server closed connection and reconnection not permitted. ... 3 more Any idea what could fix it?? -- View this message in
Null Pointer exception in Qpid Java CLient 0.24
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 in case of RabbitMQ.My properties file is as such: java.naming.factory.initial = org.apache.qpid.jndi.PropertiesFileInitialContextFactory connectionfactory.qpidConnectionfactory = amqp://rbtadmin:b_ksw...@zldv0434.vci.att.com/?brokerlist='tcp://zldv0434.vci.att.com:5672' destination.topicExchange = amq.topic The code is: Properties properties = new Properties(); properties.load(this.getClass().getResourceAsStream(hello.properties)); Context context = new InitialContext(properties); ConnectionFactory connectionFactory = (ConnectionFactory) context.lookup(qpidConnectionfactory); Connection connection = connectionFactory.createConnection(); connection.start(); Session session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE); Destination destination = (Destination) context.lookup(topicExchange); MessageProducer messageProducer = session.createProducer(destination); -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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? - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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.BasicMessageProducer.init(BasicMessageProducer.java:136) at org.apache.qpid.client.BasicMessageProducer_0_8.init(BasicMessageProducer_0_8.java:53) at org.apache.qpid.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:550) at org.apache.qpid.client.AMQSession_0_8.createMessageProducer(AMQSession_0_8.java:62) at org.apache.qpid.client.AMQSession$7.execute(AMQSession.java:2611) at org.apache.qpid.client.AMQSession$7.execute(AMQSession.java:2602) at org.apache.qpid.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:333) at org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.java:624) at org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102) at org.apache.qpid.client.AMQSession.createProducerImpl(AMQSession.java:2600) at org.apache.qpid.client.AMQSession.createProducer(AMQSession.java:1176) at org.apache.qpid.client.AMQSession.createProducer(AMQSession.java:98) at org.apache.qpid.example.Hello.runTest(Hello.java:58) at org.apache.qpid.example.Hello.main(Hello.java:40) -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126p7599128.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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 in case of RabbitMQ.My properties file is as such: java.naming.factory.initial = org.apache.qpid.jndi.PropertiesFileInitialContextFactory connectionfactory.qpidConnectionfactory = amqp://rbtadmin:b_ksw...@zldv0434.vci.att.com/?brokerlist='tcp://zldv0434.vci.att.com:5672' destination.topicExchange = amq.topic This is speculative, but try changing the line above to destination.topicExchange=topic://amq.topic The older protocols I think still require the 'binding url' format, https://cwiki.apache.org/confluence/display/qpid/BindingURLFormat. It may be that the shortened form you use above is not parsed correctly. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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 g...@redhat.com 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 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 in case of RabbitMQ.My properties file is as such: java.naming.factory.initial = org.apache.qpid.jndi.**PropertiesFileInitialContextFa**ctory connectionfactory.**qpidConnectionfactory = amqp://rbtadmin:b_Ksw6w0@**zldv0434.vci.att.com/?** brokerlist='tcp://zldv0434.**vci.att.com:5672http://rbtadmin:b_ksw...@zldv0434.vci.att.com/?brokerlist='tcp://zldv0434.vci.att.com:5672 ' destination.topicExchange = amq.topic This is speculative, but try changing the line above to destination.topicExchange=**topic://amq.topic The older protocols I think still require the 'binding url' format, https://cwiki.apache.org/**confluence/display/qpid/**BindingURLFormathttps://cwiki.apache.org/confluence/display/qpid/BindingURLFormat. It may be that the shortened form you use above is not parsed correctly. --**--**- To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.**orgdev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: Null Pointer exception in Qpid Java CLient 0.24
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 messages not getting published to it.I get the below error and its probably at createCOnsumer call Destination Created: direct://amq.direct/myqueue/myqueue?routingkey='myqueue'durable='true' javax.jms.JMSException: Error registering consumer: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.AMQSession.toJMSException(AMQSession.java:3494) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2039) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:1991) at org.apache.qpid.client.AMQConnectionDelegate_8_0.executeRetrySupport(AMQConnectionDelegate_8_0.java:333) at org.apache.qpid.client.AMQConnection.executeRetrySupport(AMQConnection.java:624) at org.apache.qpid.client.failover.FailoverRetrySupport.execute(FailoverRetrySupport.java:102) at org.apache.qpid.client.AMQSession.createConsumerImpl(AMQSession.java:1989) at org.apache.qpid.client.AMQSession.createConsumer(AMQSession.java:939) at org.apache.qpid.example.Hello.runTest(Hello.java:59) at org.apache.qpid.example.Hello.main(Hello.java:40) Caused by: org.apache.qpid.AMQException: Woken up due to class javax.jms.JMSException at org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:202) at org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:122) at org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:698) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:719) at org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:713) at org.apache.qpid.client.AMQSession_0_8.sendExchangeBound(AMQSession_0_8.java:428) at org.apache.qpid.client.AMQSession_0_8.access$100(AMQSession_0_8.java:62) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:410) at org.apache.qpid.client.AMQSession_0_8$2.execute(AMQSession_0_8.java:407) at org.apache.qpid.client.failover.FailoverNoopSupport.execute(FailoverNoopSupport.java:67) at org.apache.qpid.client.AMQSession_0_8.isBound(AMQSession_0_8.java:405) at org.apache.qpid.client.AMQSession.registerConsumer(AMQSession.java:2873) at org.apache.qpid.client.AMQSession.access$400(AMQSession.java:98) at org.apache.qpid.client.AMQSession$4.execute(AMQSession.java:2016) ... 8 more Caused by: javax.jms.JMSException: Exception thrown against AMQConnection: Host: zldv0434.vci.att.com Port: 5672 Virtual Host: Client ID: zldv0434.vci.att.com Active session count: 1: org.apache.qpid.AMQDisconnectedException: Server closed connection and reconnection not permitted. at org.apache.qpid.client.AMQConnection.exceptionReceived(AMQConnection.java:1285) at org.apache.qpid.client.protocol.AMQProtocolHandler.closed(AMQProtocolHandler.java:270) at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:222) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.qpid.AMQDisconnectedException: Server closed connection and reconnection not permitted. ... 3 more Any idea what could fix it?? -- View this message in context: http://qpid.2158936.n2.nabble.com/Null-Pointer-exception-in-Qpid-Java-CLient-0-24-tp7599126p7599153.html Sent from the Apache Qpid developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
