Planning for an upcoming Qpid Python release

Hi, everyone. I plan to start the process in about a week. Current issues: https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20qpid-python-1.36.0%20AND%20project%20%3D%20QPID Candidate issues:

Re: C++ broker build not working: 'round' is not a member of 'std'

Thanks a lot. All seems to work fine now. Regards JAkub On Wed, Feb 15, 2017 at 10:23 PM, Kim van der Riet wrote: > Doh!!! > > ... and it was on the same line I just fixed :-( > > Ok, checked in an additional fix on master. > > > On 02/15/2017 02:33 PM, Jakub Scholz

Re: C++ broker build not working: 'round' is not a member of 'std'

Doh!!! ... and it was on the same line I just fixed :-( Ok, checked in an additional fix on master. On 02/15/2017 02:33 PM, Jakub Scholz wrote: Hi Kim, It looks like there is the same problem also with the log2 function. That seems to be the last one - when I work around it the compilation

Re: C++ broker build not working: 'round' is not a member of 'std'

Hi Kim, It looks like there is the same problem also with the log2 function. That seems to be the last one - when I work around it the compilation succeeds. So it looks like there is nothing else. Thanks & Regards Jakub

Re: C++ broker build not working: 'round' is not a member of 'std'

My error. I have replaced the offending statement with a more traditional version that should not require c++11. See QPID-7676. Kim On 02/14/2017 05:18 PM, Jakub Scholz wrote: Hi Alan, Thanks for your help. The -std=c++11 flag indeed helps to work around the problem. Thanks & Regards

Delivery settlement using Qpid proton 0.16.0 C++ bindings

Hello, We are experimenting the delivery settlement using Qpid proton C++ bindings. Is there a way to find out if the delivery is remotely settled? In our case, we want to implement client acknowledgment of a message like it is done in JMS. We want to be sure that, when our ‘acknowledge’

Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice

Thanks Alan, Do not hesitate if you have any comment or feedback. Regards, Adel From: Alan Conway Sent: Wednesday, February 15, 2017 4:41:06 PM To: users@qpid.apache.org Subject: Re: [Dispatch Router] Unexpected behavior when starting the

Re: [JMS] can I include ssl keystore & truststore in connectionfactory string

I did open the debug and that's the only error I can see. But still thanks. Do you know how to include the file location in windows? in the connection string? -- View this message in context:

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

On 15 February 2017 at 16:07, Robbie Gemmell wrote: > On 15 February 2017 at 14:15, Adel Boutros wrote: > > Hello guys, > > > > > > Based on the discussion, we are currently writing a Java API based on > JMS to configure the dispatch router. I

Re: [JMS] can I include ssl keystore & truststore in connectionfactory string

You appear to be specifying the trust store location twice, and no password, in your URI, which may or may not be related. The rest of the failure might give more details. It could simply be an issue with your certificates. Turning on the full Java SSL debug logging (-Djavax.net.debug=all) could

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

- Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org > Sent: Wednesday, February 15, 2017 10:07:07 AM > Subject: Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms > > On 15 February 2017 at 14:15, Adel Boutros

Re: [JMS] can I include ssl keystore & truststore in connectionfactory string

I tried to use org.apache.qpid.jms.jndi.JmsInitialContextFactory for SSL connection and use the keystore in connection string in jndi.properties as indicated: connectionfactory.SBCF = amqps://127.0.0.1:5271?transport.keyStoreLocation=keystoreLocation=test=truststoreLoc=truststore And here is the

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

On 15 February 2017 at 14:15, Adel Boutros wrote: > Hello guys, > > > Based on the discussion, we are currently writing a Java API based on JMS to > configure the dispatch router. I have so far managed to do the following: > > * Create, Read, Delete addresses > > * Create,

Re: [Qpid Dispatch] Manage Dispatch router from Qpid Jms

Hello guys, Based on the discussion, we are currently writing a Java API based on JMS to configure the dispatch router. I have so far managed to do the following: * Create, Read, Delete addresses * Create, Read, Delete connectors Config: Dispatch Router 0.7.0 JMS 0.11.1 And I have

Re: Connecting to durable consumer - Qpid Proton Python.

Thanks.  That was it.  I'm now suppressing the call to "receiver.close" when I've got a durable subscription. For anyone's future reference, my sample code is here ->  https://github.com/goochjs/python-activemq/blob/master/python-activemq/message_receiver.py J.   Jeremy Gooch

Re: Connecting to durable consumer - Qpid Proton Python.

On 15/02/17 11:26, Robbie Gemmell wrote: On 15 February 2017 at 11:06, Jeremy Gooch wrote: Hi Gordon, Many thanks - I thought it would be simple. Did I miss where this is documented? It is documented in

Re: Test framework for testing AMQP

For the Qpid JMS client we have a basic test peer that uses the 'Data' utility from proton-j to encode/decode representations of the various AMQP frames, validates things received match certain expectations we might have and responds with what we want it to. Its basic and not the nicest thing to

Re: Connecting to durable consumer - Qpid Proton Python.

On 15 February 2017 at 11:06, Jeremy Gooch wrote: > Hi Gordon, > Many thanks - I thought it would be simple. Did I miss where this is > documented? > With the change you've suggested in place, I notice that the subscription is > only durable when I ctrl-C my

Re: Connecting to durable consumer - Qpid Proton Python.

Hi Gordon, Many thanks - I thought it would be simple.  Did I miss where this is documented? With the change you've suggested in place, I notice that the subscription is only durable when I ctrl-C my script.  If it finishes normally then the subscription seems to be deleted.  Presumably this is

Re: Connecting to durable consumer - Qpid Proton Python.

On 15/02/17 09:05, Jeremy Gooch wrote: Hi, I'm trying to get a Qpid Proton Python v3.4 client to subscribe to an ActiveMQ broker over AMQP v1.0 as a durable consumer. I can create a durable subscription but don't quite understand how to pick up the same subscription the next time my script

Connecting to durable consumer - Qpid Proton Python.

Hi, I'm trying to get a Qpid Proton Python v3.4 client to subscribe to an ActiveMQ broker over AMQP v1.0 as a durable consumer.  I can create a durable subscription but don't quite understand how to pick up the same subscription the next time my script runs. After each run, the ActiveMQ admin