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:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20and%20component%20in%20(%27
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 wrote:
>
>> Hi Kim,
>>
>> It
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 su
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
/root/rpmbuild/BUILD/qpid-cpp-1.37.0/src/qpid/linearstore/MessageStoreImpl.c
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
Jakub
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’ me
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 same
dispatch route
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:
http://qpid.2158936.n2.nabble.com/JMS-can-I-include-ssl-keystore-truststore-in-connectionfactory-stri
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 have so far managed to do the
> following:
> >
> > *
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 al
- 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 wrote:
> > Hello guys,
> >
> >
> > Based on the
On Tue, 2017-02-14 at 20:35 +, Adel Boutros wrote:
> Hello,
>
>
> Was anyone able to take a look at the submitted patches?
I am just about to. Have been working on the proton side and on other
stuff lately but am going back to dispatch now. I will try to ensure
that your fixes either get com
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&transport.keyStorePassword=test&transport.trust
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, Read, Delete connectors
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 notice
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 http://goochgooch.co
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
http://qpid.apache.org/releases/qpid-proton-0.17.0/proton/python/book/overview.html#pro
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 us
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 script. If it finishes normally the
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
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 ru
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 co
22 matches
Mail list logo