Re: qpid cpp 0.34 get sender user Id on receiver side when using SSL authentication

On 08/03/16 13:13, Gordon Sim wrote: On 08/03/16 12:55, Domen Vrankar wrote: I've changed the code and opened a issue report with patches: https://issues.apache.org/jira/browse/QPID-7130 Thanks very much Domen, I'll have a look at those as soon as I can! Domen, I've committed your patches.

RE: QPID CPP 0.34: Qpid Management Framework - CMake - path or missing file? HELP

Resolution to this issue is carefully setting ones PATH . I used the following command to identify the folders I needed in my path. python2.7 -v -c "import hashlib" 2> output.txt It comes in handy whenever one encounters a missing module. From: Alan

Re: QPID CPP 0.34: Qpid Management Framework - CMake - path or missing file? HELP

- Original Message - > From: "Alan Conway" > To: users@qpid.apache.org > Sent: Tuesday, March 8, 2016 1:57:24 PM > Subject: Re: QPID CPP 0.34: Qpid Management Framework - CMake - path or > missing file? HELP > > On Mon, 2016-03-07 at 20:29 +, Flores, Paul A.

Re: QPID CPP 0.34: Qpid Management Framework - CMake - path or missing file? HELP

On Mon, 2016-03-07 at 20:29 +, Flores, Paul A. wrote: > frustrating issue > > > > Any ideas? > > > > -- Regenerating Qpid Management Framework sources > Traceback (most recent call last): >   File "/home/pflores/Shop/qpid-cpp-0.34/managementgen/qmf-gen", line > 23, in > from

Re: QPID CPP 0.34: Interop Test Failure?

On Tue, 2016-03-08 at 16:57 +, Flores, Paul A. wrote: > What can I do to resolves these errors?   > > Can I ignore them? > > > interop_tests.CppTxTest.test_txtest2 > fail > .. >  BadProcessStatus: qpid-txtest2-2 Exit code 2: > qpid-txtest2: Transfer

Re: QPID JMS Test Hanging - How to resolve?

On 8 March 2016 at 17:18, Flores, Paul A. wrote: > Performing testing at client site and seeing the following test hang. > > > > Running > org.apache.qpid.jms.provider.amqp.message.AmqpJmsMessagePropertyIntercepterTest > > > > Is there a known resolution? Hi Paul, I've

QPID JMS Test Hanging - How to resolve?

Performing testing at client site and seeing the following test hang. Running org.apache.qpid.jms.provider.amqp.message.AmqpJmsMessagePropertyIntercepterTest Is there a known resolution?

RE: QPID CPP 0.34: Interop Test Failure?

What can I do to resolves these errors? Can I ignore them? interop_tests.CppTxTest.test_txtest2 fail .. BadProcessStatus: qpid-txtest2-2 Exit code 2: qpid-txtest2: Transfer agents failed interop_tests.PythonTxTest.test_tx_sequence

RE: QPID CPP 0.34: Interop Test Failure?

The tests try to pick an unused port, so 52652 is reasonable. > -Original Message- > From: Flores, Paul A. [mailto:paul.a.flo...@saic.com] > Sent: Tuesday, March 08, 2016 11:27 AM > To: users@qpid.apache.org > Subject: RE: QPID CPP 0.34: Interop Test Failure? > > Is the URL incorrect in

RE: QPID CPP 0.34: Interop Test Failure?

Is the URL incorrect in this particular test? ConnectError: Connect failed to amqp:tcp:127.0.0.1:52652: Reconnect disabled Shouldn't the port be 5672 and not 52652? From: Gordon Sim [g...@redhat.com] Sent: Tuesday, March 08, 2016 10:22 AM To:

Re: QPID CPP 0.34: Interop Test Failure?

On 08/03/16 15:43, Justin Ross wrote: It means one of the tests defined here is failing: https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_tests.py You should first determine which one is failing. Use the following command to run the test verbosely: ctest -R

Re: QPID CPP 0.34: Interop Test Failure?

It means one of the tests defined here is failing: https://github.com/apache/qpid/blob/trunk/qpid/cpp/src/tests/interop_tests.py You should first determine which one is failing. Use the following command to run the test verbosely: ctest -R '^interop_tests$' -VV And then see what it says.

QPID CPP 0.34: Interop Test Failure?

How do I resolve the single failing test; interop_test? More so what does this test failure mean? Any help is appreciated!

RE: QPID CPP 0.34: Qpid Management Framework - CMake - path or missing file? Fixed

Path issues From: Flores, Paul A. [paul.a.flo...@saic.com] Sent: Monday, March 07, 2016 2:29 PM To: users@qpid.apache.org Subject: QPID CPP 0.34: Qpid Management Framework - CMake - path or missing file? HELP frustrating issue Any ideas? --

Re: qpid cpp 0.34 get sender user Id on receiver side when using SSL authentication

On 08/03/16 12:55, Domen Vrankar wrote: I've changed the code and opened a issue report with patches: https://issues.apache.org/jira/browse/QPID-7130 Thanks very much Domen, I'll have a look at those as soon as I can! - To

Re: qpid cpp 0.34 get sender user Id on receiver side when using SSL authentication

>> Next I wanted to get user Id from connection >> (connection_.getAuthenticatedUsername()) but I always got "dummy" >> string. I traced that to SslConnector.cpp (getSecuritySettings >> function) where the string is hardcoded. Is there a way to get user id >> (certificate nickname) from this

AW: JMS client set headers, message and delivery annotations

Hi Robbie, Alright, thanks for the info. Best regards, Julien Avitech GmbH Engineering AxL Tel.: +49 (0)7541/282-177 Fax: +49 (0)7541/282-199 e-mail: julien.cha...@avitech.aero Avitech GmbH Principal Office: Bahnhofplatz 1 | 88045

Re: JMS client set headers, message and delivery annotations

The intent is to add such support eventually yes, but it hasn't happened yet and I am currently tied up with other things. There is some work needed to define the behaviour for the AMQP JMS mapping and implement it, I have raised https://issues.apache.org/jira/browse/QPIDJMS-153 to track things

AW: JMS client set headers, message and delivery annotations

Hi Robbie, Will that be added in future? Best regards, Julien Avitech GmbH Engineering AxL Tel.: +49 (0)7541/282-177 Fax: +49 (0)7541/282-199 e-mail: julien.cha...@avitech.aero Avitech GmbH Principal Office: Bahnhofplatz 1 | 88045

Re: JMS client set headers, message and delivery annotations

The newer Proton-based 'qpid-jms-client' AMQP 1.0 JMS client can't yet set MessageAnnotations or DeliveryAnnotations. The durable/priority/ttl fields of the Header section are set according to JMS producer semantics for delivery mode, priority, and expiration, with the delivery count field

AW: JMS client set headers, message and delivery annotations

Hi Rob, I'm using the new Qpid JMS client (org.apache.qpid: qpid-jms-client:0.8.0). Is there no possibility to set those with the new client? I found some hint to that in the org.apache.qpid.jms.provider.amqp.message.AmqpJmsMessageFacade, but I have no idea how to set them by JMS means, e.g.