Re: does qpid proton c++ support SASL SCRAM-SHA-256

[Gordon Sim]

A couple of suggestions:

- Try running `pluginviewer -c` to see if SCRAM-SHA-256 shows up as supported.
- Make sure e.g. using ccmake that your proton library is correctly
built to include sasl
- Turn on protocol tracing in order to see what mechanisms are
actually being offered by the server

On Wed, Mar 20, 2024 at 1:38 PM abdelrhman abdelhmaed
 wrote:
>
>  after installing Cyrus i get the following message when i try to
> connect to Broker:
>
>  amqp:unauthorized-access: Authentication failed [mech=SCRAM-SHA-256]
> std::string MECHANISM = "SCRAM-SHA-256";
> ConnectionOptions.sasl_allowed_mechs(MECHANISM);
> ConnectionOptions.sasl_allow_insecure_mechs(true);
> ConnectionOptions.sasl_enabled(true);
> ConnectionOptions.user("guest");
> ConnectionOptions.password("guest");
>
> when  i change the mechanism to PLAIN, the client connect the broker
> without any problem
> std::string MECHANISM = "PLAIN";
> ConnectionOptions.sasl_allowed_mechs(MECHANISM);
> ConnectionOptions.sasl_allow_insecure_mechs(true);
> ConnectionOptions.sasl_enabled(true);
> ConnectionOptions.user("guest");
> ConnectionOptions.password("guest");
>
> i have configured the broker to support both PLAIN and  SCRAM-SHA-256
>
> the broker.xml
>  
>  tcp://0.0.0.0:7014?saslMechanisms=PLAIN,
> SCRAM-SHA-256,tcpSendBufferSize=1048576;tcpReceiveBufferSize=1048576;protocols=AMQP;useEpoll=true;amqpCredits=1000;amqpLowCredits=300;amqpMinLargeMessageSize=102400;amqpDuplicateDetection=true
> 
>
>
> On 2024/03/19 07:57:31 abdelrhman abdelhmaed wrote:
> > Hi,
> > I am using the qpid proton library to connect to Broker( Apache ActiveMQ
> > Artemis).
> > The authentication mechanism must be  SALS SCRAM_SHA-256.
> > i tried to configure Qpid proton client to use this mechanism via the
> > following methods
> >
> > std::string MECHANISM = "SCRAM-SHA-256";
> > ConnectionOptions.sasl_allowed_mechs(MECHANISM);
> > ConnectionOptions.sasl_allow_insecure_mechs(true);
> > ConnectionOptions.sasl_enabled(true);
> > ConnectionOptions.user("guest");
> > ConnectionOptions.password("guest");
> >
> > but it dont work out. I got the following error message
> >
> > amqp:unauthorized-access: Authentication failed [mech=none]
> >
> > so my question wether qpid proton client support this mechanism and if
> so,
> > how i am supposed to configure it
> >


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: does qpid proton c++ support SASL SCRAM-SHA-256

[Gordon Sim]

On linux, proton uses the cyrus-sasl libraries. Different mechanisms
are often pacakged separately. So if on linux, check that you have the
right cyrus sasl plugin installed.

On Tue, Mar 19, 2024 at 11:33 AM abdelrhman abdelhmaed
 wrote:
>
> Hi,
> I am using the qpid proton library to connect to Broker( Apache ActiveMQ
> Artemis).
> The authentication mechanism must be  SALS SCRAM_SHA-256.
> i tried to configure Qpid proton client to use this mechanism via the
> following methods
>
> std::string MECHANISM = "SCRAM-SHA-256";
> ConnectionOptions.sasl_allowed_mechs(MECHANISM);
> ConnectionOptions.sasl_allow_insecure_mechs(true);
> ConnectionOptions.sasl_enabled(true);
> ConnectionOptions.user("guest");
> ConnectionOptions.password("guest");
>
> but it dont work out. I got the following error message
>
> amqp:unauthorized-access: Authentication failed [mech=none]
>
> so my question wether qpid proton client support this mechanism and if so,
> how i am supposed to configure it


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M18

[Gordon Sim]

+1 (built from source including running all tests, ran example against
dispatch router)

On Wed, Nov 1, 2023 at 2:32 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M18 Qpid protonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M18-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1270
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353499
>
> Regards
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>
>  
>staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1270
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M18
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M18
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Broker-J 9.1.0

[Gordon Sim]

+1 (checked signature and checksum, built from source including all
tests, configured broker via console, ran qpid::messaging, proton cpp
and proton python example programs against it)

On Wed, Aug 16, 2023 at 12:02 PM Tomas Vavricka  wrote:
>
> +1
>
> * verified signatures and checksum files
> * executed mvn apache-rat:check
> * executed the build and tests on JDK 11/17
> * started Qpid Broker-J from binary on JDK 11, created 
> queues/exchanges/ports/... via REST API
> * sent and received messages using Qpid JMS Client
>
> Tomas
>
> On 2023/08/14 10:03:47 Tomas Vavricka wrote:
> > Hi all,
> >
> > I built release artifacts for Qpid Broker-J version 9.1.0 RC1.
> > Please, give them a test out and vote accordingly.
> >
> > The source and binary archives can be found at:
> > https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc1/
> >
> > The maven artifacts are also staged at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> >
> > The new version brings a number of improvements and bug fixes.
> > You can find the full list of JIRAs included in the release here:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520=12353514
> >
> > Regards,
> > Tomas
> >
> > P.S. For testing of maven broker staging repo artifacts, please add
> > into to your project pom the staging repo as below:
> >
> > 
> > 
> >   staging
> >   
> > https://repository.apache.org/content/repositories/orgapacheqpid-1266/
> > 
> > 
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: session filter question

[Gordon Sim]

The c++ broker does not support that filter. The proton client should
be able to send it if you use that with service bus. There is an
example that shows how:
https://qpid.apache.org/releases/qpid-proton-0.39.0/proton/cpp/examples/service_bus.cpp.html

On Tue, Aug 1, 2023 at 4:31 AM 工作与生活  wrote:
>
> NowI'm using the Qpid Broker C++<1.39.0 with the Qpid Proton 
> <0.39.0 C API.
> I need a session filter function 
> like"com.microsoft:session-filter"in C++, but I haven't found the 
> relevant content in the API reference.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M17

[Gordon Sim]

+1 (checked signature and checksum, build from source including all
tests, ran example against router)

On Mon, Jul 31, 2023 at 3:37 PM Timothy Bish  wrote:
>
> Vote remains open awaiting another binding +1 from someone with time to
> give a quick review.
>
> On 7/25/23 11:49, Timothy Bish wrote:
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M17 Qpid protonJ2
> > release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M17-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1264
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353394
> >
> >
> > Regards
> >
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> >
> >   
> > 
> >   staging
> > https://repository.apache.org/content/repositories/orgapacheqpid-1264
> >
> > 
> >   
> >
> > The dependency for the protocol engine or the client itself would then
> > be:
> >
> >   
> > org.apache.qpid
> > protonj2
> > 1.0.0-M17
> >   
> >   
> > org.apache.qpid
> > protonj2-client
> > 1.0.0-M17
> >   
> >
> >
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Question : Download links not working

[Gordon Sim]

If you follow the link for whichever component you want from this
page: https://qpid.apache.org/releases/index.html#current-releases you
should get download links. I tried a couple and they worked for me.

On Thu, Jul 13, 2023 at 10:51 PM Paul Flores  wrote:
>
> Download links are not working.  Can someone forward me the link to the 
> correct web page?


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M16

[Gordon Sim]

+1, verified checksum and signature, built from source including all
tests, ran example against router

On Mon, Jun 26, 2023 at 6:05 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M16 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M16-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1261
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353206
>
> Regards
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>
>  
>staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1261
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M16
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M16
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.10.0

[Gordon Sim]

+1, checked checksum and signature, built from source with tests, ran
example against router

On Tue, Jun 27, 2023 at 3:40 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.10.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.10.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1262
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353303
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1262
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.10.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 2.4.0

[Gordon Sim]

+1, checked checksum and signature, built from source with tests, ran
example against router

On Tue, Jun 27, 2023 at 4:34 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.4.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.4.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1263
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12353304
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1263
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.4.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M9

[Gordon Sim]

+1, checked signature and checksum, ran the test script with no failures

On Fri, May 26, 2023 at 4:07 PM Timothy Bish  wrote:
>
> Hi folks, gentle reminder that this vote still remains open pending
> one additional binding +1
>
> On Mon, May 22, 2023 at 6:33 PM Timothy Bish  wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M9 Qpid
> > proton-dotnet release,
> > please give it a test out and vote accordingly.
> >
> > Tests can be run using the build script in the source archive:
> >
> > "./build.sh podman-test" or "./build.sh docker-test"
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M9-rc1/
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/projects/PROTON/versions/12353225
> >
> > Regards
> >
> > --
> > Tim Bish
> >
>
>
> --
> --
> Tim Bish
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 2.3.0

[Gordon Sim]

+1 (checked signature and checksum, build from source including
successful run through all tests, ran example against router 1.19.0)

On Wed, May 17, 2023 at 6:46 PM Robbie Gemmell  wrote:
>
> I have put together a spin for a 2.3.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.3.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1260
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352748
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1260
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.3.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.9.0

[Gordon Sim]

+1 (checked signature and checksum, build from source including
successful run through all tests, ran example against router 1.19.0)

On Wed, May 17, 2023 at 5:52 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.9.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The staged source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.9.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1259
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352747
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1259
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.9.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M8 (RC1)

[Gordon Sim]

+1, checked checksum and signature and ran the build script with
podman-test argument.


On Tue, May 9, 2023 at 6:22 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M8 Qpid
> proton-dotnet release,
> please give it a test out and vote accordingly.
>
> Tests can be run using the build script in the source archive:
>
> "./build.sh podman-test" or "./build.sh docker-test"
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M8-rc1/
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352669
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M15

[Gordon Sim]

+1 (Checked signature and checksum, built from source including tests
and ran example against 1.19.0 router)

On Tue, May 2, 2023 at 6:36 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M15 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M15-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1258
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12353134
>
> Regards
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>
>  
>staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1258
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M15
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M15
>
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13 (RC1)

[Gordon Sim]

On Mon, Mar 27, 2023 at 8:10 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M13 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M13-rc1/

+1, verified signature and checksum, built from source including
running of all tests, ran example against router.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M12

[Gordon Sim]

+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 9:35 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M12 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M12-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1254
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352532
>
> Regards
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>
>  
>staging
> https://repository.apache.org/content/repositories/orgapacheqpid-1254
>  
>
>
> The dependency for the protocol engine or the client itself would then be:
>
>
>  org.apache.qpid
>  protonj2
>  1.0.0-M12
>
>
>  org.apache.qpid
>  protonj2-client
>  1.0.0-M12
>
>
> {template}
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 2.2.0

[Gordon Sim]

+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 6:04 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 2.2.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/2.2.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1253
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352307
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1253
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 2.2.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.8.0

[Gordon Sim]

+1, checked checksum and signature, built from source, ran example
against latest router release

On Tue, Jan 10, 2023 at 5:11 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 1.8.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.8.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1252
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12352308
>
> Regards,
> Robbie
>
> P.S. If you want to test it out using maven (e.g with the examples
> src, or your own things), you can temporarily add this to your poms to
> access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1252
> 
>   
>
> The dependency for the client itself would then be:
>
>   
> org.apache.qpid
> qpid-jms-client
> 1.8.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M7

[Gordon Sim]

+1, verified checksum and signature, ran podman-test with no failures

On Mon, Dec 5, 2022 at 9:59 PM Timothy Bish  wrote:
>
> Hi folks,
>
> I have put together a release candidate for a 1.0.0-M7 Qpid
> proton-dotnet release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M7-rc1/
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/projects/PROTON/versions/12352533
>
> Regards
>
> --
> Tim Bish
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M6

[Gordon Sim]

+1

checked signature and checksum, ran `build.sh podman-test`, all passed

On Wed, Nov 9, 2022 at 1:25 PM Robbie Gemmell  wrote:
>
> On Tue, 8 Nov 2022 at 19:46, Timothy Bish  wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M6 Qpid
> > proton-dotnet release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/proton-dotnet/1.0.0-M6-rc1/
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352477
> >
> > Regards
> >
> > --
> > Tim Bish
> >
>
> +1
>
> I checked things over as follows:
> - Verified the signature + checksum files.
> - Checked for LICENCE + NOTICE files in the archives.
> - Used "mvn apache-rat:check" to verify headers in the source archive.
> - Ran the source build and tests in container, using "./build.sh
> podman-test", all passed.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M11

[Gordon Sim]

+1

checked signature and checksum, ran mvn install, untarred the target
and ran the example within it against qdrouterd 1.19

On Wed, Nov 9, 2022 at 2:55 PM Robbie Gemmell  wrote:
>
> On Tue, 8 Nov 2022 at 18:00, Timothy Bish  wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M11 Qpid ProtonJ2
> > release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M11-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1250
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12352473
> >
> > Regards
> >
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> >
> >
> >  
> >staging
> > https://repository.apache.org/content/repositories/orgapacheqpid-1250
> >  
> >
> >
> > The dependency for the protocol engine or the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  protonj2
> >  1.0.0-M11
> >
> >
> >  org.apache.qpid
> >  protonj2-client
> >  1.0.0-M11
> >
> >
> > --
> > Tim Bish
> >
>
> +1
>
> I checked things out as follows:
> - Verified the signature + checksum files.
> - Checked for LICENCE + NOTICE files in the archives.
> - Used "mvn apache-rat:check" to check headers in the source archive.
> - Ran the source build and tests on JDK 11.
> - Ran HelloWorld example against ActiveMQ Artemis 2.26.0 using the
> staged client bits on JDK 11.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpid c++ broker status

[Gordon Sim]

The proton bindings will certainly work against activemq artemis. The
brokers do have different semantic behaviours in some areas however,
so it really depends on how your broker is configured and what
behaviours you rely on.

On Mon, Oct 10, 2022 at 1:24 PM Jonathan Schaeffer
 wrote:
>
> Hello,
>
> would a migration from qpidd to artemis require changes on the clients ?
> Specifically, clients use python-qpid-proton bindings. Would we need to
> rewrite client's codes ?
>
> Cheers,
>
> On 10/10/22 10:32, Gordon Sim wrote:
> > ActiveMQ Artemis
>
> --
> Jonathan (ﾉ°益°)ﾉ 彡 [ɹǝɟɟǝɐɥɔS]
> Observatoire des Sciences de l'Univers de Grenoble
> Responsable technique Résif-DC
>  Isterre, bureau 035, 1381 rue de la Piscine 38610 GIERES
> ✆ +33 4 76 63 51 37


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpid c++ broker status

[Gordon Sim]

ActiveMQ Artemis is probably the most obvious choice as it has the
most ongoing activity.

The fact is, as you point out, the c++ broker is not being actively
maintained. Unless there are people willing to put in some time to do
that, I think it is better to be clear about how things stand.

On Mon, Oct 10, 2022 at 8:50 AM Михаил Иванов  wrote:
>
> Which broker then is supposed to be used instead?
>
> On 10.10.2022 10:31, Gordon Sim wrote:
> > In my opinion, in the absence of any volunteers able to spend some
> > amount of time on it, we should 'archive' it in some way (i.e. ensure
> > that the code remains available, but that it is clear from the website
> > etc that it is no longer maintained).
> >
> > On Sat, Oct 8, 2022 at 8:44 PM Michael Ivanov  wrote:
> >> Hallo,
> >>
> >> Is qpid c++ broker still alive? I see that last release reported on apache
> >> page is 1.39.0 from 2018 and last redhat rpm package I can find is for
> >> centos7/redhat7 only. When I try to build it on rocky9 it fails because
> >> of missing python2 packages.
> >>
> >> Best regards,
> >> --
> >> Michael Ivanov
> >
> > -
> > To unsubscribe, e-mail:users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail:users-h...@qpid.apache.org
> >


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpid c++ broker status

[Gordon Sim]

In my opinion, in the absence of any volunteers able to spend some
amount of time on it, we should 'archive' it in some way (i.e. ensure
that the code remains available, but that it is clear from the website
etc that it is no longer maintained).

On Sat, Oct 8, 2022 at 8:44 PM Michael Ivanov  wrote:
>
> Hallo,
>
> Is qpid c++ broker still alive? I see that last release reported on apache
> page is 1.39.0 from 2018 and last redhat rpm package I can find is for
> centos7/redhat7 only. When I try to build it on rocky9 it fails because
> of missing python2 packages.
>
> Best regards,
> --
> Michael Ivanov


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Benchmark comparison between Java broker and Cpp broker

[Gordon Sim]

I don't know of any existing benchmarks. However my advice would be to
just go ahead and move. If you are concerned, you can do some simple
benchmarking with your actual application, but I doubt there will be
any issue with performance.

On Wed, Oct 5, 2022 at 10:48 PM rammohan ganapavarapu
 wrote:
>
> Anyone have any ideas?
>
> On Tue, Sep 20, 2022 at 10:52 AM rammohan ganapavarapu <
> rammohanga...@gmail.com> wrote:
>
> > Hi,
> >
> > I have been using a CPP based qpid broker for a while and i am trying to
> > move to Java based broker, i just wanted to see if there are any
> > perf/benchmarking comparison between these two.
> >
> > Thanks,
> > Ram
> >


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpidd access with encryption required on

[Gordon Sim]

If you want to completely disable the 5672 port, use --listen-disable tcp.

The require-encryption option only works when authentication is enabled.

On Wed, Oct 5, 2022 at 4:14 PM Michael Ivanov  wrote:
>
> Greetings!
>
> I observed strange qpidd behavior. It is started from systemd with following
> command line:
>
> /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
>
> qpidd.conf contains following options:
>
> pid-dir=/var/run
> mgmt-enable=yes
> require-encryption=yes
> ssl-cert-db=/etc/qpid/certs
> ssl-cert-name=qpid.logit-ag.de
> ssl-port=5671
> auth=no
>
> Daemon listens on both ports (5671 and 5672) but when I try to access it
> using eg. qpid-tool -q I'm getting the expected results:
>
> qpid-stat -b amqps://localhost:5671 -q-- works
>
> qpid-stat -b amqp://localhost:5672 -q
>-- fails (as expected) with 'encryption required' error.
>
> One of my colleagues claimed that he was able to send a message successfully
> to this broker using *unencrypted* connection to port 5672. I captured the
> traffic to this broker and to my surprise I have seen a message in plain text,
> which was successfully delivered to receiver. He used this package to send
> the message:
>
> https://mvnrepository.com/artifact/org.apache.qpid/qpid-jms-client/2.0.0
>
> Now what do I miss in my qpidd configuration?
>
> qpidd version used is 1.39.0
>
> Best regards,
>
> --
>
> Michael Ivanov


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Use Qpid Messaging API to connect to a service bus queue

[Gordon Sim]

On Wed, Sep 7, 2022 at 8:13 AM Yuanyuan Feng
 wrote:
> Is it possible to use QPID messaging API to connect to a service bus 
> namespace and then send/receive messages to/from a queue on demand?

I don't believe anyone has ever done so.

In general I would advise against starting new projects using
qpid::messaging. It gets very little attention these days as proton is
the focus.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid Proton-J 0.34.0

[Gordon Sim]

+1, built from source including all tests

On Tue, Aug 30, 2022 at 7:24 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a Qpid Proton-J 0.34.0 release, please
> test it and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.34.0-rc1/
>
> The maven artifacts are staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1244
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12350696
>
> Regards,
> Robbie
>
> P.S. If you want to test things out using maven with your own build
> you can temporarily add this to your poms to access the staging repo:
>
>   
> 
>   staging
>   
> https://repository.apache.org/content/repositories/orgapacheqpid-1244
> 
>   
>
> The dependency for proton-j would then be:
>
>   
> org.apache.qpid
> proton-j
> 0.34.0
>   
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: How do I install and use Apache Qpid?

[Gordon Sim]

On Tue, Jul 26, 2022 at 3:29 PM Turritopsis Dohrnii Teo En Ming
 wrote:
> How do I install and use Apache Qpid?

Qpid comprises various different components. What component(s)
specifically are you interested in? I would advise going to
https://qpid.apache.org/ to find out more.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [C++] QPID Connection Closing after 60s

[Gordon Sim]

On Wed, Jul 6, 2022 at 2:26 PM Arjee Jacob  wrote:
>
> Thank you. Sorry, This may be a delayed response.
> We have qpidd running on the device as a server, and we have 4 clients.
> 3 clients are qpid C++ clients, using a qpid topic.
> And 1 Client is a python script, which uses qpid proton using the same
> topic.
> Would this be caused by qpid proton in python3 script, because only this
> script was the latest change.

I would not *expect* so, but I think you will need to do some
debugging to figure it out. E.g. if it is reproducible, run wireshark
to determine what is going on in terms of connections into the broker.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Apache QPID product support

[Gordon Sim]

I would not advise starting any project using the qpid messaging c++
api unless you are able and willing to invest time in maintaining the
code yourself. As far as the active development activity within qpid
is concerned, that api has been superceded by the proton c++ api.

On Fri, Jul 1, 2022 at 7:54 PM Guthrie, John M CIV USN NUWC DIV KPT WA
(USA)  wrote:
>
> Good afternoon,
>
> My workgroup uses the Qpid Messaging API C++, version 1.39.0.  My workgroup 
> needs more information about the level of software support.  What support is 
> provided for this product? Will this software be supported from roughly July 
> 25th, 2022 to July 24, 2023?  Any information is appreciated.  Thank you.
>
>
>
> V/r,
>
> John Guthrie
>
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: C++ Messaging AMQP 1.0 Topics

[Gordon Sim]

On Wed, Jun 29, 2022 at 4:53 PM Tiaan Wessels  wrote:
> Thanks. When a topic varies per message, would it not be better to be able
> to set it per message. With the current design it seems one would need to
> create a new session per message if you want to vary the topic? It seems
> the only address that can be set into a message is the reply-to if i am not
> mistaken.

In AMQP 1.0 a message has both a 'subject' and a 'to' field. The
subject can be set through qpid::messaging::Message::setSubject. The
to field must be set through a special property key, x-amqp-to. If/how
those to fields are used in routing a message depends on the broker in
use

The qpid::messaging API predates the AMQP 1.0 spec, so does not
directly support everything in 1.0. Generally the proton API for c++
is recommended for new 1.0 based applications.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: C++ Messaging AMQP 1.0 Topics

[Gordon Sim]

On Wed, Jun 29, 2022 at 1:45 PM Tiaan Wessels  wrote:
> When AMQP 1.0 is activated in a QPID Messaging API C++ program, what is the
> correct way to set the topic of a message to be sent to a broker ?
> The protocol is activated by protocol:'amqp1.0' in connection options.
> Also. is there a way to set the exchange to which the message should be
> delivered ?

AMQP 1.0 doesn't have the concept of exchange or topic. The address of
the sender or receiver indicates what 'thing' it should be delivered
to (AMQP 1.0 calls these 'nodes'). You can set a requested capability
alongside the address. In the qpid::messaging client you do that with
an address like this: foo; {node: {type: topic}}. Whether (and how)
the broker (or peer more generally) interprets that depends on what
you are connecting to.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M7

[Gordon Sim]

+1

- Verified signature and checksum
- Built from source including running tests
- Ran Hello World example against 1.19.0 router

On Tue, Jun 28, 2022 at 11:50 AM Robbie Gemmell
 wrote:
>
> On Mon, 27 Jun 2022 at 17:05, Timothy Bish  wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M7 Qpid ProtonJ2
> > release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M7-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1241
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12351788
> >
> > Regards
> >
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> >
> >
> >  
> >staging
> > https://repository.apache.org/content/repositories/orgapacheqpid-1241
> >  
> >
> >
> > The dependency for the protocol engine or the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  protonj2
> >  1.0.0-M7
> >
> >
> >  org.apache.qpid
> >  protonj2-client
> >  1.0.0-M7
> >
> >
> > --
> > Tim Bish
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> +1
>
> I checked things over as follows:
> - Verified the signature + checksum files.
> - Checked for LICENCE + NOTICE files in the archives.
> - Used "mvn apache-rat:check" to verify headers in the source archive.
> - Ran the source build and tests on JDK 17.
> - Ran HelloWorld example against Qpid Broker-J 8.0.6 using the staged
> client bits on JDK 17.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [C++] QPID Connection Closing after 60s

[Gordon Sim]

On a server, that log suggests that something is opening a socket to
the 5672 port, but then not actually transmitting anything over it.
E.g. it could be some kind of L4 probe.

On Mon, Jun 6, 2022 at 8:35 AM Arjee Jacob  wrote:
>
> Hey there,
>
> I am getting a message in my logs that says
> "[System] error Connection qpid.5672-No protocol received after 60s,
> closing"
>
> Any idea what this means? How to rectify it?
>
> Warm Regards,
> Jacob


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [TUTORIAL] Apache QpidProton | C/C++ | Python

[Gordon Sim]

Have you seen 
https://qpid.apache.org/releases/qpid-proton-0.37.0/proton/python/docs/tutorial.html
and 
https://qpid.apache.org/releases/qpid-proton-0.37.0/proton/cpp/api/tutorial_page.html
?

On Wed, Jun 1, 2022 at 5:45 AM Arjee Jacob  wrote:
>
> Dear all,
>
> I am not sure if this is the right forum to ask this question.
>  Are there any good resources where I can learn AMQP and QPID Proton from
> scratch on C/C++/Python?
> I am very new to the AMQP technology in general , and started with QPID
> proton. I am in the process of  implementing a few apps with AMQP adopted.
> I do see some examples on the Apache site, but I am finding it difficult to
> follow, as there are some ground zero level fundamentals about amqp that I
> am not familiar with.
>
> My target outcome is 2 things.
> 1. I want to be able to communicate between 2 processes (One written in
> python and One in C++ code) running on the same embedded device.
> 2, I want to be able to communicate between 2 embedded devices connected in
> the same network.
>
> If someone could point me to resources that show how AMQP works in general
> and how QPID Proton ties into all of this, it would be really helpful.
>
> What prompted me to ask in this forum is because, usually if I click on a
> method or object in the VS Code IDE, it takes me to the respective
> definitions of those objects/methods . But after importing the
> following(eg. Python)
>
> from proton.handlers import MessagingHandler
> from proton.reactor import Container
> from proton import Message
>
> I am not able to navigate(Ctrl+Left Click) to their definitions (Container,
> MessagingHandler, Message), as with other regular python modules.
>
> Any help is welcome since I am not sure how these things work at
> a fundamental level.
>
> Warm Regards,
> Jacob Jacob


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Tangent on approach to run example (was Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M6)

[Gordon Sim]

I built from source using `mvn clean package`, then I untar the
tarball in the target directory. That contains th examples with the
pom file, but maven complained about not finding a parent. This may be
the wrong approach but is essentially how I tested the previous
version and also the original protonj client. It ran fine when I just
included the jar file built in the source tree.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M6

[Gordon Sim]

+1, built from source including all tests and ran example against router

(My usual approach here did not work as the
apache-qpid-protonj2-1.0.0-M6-bin.tar.gz tarball which I 'install'
from after building did not have a top level maven project file, so
running maven against the examples failed. However I just used the
examples as built in the main source tree to run. Most likely this is
my stupidity with regard to maven, just mentioning incase something is
not as expected).

On Tue, May 24, 2022 at 2:18 PM Robbie Gemmell  wrote:
>
> On Mon, 23 May 2022 at 17:24, Timothy Bish  wrote:
> >
> > Hi folks,
> >
> > I have put together a release candidate for a 1.0.0-M6 Qpid ProtonJ2
> > release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M6-rc1/
> >
> > The maven artifacts are also staged for now at:
> > https://repository.apache.org/content/repositories/orgapacheqpid-1240
> >
> > The JIRAs assigned are:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12351559
> >
> > Regards
> >
> > P.S. If you want to test it out using maven (e.g with the examples
> > src, or your own things), you can temporarily add this to your poms to
> > access the staging repo:
> >
> >
> >  
> >staging
> > https://repository.apache.org/content/repositories/orgapacheqpid-1240
> >  
> >
> >
> > The dependency for the protocol engine or the client itself would then be:
> >
> >
> >  org.apache.qpid
> >  protonj2
> >  1.0.0-M6
> >
> >
> >  org.apache.qpid
> >  protonj2-client
> >  1.0.0-M6
> >
> >
> > --
> > Tim Bish
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> +1
>
> I checked things out as follows:
> - Verified the signature + checksum files.
> - Checked for LICENCE + NOTICE files in the archives.
> - Used "mvn apache-rat:check" to verify headers in the source archive.
> - Ran the source build and tests.
> - Ran HelloWorld example against Qpid Dispatch 1.19.0 and ActiveMQ
> Artemis 2.22.0 using staged client bits.
>
> Robbie
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: SSL Proxy

[Gordon Sim]

On Mon, May 23, 2022 at 5:05 PM Tiaan Wessels  wrote:
> Is it possible to connect with qpid messaging api c++ via ssl proxy to an
> AMQP broker?

It depends on the exact nature of the proxying. If the proxy uses SNI
information to route the connection, but leaves the encryption end to
end, that will certainly work. (That is used e.g. to access a broker
in openshift from outside the cluster, using a passthrough route).

If the proxy terminates the encryption, then tries to re-encrypt, it
may expect that the unencrypted content is HTTP, in which case it
would fail.

My advice would be to try it out with the proxy you envisage using.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Python Proton Binding on Receiver for Broker

[Gordon Sim]

On Thu, Apr 28, 2022 at 9:58 PM ONeil, Jerome  wrote:
> So that's grand.  I need to control the binding with more detail, though, and 
> for the life of me I can't figure out how to do it.  I've tried controlling 
> on the URL.  I've tried Filters and Selectors.  I have tried a variety of 
> different link and receiver properties (x-bindings, etc..) and other methods 
> scrapped up from the internet, and all I ever get for that binding is '#'.
>
> Can someone provide a simple example?  Lets say I wanted that binding to 
> actually be
>
> bind [jerome.#] => MyTopic
>
> What would that look like?  I am all out of clues and hope someone has one to 
> spare.

Attached is an example that sets the topic binding.
#!/usr/bin/env python
#
# Licensed to the Apache Software Foundation (ASF) under one
# or more contributor license agreements.  See the NOTICE file
# distributed with this work for additional information
# regarding copyright ownership.  The ASF licenses this file
# to you under the Apache License, Version 2.0 (the
# "License"); you may not use this file except in compliance
# with the License.  You may obtain a copy of the License at
#
#   http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied.  See the License for the
# specific language governing permissions and limitations
# under the License.
#

from __future__ import print_function, unicode_literals
from proton import Described, Message, symbol
from proton.reactor import Container, Filter
from proton.handlers import MessagingHandler

class SubjectFilter(Filter):
def __init__(self, value):
super(SubjectFilter, self).__init__({symbol('subject-filter'): Described(symbol('apache.org:legacy-amqp-topic-binding:string'), value)})

class Recv(MessagingHandler):
def __init__(self):
super(Recv, self).__init__()

def on_start(self, event):
conn = event.container.connect("anonymous@localhost:5672")
event.container.create_sender(conn, "amq.topic")
event.container.create_receiver(conn, "amq.topic", options=SubjectFilter("red.#"))

def on_sendable(self, event):
for i in ['red.panda', 'blue.whale', 'green.hornet', 'yellow.submarine', 'red.squirrel']:
event.link.send(Message(subject=i, body="this is a message with subject %s" % i))
event.link.close()

def on_message(self, event):
print(event.message.body)

try:
Container(Recv()).run()
except KeyboardInterrupt: pass




-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M5

[Gordon Sim]

On Tue, Apr 5, 2022 at 8:40 PM Timothy Bish  wrote:
> I have put together a release candidate for a 1.0.0-M5 Qpid ProtonJ2
> release,
> please give it a test out and vote accordingly.  I made a mistake and
> went a step
> to far when staging the maven bits and hit release instead of just
> closing the repository
> which means they were synced to the main maven repository,  I did quite
> a bit of testing
> beforehand so I'm hoping this one passes without issue.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M5-rc1/

+1 built from source including running all tests, ran HelloWorld
against dispatch router and qpidd


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Queue handling

[Gordon Sim]

On Thu, Mar 31, 2022 at 1:55 PM rahul.sin...@morganstanley.com
 wrote:
>
> Many thanks Gordon. I tried using the selector while creating the Receiver 
> for response queue (as per the example given 
> https://lists.apache.org/thread/95ozl3hxf0cqzt0nxgbvwroddx39kq1w)
> However, I get below exception -
> std::exception Link detached by peer with amqp:unauthorized-access: 
> AMQ119015: not authorized to create consumer, AMQ229032: User: FOOBAR does 
> not have permission='CREATE_ADDRESS' on address 'X.ResQueue_L'


That sounds like a question for your broker support group. (If they
need it, you can see the protocol trace from the client by setting env
var QPID_LOG_ENABLE="trace+:Protocol")


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Queue handling

[Gordon Sim]

On Thu, Mar 31, 2022 at 11:30 AM rahul.sin...@morganstanley.com
 wrote:
> 2) For the longer term/better solution, I will start looking into selector. 
> Is this within qpid C++ or proton layer. Any quick pointer will be highly 
> appreciated.

For proton C++:
https://github.com/apache/qpid-proton/blob/main/cpp/examples/selected_recv.cpp

For example with the old qpid::messaging API see e.g.
https://lists.apache.org/thread/95ozl3hxf0cqzt0nxgbvwroddx39kq1w


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Queue handling

[Gordon Sim]

On Thu, Mar 31, 2022 at 11:06 AM rahul.sin...@morganstanley.com
 wrote:
> How do we ensure the first receiver has released it? Is it invocation of 
> Session::acknowledge(msg) which makes it available to other receivers?

No, acknowledging the message will remove it permanently from the
queue. To release you need to use Session::relese(msg). However it is
always possible that the broker will allocate the same message to you
again, so there can be some inefficiency involved.

Are you able to use a selector? That way your receivers could select
only those messages with the appropriate value(s) for APPId.

> What difference will it make if we use Receiver::get() instead of 
> Receiver::fetch() ?

In this context none at all. The difference there is simply how the
client handles the case where it has no prefetched message available.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Queue handling

[Gordon Sim]

AMQP 1.0 doesn't really support what you are trying to do, which if I
understand it correctly, is to have many receivers peek at messages in
the queue and only remove those that are relevant to them. There is
the concept of a delivery mode, but no way to 'acquire' a copied
message. For the default 'move' distribution mode, on a shared queue,
a message will be allocated to one of the available receivers and from
that point will not be available to any other receiver until the first
receiver releases it.

The better pattern in my opinion is to have the broker filter the
messages into a separate response queue per receiver. Perhaps that is
per unique APPId in your case.

On Thu, Mar 31, 2022 at 9:39 AM rahul.sin...@morganstanley.com
 wrote:
>
> Hel
> We are using C++ API - qpid-cpp-1.39.0 and qpid-proton-0.34.0 and seems to 
> have an issue handling multiple instances of application (using different 
> implementations).
> The broker supplies all messages to our entity in 1 Response Queue and there 
> are uniqueAPPId to identify the messages received in Response Queue.
>
> However, at times, only 1 instance seems to get these messages. We suspect 
> it's the way we retrieve the messages from the queue. Our current logic is
> Using namespace qpid::messaging;
> Message msg;
> If(Receiver::fetch (msg, Duration(0)))
> {
> //process the message if unqiueAppId is ours
>
> //Acknowledge the message
>Session::acknowledge(msg);
> }
>
> Is this the correct way of handling the messages form Response Queue?
>
>
>   1.  We had a look at description for Receiver::get() and it indicates that 
> the message is retrieved from the Receiver's local Queue.
> For Receiver::fetch(), the description says "Retrieves the message from 
> Receiver's Subscription. Unlike get(), this message will check with the 
> server that there is no message for the subscription this
> Receiver is serving before returning false. Is the Receiver::fetch method 
> popping the message off the Response Queue as opposed to Receiver::get () 
> method.
>
>   1.  Whats the purpose of Session::acknowledge(msg) ? Does it pop the 
> message off the Response Queue.
>
> We want to only pull the message off the queue which are destined to our 
> instance. Otherwise, we don't want to remove them since this might affect 
> other instances.
>
> Please can you help in throwing some light on how to get this logic right.
>
> Best Regards,
> Rahul
>
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions 
> or views contained herein are not intended to be, and do not constitute, 
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform 
> and Consumer Protection Act. If you have received this communication in 
> error, please destroy all electronic and paper copies and notify the sender 
> immediately. Mistransmission is not intended to waive confidentiality or 
> privilege. Morgan Stanley reserves the right, to the extent required and/or 
> permitted under applicable law, to monitor electronic communications, 
> including telephone calls with Morgan Stanley personnel. This message is 
> subject to the Morgan Stanley General Disclaimers available at the following 
> link: http://www.morganstanley.com/disclaimers.  If you cannot access the 
> links, please notify us by reply message and we will send the contents to 
> you. By communicating with Morgan Stanley you acknowledge that you have read, 
> understand and consent, (where applicable), to the foregoing and the Morgan 
> Stanley General Disclaimers.
>
> You may have certain rights regarding the information that Morgan Stanley 
> collects about you. Please see our Privacy Pledge 
> https://www.morganstanley.com/privacy-pledge for more information about your 
> rights.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid Proton 0.37.0 (RC2)

[Gordon Sim]

On Tue, Mar 15, 2022 at 5:40 PM Robbie Gemmell  wrote:
> I have put together another spin for a Qpid Proton 0.37.0 release,
> please give it a test out and vote accordingly.
>
> The files can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/proton/0.37.0-rc2/

I checked signature and checksum, built from source, ran tests against
it, ran example against router (also built against this rc).

Apart from c-fdlimits-tests all looked ok. Assuming those more
familiar with that test and its history understand the issue with the
test and it is of no concern to them, I am happy to vote +1 on the
release.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Dispatch Router 1.19.0 (RC2)

[Gordon Sim]

On Thu, Mar 17, 2022 at 1:14 AM Ken Giusti  wrote:
> Please cast your vote on this thread to release RC2 as the official
> Qpid Dispatch Router version 1.19.0.
>
> RC2 of Qpid Dispatch Router version 1.19.0 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.19.0-rc2/

+1 (checked signature and checksum, built from source against proton
0.37.0 candidate, ran all tests[1], installed and ran selected python
and cpp examples against it)

[1] I get a failure in the python checker for 3.8 as I am on 3.6, but
otherwise everything passed.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid Proton 0.37.0 (RC2)

[Gordon Sim]

On Fri, Mar 18, 2022 at 9:35 AM Jiri Daněk  wrote:
>
> On Fri, Mar 18, 2022 at 10:20 AM Roddie Kieley  wrote:
>
> > Has anyone else been testing with python 3.10? I see that we specify
> > python 3.6+ as per:
> >
> > -- Found Python: /usr/bin/python3.10 (found suitable version "3.10.0",
> > minimum required is "3.6") found components: Interpreter Development
> > Development.Module Development.Embed
> >
> > but on Fedora 34 with python 3.10 installed and built using gcc I see that
> > the c-fdlimits-tests fail intermittently. With clang 12.0.1 + python 3.10
> > the list of failures is larger and more consistent. Should we expect this
> > to be a python 3.10 to be usable at the moment? If this is not an issue
> > specific to my environment, are we able to release note it?
> >
>
> Python 3.10 is default on Fedora 35 as well, so I expect most people here
> will use this version of Python.
>
> Does the fdlimits failure look anything like the former problems with the
> test?
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PROTON%20AND%20text%20~%20c-fdlimits-tests
>
> What are the other failures? Could it be that newer Python is more
> sensitive to detecting resource leaks?

That test fails for me with 3.6 (every time so far). I get lots of
resource warnings then an assertion failure:

6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning:
subprocess 849819 is still running
6:   _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6: /usr/lib64/python3.10/subprocess.py:1067: ResourceWarning:
subprocess 850082 is still running
6:   _warn("subprocess %s is still running" % self.pid,
6: ResourceWarning: Enable tracemalloc to get the object allocation traceback
6:
6: ==
6: FAIL: test_fd_limit_broker (__main__.FdLimitTest)
6: Check behaviour when running out of file descriptors on accept
6: --
6: Traceback (most recent call last):
6:   File 
"/home/gordon/releases/proton/0.37.0/qpid-proton-0.37.0/c/tests/fdlimit.py",
line 77, in test_fd_limit_broker
6: self.assertNotEqual(sender.poll(), 0)
6: AssertionError: 0 == 0
6:
6: --
6: Ran 1 test in 2.101s
6:
6: FAILED (failures=1)
1/1 Test #6: c-fdlimit-tests ..***Failed2.18 sec


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid C++ Broker Segfault

[Gordon Sim]

On Tue, Feb 8, 2022 at 8:11 PM Pete Fawcett  wrote:
> Would you prefer that I submit a Pull Request for the current fixes or wait
> until further changes are made?

Either way


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid C++ Broker Segfault

[Gordon Sim]

On Fri, Jan 14, 2022 at 10:36 AM Pete Fawcett  wrote:
> I tried this but it didn't, initially, fix the problem.
> It turns out that the current exception handling is causing the link to be
> closed from within Connection object doDeliveryUpdated
> 
> Calling Session::abort_pending() from there meant changing abort_pending()
> to be a public function, which makes me wonder if it is the right thing to
> be doing.
> Making the change, and calling abort_pending() before closing the link in
> doDeliveryUpdated, did remove the pending items and so prevent the Segfault.

You could also put a try/catch in Session::readable[1], and call
abort_pending before rethrowing. (Or later, send back a nack for the
message instead of rethrowing for certain errors).

[1] 
https://github.com/apache/qpid-cpp/blob/main/src/qpid/broker/amqp/Session.cpp#L697


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid C++ Broker Segfault

[Gordon Sim]

On Thu, Jan 6, 2022 at 8:56 PM Pete Fawcett  wrote:
> *Questions:*
>
> Firstly, a simple work around is to check the link pointer when moving
> delivery pointers from 'pending' to completed and discarding them if the
> 'link' is NULL . Does this suffice?

I think that would probably work. However it would be nicer to
actually remove them from pending before they were invalidated. Does
calling abort_pending() for the link before closing it in
https://github.com/apache/qpid-cpp/blob/main/src/qpid/broker/amqp/Session.cpp#L764
prevent the segfault?

> Secondly, does the link need to be cleared just because a message is too
> big for the queue? Can it not be signalled back to the sender in a less
> drastic manner? (Dropping the link means it is likely for numerous messages
> to be repeatedly delivered when using "at least once" delivery)

The message could be rejected. (I think that would involve changing
the exception handling at
https://github.com/apache/qpid-cpp/blob/main/src/qpid/broker/amqp/Session.cpp#L948
to not throw but to simply reject the message).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.60.1

[Gordon Sim]

On Wed, Dec 15, 2021 at 5:31 PM Robbie Gemmell  wrote:
> I have put together a spin for a 0.60.1 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.60.1-rc1/

+1, verified signature and checksum, built from source including
tests, ran example against c++ broker


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.4.1

[Gordon Sim]

On Wed, Dec 15, 2021 at 4:50 PM Robbie Gemmell  wrote:
> I have put together a spin for a 1.4.1 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.4.1-rc1/


+1, verified signature and checksum, built from source including
tests, ran example against c++ broker


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.4.0

[Gordon Sim]

On Mon, Dec 13, 2021 at 6:32 PM Robbie Gemmell  wrote:
> I have put together a spin for a 1.4.0 Qpid JMS client release, please
> give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.4.0-rc1/

+1

* verified checksum and signature
* built from source including all tests
* ran example against router and c++ broker


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: visiblity of selectors im use on C++ broker

[Gordon Sim]

On Tue, Nov 30, 2021 at 12:26 PM Andy Gibson  wrote:
> My team are currently in the process of replacing header bindings with 
> selectors. We're using a python3 proton client and the C++ qpid broker.
> We're used to being able to use the QMF console to see what header bindings 
> are being used to understand the data being routed.
>
> Whilst selectors are operating as expected, I can't find any means to 
> determine the selector being used for a queue.
> I've had a look in the QMF console, through the QMF api and using the 
> management tools on the broker.
>
> Is there any mechanism for establishing the details of selectors in use?

Unfortunately not.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Dispatch Router 1.18.0 (RC1)

[Gordon Sim]

On Tue, Nov 16, 2021 at 9:36 PM Ken Giusti  wrote:
> Please cast your vote on this thread to release RC1 as the official
> Qpid Dispatch Router version 1.18.0.
>
> RC1 of Qpid Dispatch Router version 1.18.0 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.18.0-rc1/

+1


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Setting application properties on Message with Qpid Proton Python

[Gordon Sim]

On Tue, Nov 16, 2021 at 12:17 PM Kai  wrote:
> I am trying to set some application properties on a message to be sent
> using Qpid Python 0.36 using the following code:
> msg = Message(
> body="the body",
> properties={
> "status": 200
> },
> address="reply-to-address",
> correlation_id="correlationId",
> content_type="text/plain"
> )
>
> when I send this message then at the consumer side I am not able to
> retrieve the "status" from the message's application properties.

It works for me (sending message above, I can print out the properties
in a receiver and see the status set as expected). If you run the
python program with PN_TRACE_FRM=1, what do you see for the transfer
content?


(I see 
"\x00SpE\x00Ss\xd0\x00\x00\x005\x00\x00\x00\x07@@\xa1\x10reply-to-address@@\xa1\x0dcorrelationId\xa3\x0atext/plain\x00St\xd1\x00\x00\x00\x15\x00\x00\x00\x02\xa1\x06status\x81\x00\x00\x00\x00\x00\x00\x00\xc8\x00Sw\xa1\x08the
body" using

#!/usr/bin/env python

from proton import Message
from proton.handlers import MessagingHandler
from proton.reactor import Container

class Test(MessagingHandler):
def __init__(self, url):
super(Test, self).__init__()
self.url = url
self.sent = False

def on_start(self, event):
event.container.create_sender(self.url)
event.container.create_receiver(self.url)

def on_sendable(self, event):
if not self.sent:
msg = Message(
body="the body",
properties={
"status": 200
},
address="reply-to-address",
correlation_id="correlationId",
content_type="text/plain"
)
event.sender.send(msg)
self.sent = True

def on_message(self, event):
print("properties:", event.message.properties)
print("body:", event.message.body)
event.receiver.close()
event.connection.close()

def on_accepted(self, event):
event.connection.close()

try:
Container(Test("localhost/examples")).run()
except KeyboardInterrupt:
pass


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Receive from wildcard address

[Gordon Sim]

On Mon, Nov 15, 2021 at 6:32 PM Alec Liu  wrote:
> Is there anyway that for a client program which linking with a qpid
> dispatch to receive all messages for different addresses? Like using some
> kind of wildcard address, etc.

No, wildcard based routing is not supported at this time.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Interop Test 0.3.0

[Gordon Sim]

+1 (build as a container and ran all tests)

On Thu, Oct 28, 2021 at 9:36 PM Kim van der Riet  wrote:
>
> Hi,
>
> I have assembled a release of Qpid Interop Test 0.3.0. The proposed release
> (RC1) is available at:
> https://dist.apache.org/repos/dist/dev/qpid/interop-test/0.3.0-rc1/
>
> Issues included in this release are listed at
> https://issues.apache.org/jira/browse/QPIDIT-143?jql=project%20%3D%20QPIDIT%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%200.3.0%20ORDER%20BY%20updated%20DESC
> .
>
> Please test and vote by replying to this list.
>
> The JIRA for this project is at https://issues.apache.org/jira/browse/QPIDIT
> .
>
> Qpid Interop Test is a set of Qpid client interoperability tests. It sends
> and receives messages between combinations of the Qpid clients to ensure
> they work correctly with each other.
>
> See the QUICKSTART.md file in the root directory for building and running
> the tests, either natively or in a container.
>
> Thank you for your time,
> Kim van der Riet


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Dispatch Router 1.17.1 (RC1)

[Gordon Sim]

On Thu, Oct 28, 2021 at 10:30 PM Ken Giusti  wrote:
> Please cast your vote on this thread to release RC1 as the official
> Qpid Dispatch Router version  1.17.1.
>
> RC1 of Qpid Dispatch Router version 1.17.1 can be found here:
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.17.1-rc1/
>
> To validate the integrity and signature of the tar file please follow
> the instructions on the Downloads page from the qpid.apache.org
> website:
> https://qpid.apache.org/download.html#verify-what-you-download
>
> The fixed JIRAs included in this release are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315321=12350729
>
> It is tagged as 1.17.1-rc1.

+1 (verified checksum and signature, ran tests and installed, ran
python examples and qdstat against router, ran through skupper CI)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

1.17.1?

[Gordon Sim]

I would like to suggest a possible bug fix release, 1.17.1. I have two
fixes I would like to include in that - DISPATCH-2257 and
DISPATCH-2259 - in order to make those fixes available more easily to
those who need them before the 0.18.0 release. Any other bugs anyone
feels could/should be included?


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Python BlockingReceiver accept() fails when used with qpidd broker

[Gordon Sim]

This is because you are setting 'examples' to be a topic exchange, and
so the messages sent are pre-settled by default (which the example
application is not checking before trying to accept). The example is a
simple one intended to work with a queue (or queue like thing).

On Wed, Oct 13, 2021 at 11:16 PM Majszak, Gregory J
 wrote:
>
> ./qpidTest.bash script:
> #!/usr/bin/env bash
>
> function main() {
>   # Display Linux distro
>   echo "Linux distro:"
>   cat /etc/*release*
>   echo
>
>   # Display Linux version
>   echo "Linux version:"
>   cat /proc/version
>   echo
>
>   # Display Python 3 version
>   echo "Python3 version:"
>   python3 --version
>   echo
>
>   # Display C++ Qpid qpidd broker version
>   echo "C++ Qpid qpidd broker version:"
>   qpidd --version
>   echo
>
>   echo "Run of Qpid Python 3 example broker and helloworld_blocking scripts:"
>
>   # Start and background Python 3 example Qpid broker
>   python3 ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/broker.py &
>   local brokerPid=${!}
>
>   # Allow some time for Python 3 example Qpid broker to get up and running
>   sleep 1
>
>   # Run helloworld_blocking.py (note no error, receiver.accept() performs as 
> expected)
>   if [[ "Hello World!" == $(python3 
> ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/helloworld_blocking.py) 
> ]]; then
> echo "Completed without error"
>   else
> echo "Command 'python3 
> ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/helloworld_blocking.py' 
> failed"
>   fi
>
>   # Stop background Python 3 example Qpid broker
>   kill ${brokerPid}
>   echo
>
>   echo "Run of C++ Qpid qpidd broker and helloworld_blocking script:"
>
>   # Start and background C++ Qpid qpidd broker
>   qpidd &
>   brokerPid=${!}
>
>   # Allow some time for C++ Qpid qpidd broker to get up and running
>   sleep 1
>
>   # Add exchange topic 'examples'
>   qpid-config add exchange topic examples '*' || {
> echo "Command 'qpid-config add exchange topic examples '*'' failed"
>   }
>
>   # Run same helloworld_blocking.py (note error, receiver.accept() fails with 
> 'IndexError: pop from an empty deque')
>   # If 'receiver.accept()' is commented out from helloworld_blocking.py, 
> command succeeds and returns 'Hello World!'
>   # but message is 'leaked' and/or stored/queued awaiting acceptance
>   if [[ "Hello World!" == $(python3 
> ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/helloworld_blocking.py 
> || echo "${?}") ]]; then
> echo "Completed without error"
>   else
> echo "'python3 
> ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/helloworld_blocking.py' 
> failed"
>   fi
>
>   # Stop background C++ Qpid qpidd broker
>   kill ${brokerPid}
> }
>
> main "${@}"
>
> exit
>
>
> ./qpidTest.bash script run output:
> [gmajszak@xxx-u-dev-wks20 ~]$ ./qpidTest.bash
> Linux distro:
> NAME="Red Hat Enterprise Linux Workstation"
> VERSION="7.6 (Maipo)"
> ID="rhel"
> ID_LIKE="fedora"
> VARIANT="Workstation"
> VARIANT_ID="workstation"
> VERSION_ID="7.6"
> PRETTY_NAME="Red Hat Enterprise Linux Workstation 7.6 (Maipo)"
> ANSI_COLOR="0;31"
> CPE_NAME="cpe:/o:redhat:enterprise_linux:7.6:GA:workstation"
> HOME_URL=https://www.redhat.com/
> BUG_REPORT_URL=https://bugzilla.redhat.com/
>
> REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
> REDHAT_BUGZILLA_PRODUCT_VERSION=7.6
> REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
> REDHAT_SUPPORT_PRODUCT_VERSION="7.6"
> Red Hat Enterprise Linux Workstation release 7.6 (Maipo)
> Red Hat Enterprise Linux Workstation release 7.6 (Maipo)
> cpe:/o:redhat:enterprise_linux:7.6:ga:workstation
>
> Linux version:
> Linux version 3.10.0-1160.45.1.el7.x86_64 
> (mockbu...@x86-vm-37.build.eng.bos.redhat.com)
>  (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Fri Sep 24 
> 10:17:16 UTC 2021
>
> Python3 version:
> Python 3.6.8
>
> C++ Qpid qpidd broker version:
> qpidd (qpid-cpp) version 1.39.0
>
> Run of Qpid Python 3 example broker and helloworld_blocking scripts:
> Completed without error
>
> Run of C++ Qpid qpidd broker and helloworld_blocking script:
> 2021-10-13 15:04:53 [Broker] notice Broker (pid=4832) start-up
> 2021-10-13 15:04:53 [Security] notice SSL plugin not enabled, you must set 
> --ssl-cert-db to enable it.
> 2021-10-13 15:04:53 [Store] notice Linear Store: Store module initialized; 
> store-dir=/home/gmajszak/.qpidd
> 2021-10-13 15:04:53 [Network] notice Listening on TCP/TCP6 port 5672
> ./qpidTest.bash: line 3:  4827 Terminated  python3 
> ~/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/broker.py
> Traceback (most recent call last):
>   File 
> "/home/gmajszak/Downloads/Qpid_Proton_0.35.0/Proton_Python_Examples/helloworld_blocking.py",
>  line 32, in 
> receiver.accept()
>   File "/usr/lib64/python3.6/site-packages/proton/_utils.py", line 248, in 
> accept
> self.settle(Delivery.ACCEPTED)
>   File "/usr/lib64/python3.6/site-packages/proton/_utils.py", line 

Re: qpid messaging api to activemq topic

[Gordon Sim]

On Wed, Sep 29, 2021 at 1:25 AM EXT-Walsh, Jody R
 wrote:
> I am able to connect and send to a queue. To send to a topic, I need to 
> prefix the address with "topic://", but this is not accepted by the qpid 
> messaging api.

You need to add inner quotes around the topic, so e.g. "'topic://my-topic'"


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Azure event hub checkpointing with Qpid proton C++ API

[Gordon Sim]

On Wed, Sep 22, 2021 at 8:11 PM Adrian Florea  wrote:
> You can take a look at:
>
> https://azure.github.io/amqpnetlite/articles/azure_eventhubs.html
>
> Look at the "Filter" section.

For an example of setting a filter with proton c++:
https://github.com/apache/qpid-proton/blob/main/cpp/examples/selected_recv.cpp#L38

There is no example for setting message annotations, but it is similar
to setting properties,
https://github.com/apache/qpid-proton/blob/main/cpp/examples/colour_send.cpp#L64,
except instead of the properties() method you use
message_annotations() as per
https://qpid.apache.org/releases/qpid-proton-0.35.0/proton/cpp/api/classproton_1_1message.html#a5d96699458d8be84d821f5651a7b3717


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Azure event hub checkpointing with Qpid proton C++ API

[Gordon Sim]

On Wed, Sep 22, 2021 at 6:54 PM Arun Koshal  wrote:
> I plan to use Apache qpid proton C++ API for receiving messages from Azure
> Event hub. I am able to implement a client and fetch the events. The
> problem is, whenever I restart my clients it reads all the events from the
> event hub.
>
> A quick search revealed that Event hub provides stream offset with the
> events sent to the readers which the reader can remember. The reader can
> start reading from a new offset which it hasn't read so far.

What is the mechanism in AMQP terms by which that is done? E.g. is it
a link property, a filter, ?

> I did a lot of searching in Qpid proton code and the C++ API, but could not
> find a way to get the following:
> 1. the offset value when a message is received from event hub
> 2. a way to specify the offset from which to start reading messages, while
> opening a receiver


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Random "local-idle-timeout expired" disconnections with Qpid Proton C++

[Gordon Sim]

Is the broker disconnecting the client with the timed out error? Or is
it the client disconnecting from the broker?

My initial thought was that
https://issues.apache.org/jira/browse/PROTON-2422 might be relevant,
but that results in heartbeats *not* being sent by proton. Did you
notice any such gap before disconnection? If not, i.e. if heartbeats
are being sent correctly but one side is still timing out, that
suggests the bug is on that side. (The fact that a vanilla broker
works would suggest that the other broker might have an issue (e.g.
older version of proton within it?), unless that is coincidental).

On Thu, Sep 2, 2021 at 9:30 AM Francesco Raviglione
 wrote:
>
> Dear all,
> I am writing as I am experiencing an issue with Qpid Proton and some
> specific AMQP brokers.
> In particular, I am currently using Qpid Proton 0.33.0 (the C++ version) in
> a project. In order to set up the client, I based my code on the examples
> available in the official documentation (like
> https://qpid.apache.org/releases/qpid-proton-0.33.0/proton/cpp/api/simple_recv_8cpp-example.html
> ).
> My client should subscribe to a specific topic and then wait for new
> messages (it is expected to be a "receive-only" AMQP client), which may
> come at a very fast rate, but which may also not come for several minutes
> or hours (and, in this case, it should remain connected to the broker
> waiting for the moment in time in which new messages will come).
> With some AMQP brokers (in particular, with an almost vanilla Apache
> ActiveMQ version), everything is working properly, even if I do not set any
> idle timeout with "co.idle_timeout(proton::duration());". If
> I do not set a connection idle timeout, I can see my client sending to the
> broker empty heartbeat messages with a periodicity of 7.5 seconds (probably
> due to some settings in the broker which require this periodicity to
> consider the client up and running). If, instead, I set a co.idle_timeout,
> I also see the broker sending me empty heartbeat messages at a periodicity
> equal to 1/4 of the idle timeout, which is what I am expecting.
> However, with some other AMQP brokers (in particular, with a custom broker
> based on ActiveMQ), I experience, after a completely variable amount of
> time (spanning from few minutes to several hours), a disconnection, with
> the error:
> "amqp:resource-limit-exceeded: local-idle-timeout expired"
> Setting any local idle timeout with "co.idle_timeout()" (including 100,
> 1000, FOREVER and several other options) does not seem to solve the issue:
> the client gets randomly disconnected after a while.
> As in the previous case, I can see the empty heartbeat messages from my
> client to the broker every 7.5 seconds.
> Do you know why this is happening? Could this be a bug in Qpid Proton 0.33?
> Or could it be an issue related to how the broker manages the reception of
> the heartbeats coming from my client?
>
> Thank you very much in advance,
> Francesco


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Broker-J 8.0.6

[Gordon Sim]

On Tue, Aug 24, 2021 at 9:39 PM Alex Rudyy  wrote:
> I built release artefacts for Qpid Broker-J version 8.0.6 RC1.
> Please, give them a test out and vote accordingly.
>
> The source and binary archives can be found at:
> https://dist.apache.org/repos/dist/dev/qpid/broker-j/8.0.6-rc1/

+1, built and ran all tests, ran selected python proton examples
against it, ran some qpid-cpp clients against it (0-10 and 1.0).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: how to enable AMQP 1.0 and 0-10 for Qpid C++ broker

[Gordon Sim]

On Tue, Aug 3, 2021 at 9:15 PM Svrankovic11
 wrote:
> I would like to connect to Qpid C++ broker 1.39.0 using different clients 
> that run AMQP 1.0 and 0-10. How can I turn on both protocol versions for Qpid 
> C++ Broker?

0-10 is always on, whether you want it or not
1.0 is built as a plugin; to build it you need to have qpid proton


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPIC CPP threading model

[Gordon Sim]

On Tue, Jul 13, 2021 at 1:10 PM rahul.sin...@morganstanley.com
 wrote:
> I need it to ensure I can run it on a specific CPU core.

Ok, running pstack against the process should show you the thread id for that.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPIC CPP threading model

[Gordon Sim]

On Tue, Jul 13, 2021 at 12:23 PM rahul.sin...@morganstanley.com
 wrote:
> I am using qpid-cpp-1.39.0 and want to create multiple topics and handle 
> incoming data in the most efficient way. What I have understood is that the 
> qpid::messaging::Connection, Session and Receiver are all created in the 
> application thread. When we try to fetch data from the Receiver, this is also 
> processed in the application thread. But under the hood, it sounds like the 
> Session might be communicating with the broker in a different thread and 
> buffering up the incoming data for appropriate receivers to fetch them. I am 
> inferring this after reading the in line comments for Receiver::fetch() 
> method which states that "this method will check with the server that there 
> is no message for the subscription this receiver is serving before returning 
> false."

Correct. There is an IO thread that does all the sending and receiving of data.

> Is there a way we can get the thread Id or any Callback from it so that we 
> can determine the thread id.

There is no callback. You could get the thread id from pstack output.
Why do you need it? (If you prefer a callback style of API, look at
the QPid proton c++ library).

> Also is it correct to assume there is only 1 such thread per Session which is 
> getting data from the other end?

There is one IO thread per connection.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Ruby requirements for QPID C++

[Gordon Sim]

On Fri, Jul 9, 2021 at 4:00 PM rahul.sin...@morganstanley.com
 wrote:
> I haven't look deeper but it would be really great if you can help locating 
> where actually the generated code gets in. Does it go under the install 
> directory or  the source directory where we have qpid-cpp-1.39.0 folder.

It is in the build directory, under [src|include]/qpid/[framing|client]


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid C++ Broker 1.39 on RHEL 8 ?

[Gordon Sim]

On Thu, Jul 8, 2021 at 7:44 PM Steve Charbonneau
 wrote:
> Can someone confirm if the Qpid C++ Broker (v1.39) is also supported for
> running on RHEL 8 ?

I can confirm it will build and run on RHEL8. However, work on that
component has mostly stopped. Have you considered the java broker? Or
one of the ActiveMQ brokers?


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Ruby requirements for QPID C++

[Gordon Sim]

On Fri, Jul 9, 2021 at 12:39 PM rahul.sin...@morganstanley.com
 wrote:
> Building qpid-proton is fine without Ruby. However, when I try to build 
> qpid-cpp-1.39.0, cmake gives below error -
>
> CMake Error at src/CMakeLists.txt:87 (message):
>   Can't locate ruby, needed to generate amqp 0-10 framing code.
>
> Though I need it for AMQP 1.0.
> I use the same install folder as I did for qpid proton. Also, I exported the 
> PKG_CONFIG_PATH.
>
> Once I add Ruby module, then it works happily and later on detects that AMQP 
> 1.0 is enabled.

Unfortunately building the 0-10 code is not optional at present.
However if the generated code is there then it doesn't need to be
regenerated. (You would still get an error, but that could be disabled
with the attached patch). So if you had to build somewhere that didn't
have ruby you could bundle up and reuse source generated from
somewhere you do have ruby. Or if you want to remove it after
generation, you could do that also.
diff --git a/src/CMakeLists.txt b/src/CMakeLists.txt
index fe6309010..de8097b63 100644
--- a/src/CMakeLists.txt
+++ b/src/CMakeLists.txt
@@ -83,9 +83,9 @@ mark_as_advanced(QPID_AMQP_SPEC)
 if (NOT QPID_AMQP_SPEC)
   message(FATAL_ERROR "Can't find amqp 0-10 spec for framing code generation")
 endif (NOT QPID_AMQP_SPEC)
-if (NOT RUBY_EXECUTABLE)
-  message(FATAL_ERROR "Can't locate ruby, needed to generate amqp 0-10 framing code.")
-endif (NOT RUBY_EXECUTABLE)
+#if (NOT RUBY_EXECUTABLE)
+#  message(FATAL_ERROR "Can't locate ruby, needed to generate amqp 0-10 framing code.")
+#endif (NOT RUBY_EXECUTABLE)
 
 set(specs ${QPID_AMQP_SPEC})
 set(regen_amqp OFF)

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Ruby requirements for QPID C++

[Gordon Sim]

On Fri, Jul 9, 2021 at 10:35 AM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> I have recently build  qpid-proton-0.34.0 and qpid-cpp-1.39.0 and need them 
> for AMQP1.0. I removed the BINDINGS for RUBY ( -DBUILD_BINDING_RUBY=OFF while 
> building qpid-cpp-1.39.0 AND -DBUILD_RUBY=OFF while building 
> qpid-proton-0.34.0).
>
> However, it still requires the ruby modules. Is there a way we can build 
> these without depending on ruby?

Are you getting a specific error requesting those modules?


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.1.0

[Gordon Sim]

On Mon, Jul 5, 2021 at 5:25 PM Robbie Gemmell  wrote:
> I have put together a spin for a 1.1.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/1.1.0-rc1/

+1 (ran tests, ran example against router)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Subscribing to a topic

[Gordon Sim]

Use the Message:setContentObject()/getContentObject() methods and
supply the body as a qpid::types::Variant which lets you specify the
*encoding* as utf8, ensuring it is encoded correctly as a string for
AMQP 1.0 rather than bytes.

e.g. either:

qpid::types::Variant value(s[i], "utf8");
msg.setContentObject(value);

or:

msg.getContentObject() = s[i];
msg.getContentObject().setEncoding("utf8");


On Fri, Jul 2, 2021 at 12:18 PM rahul.sin...@morganstanley.com
 wrote:
>
> Many thanks for your responses. Using the single quote helped me to get this 
> working.
>
> Now I am trying to add a request to a queue. For this I create a sender and 
> receiver where I would send the request on 'queue://ID.RequestQueueExample' 
> and then receive any response from 'queue://ID.ResponseQueueExample'.
> Sender sender = session.createSender("'queue://ID.RequestQueueExample'");
> Receiver recv = session.createReceiver("'queue://ID.ResponseQueueExample'");
>
> Then I create a Message and set the necessary parameters and prepare the 
> Content as required.  The content needs to be in XML format which I populate 
> beforehand, extract it in a string and then invoke Message::setContent(str).
> I also tried setting the contentType to "utf8".  Not sure if we need to set 
> this to any other type?
> Here is an example of the string passed to Message::setContent(str) -
> 
>   
> ABCDE
> AB_CDE
>   
>   
> XYZ
>   
> 
>
> However, when I send the request, I receive back error from the broker in the 
> receiver queue complaining that the message format is incorrect. My suspicion 
> are -
>
> 1)  The content and contentType is not being set properly.
> 2)  I do not find the sender queue details in the outgoing AMQP frames.  In 
> the message, I set the Message::ReplyTo with the Receiver Queue Address. 
> After looking at some example AMPQ frames which seems to be taken from JMS, I 
> see that the outgoing frame also has the Sender queue address 
> 'queue://ID.ReqQueueExample' in the outgoing frame. I am not quite sure how 
> can I add that with the C++ QPID API. The Message class do not seem to have 
> that option.
>
> Any suggestions for the above 2 points would be highly appreciated.
>
> Best Regards,
> Rahul
> -Original Message-
> From: Robbie Gemmell 
> Sent: 01 July 2021 15:01
> To: users 
> Subject: Re: QPID C++ Subscribing to a topic
>
> On Thu, 1 Jul 2021 at 13:18, Gordon Sim  wrote:
> >
> > On Thu, Jul 1, 2021 at 1:08 PM rahul.sin...@morganstanley.com
> >  wrote:
> > >   1.  As per Robbie's suggestion, I have tried adding topic:// in the 
> > > past as well but the address and name selection gets chopped off from our 
> > > end (after topic: ) in the outgoing AMQP frame to Broker.
> > >
> > > Our Code -
> > > qpid::messaging::Receiver topic_receiver = 
> > > session.createReceiver("topic://ID.ExampleTopic; {node:{type:topic}}"
> > > ");
> >
> > You need some ugly quoting in there, netsed single quotes around the
> > address, e.g.:
> >
> >session.createReceiver("'topic://ID.ExampleTopic';
> > {node:{type:topic}}");
> >
> > That prevents the '/' being misinterpreted. (It has special meaning in
> > the qpid::messaging address syntax, which we don't want here).
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For
> > additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> What Gordon said with the quoting should work to get it to parse correctly, I 
> forgot about that being needed (as its not a combination I've really used 
> myself).
>
> Note I wasnt suggesting you do both the prefix and the 'type:topic'
> node config though, as I dont think ActiveMQ 5 actually looks for the 
> terminus 'topic' capability that adds, rather it uses the address name and 
> looks for a name prefix of "topic://" (something which e.g the JMS client 
> adds itself under the covers based on values the broker advertises at 
> connection open time).
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional 
> commands, e-mail: users-h...@qpid.apache.org
>
>
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions 
> or views contained herein are not intended to be, and do not constitute, 
> advice within the meaning of

Re: QPID C++ Subscribing to a topic

[Gordon Sim]

On Thu, Jul 1, 2021 at 1:08 PM rahul.sin...@morganstanley.com
 wrote:
>   1.  As per Robbie's suggestion, I have tried adding topic:// in the past as 
> well but the address and name selection gets chopped off from our end (after 
> topic: ) in the outgoing AMQP frame to Broker.
>
> Our Code -
> qpid::messaging::Receiver topic_receiver = 
> session.createReceiver("topic://ID.ExampleTopic; {node:{type:topic}}"
> ");

You need some ugly quoting in there, netsed single quotes around the
address, e.g.:

   session.createReceiver("'topic://ID.ExampleTopic'; {node:{type:topic}}");

That prevents the '/' being misinterpreted. (It has special meaning in
the qpid::messaging address syntax, which we don't want here).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Subscribing to a topic

[Gordon Sim]

To specify a :topic capability you can use an address of the form
"ID.ExampleTopic; {node:{type:topic}}".

On Thu, Jul 1, 2021 at 10:10 AM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> The broker does not seem to have much understanding of the C++ QPID Messaging 
> API and is more used to the Java version. All it is suggesting to ensure that 
>  we pass the topic in the format "ID.ExampleTopic". However, looking at the 
> AMQP frames from Broker, it seems to misinterpret that topic for a queue, 
> hence there is an unauthorize error reported. ( " is not authorized to 
> create: queue://ID.ExampleTopic" )
> From the QPID API usage perspective, do I need to invoke something else to 
> make the topic usage clear. I also experimented with creating a Sender with 
> same topic name but I get the same error.
>
> Best Regards,
> Rahul
>
> -Original Message-
> From: Gordon Sim 
> Sent: 30 June 2021 10:01
> To: users@qpid.apache.org
> Subject: Re: QPID C++ Subscribing to a topic
>
> On Wed, Jun 30, 2021 at 9:40 AM rahul.sin...@morganstanley.com 
>  wrote:
> > After being able to establish the connection with the broker at other end, 
> > we try to subscribe to a given topic. For this, we create the receiver with 
> > string mapping to the topic. ( Id.ExampleTopic ), where Id is the 
> > identifier broker assigned to us and ExampleTopic is the topic.
> > We have already sought clarification with the broker about this issue, 
> > however, we wanted to ensure if the AMQP APIs are being used correctly for 
> > this and if we need to somehow communicate that we are subscribing for a 
> > topic. (for example, do we need to add some qualifier to the passed string 
> > etc.
> >
> > qpid::messaging::Connection conn(url, options); conn.open();
> >
> > qpid::messaging::Session session = conn.createSession();
> >
> > qpid::messaging::Receiver topic_receiver =
> > session.createReceiver("Code.ExampleTopic");
>
>
> If you are using AMQP 1.0, and the broker treats the creation of a receiver 
> with that pattern as a subscription on a topic, then the client does not 
> require any further configuration.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional 
> commands, e-mail: users-h...@qpid.apache.org
>
>
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions 
> or views contained herein are not intended to be, and do not constitute, 
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform 
> and Consumer Protection Act. If you have received this communication in 
> error, please destroy all electronic and paper copies and notify the sender 
> immediately. Mistransmission is not intended to waive confidentiality or 
> privilege. Morgan Stanley reserves the right, to the extent permitted under 
> applicable law, to monitor electronic communications. This message is subject 
> to terms available at the following link: 
> http://www.morganstanley.com/disclaimers  If you cannot access these links, 
> please notify us by reply message and we will send the contents to you. By 
> communicating with Morgan Stanley you consent to the foregoing and to the 
> voice recording of conversations with personnel of Morgan Stanley.
>
> You may have certain rights regarding the information that Morgan Stanley 
> collects about you.  Please see our Privacy Pledge 
> https://www.morganstanley.com/privacy-pledge for more information about your 
> rights.
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Commit rights for Tomas Vavricka

[Gordon Sim]

+1

On Thu, Jul 1, 2021 at 12:23 AM Alex Rudyy  wrote:
>
> Hi folks,
>
> I'd like to call a vote to offer commit rights to Tomas Vavricka
>
> Tomas has been contributing to Qpid Broker-J for a couple of years
> starting from 2017. In particular, he submitted an initial
> implementation of the queue ring policy (QPID-7618) and reject policy
> (QPID-7815) for Qpid Broker-J back in 2017. He is an author of
> certificate revocation feature in Qpid Broker-J (QPID-8367). Tomas
> contributed a number of bug fixes and improvements for Qpid Broker-J
> (QPID-83543, QPID-8354,QPID-8456,QPID-8460,QPID-8458,QPID-8459). He
> tested and voted on a number of Qpid Broker-J releases. He also has
> been raising various issues with Qpid Broker-J and Qpid JMS Client for
> AMQP 1.0 in the user mailing list and creating JIRAs for the issues.
>
> I feel it is time we offer Tomas commit-rights of his own.
>
> I will close this vote at 00:00 UTC on Friday 9th June, at which timeI
> will tally the votes.
>
> Regards,
> Alex Rudyy
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Subscribing to a topic

[Gordon Sim]

On Wed, Jun 30, 2021 at 9:40 AM rahul.sin...@morganstanley.com
 wrote:
> After being able to establish the connection with the broker at other end, we 
> try to subscribe to a given topic. For this, we create the receiver with 
> string mapping to the topic. ( Id.ExampleTopic ), where Id is the identifier 
> broker assigned to us and ExampleTopic is the topic.
> We have already sought clarification with the broker about this issue, 
> however, we wanted to ensure if the AMQP APIs are being used correctly for 
> this and if we need to somehow communicate that we are subscribing for a 
> topic. (for example, do we need to add some qualifier to the passed string 
> etc.
>
> qpid::messaging::Connection conn(url, options);
> conn.open();
>
> qpid::messaging::Session session = conn.createSession();
>
> qpid::messaging::Receiver topic_receiver = 
> session.createReceiver("Code.ExampleTopic");


If you are using AMQP 1.0, and the broker treats the creation of a
receiver with that pattern as a subscription on a topic, then the
client does not require any further configuration.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Dispatch Router 1.16.1 (RC1)

[Gordon Sim]

On Mon, Jun 28, 2021 at 7:33 PM Ken Giusti  wrote:
> Please cast your vote on this thread to release RC1 as the official Qpid
> Dispatch Router version  1.16.1.
>
>
> RC1 of Qpid Dispatch Router version 1.16.1 can be found here:
>
>
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.16.1-rc1

+1 (verified checksum and signature, built from source, ran all tests,
ran selected python proton examples against it, verified qdstat and
qdrouterd between 1.15.0 and 1.16.1 in each direction, built image and
ran it through CI at skupper.io)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Connection url

[Gordon Sim]

On Tue, Jun 29, 2021 at 9:19 AM rahul.sin...@morganstanley.com
 wrote:
> Many thanks for your help. I got it connected now...

Great! \o/


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Connection url

[Gordon Sim]

On Mon, Jun 28, 2021 at 7:43 PM rahul.sin...@morganstanley.com
 wrote:
> On further debugging,  we find that the SSL Connection is failing. The error 
> reported is -
> [System] debug Exception constructed: Failed: NSS error [-8172] 
> (PATH_QPID_CPP1_39_0/src/qpid/qpid-cpp-1.39.0/src/qpid/sys/ssl/SslSocket.cpp:205)
>
> Which points to method SslSocket::finishConnect and at the last line 
> NNS_CHECK(SSL_ForceHandshake ) .
> I tried searching for NSS error code -8172 but could not get much info. Is 
> this something you can help with.

That means "Peer's certificate issuer has been marked as not trusted
by the user.", which probably means that you don't have the CA cert
that issued the server's cert in your NSS DB as a trusted CA.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Connection url

[Gordon Sim]

On Mon, Jun 28, 2021 at 2:45 PM rahul.sin...@morganstanley.com
 wrote:
> I don’t get url exception if I use example.xyz.com:5671 format. But still, I 
> receive Connect failed error.
>
> "caught std::exception Connect failed to amqp:ssl::example.xyz.com:5671 
> Exceeded retries"
>
> At the moment, its not clear whether the above error indicates issues at TCP 
> level or at SSL layer. Is there a way we can get some traces in qpid code and 
> troubleshoot.

The easiest way is to run the client with env var QPID_LOG_ENABLE=trace+


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Connection url

[Gordon Sim]

Have you tried amqps:/example.xyz.com or even example.xyz.com:5671?

On Fri, Jun 25, 2021 at 2:43 PM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> I get below exception -
> Caught std::exception Invalid URL: amqps://example.xyz.com 
> (qpid/qpid-cpp-1.39.0/src/qpid/Url.cpp:248)
>
> We have been by the broker at the other end that fully qualified domain names 
> are necessary for certificate handshake.
>
> Best Regards,
> Rahul
> -Original Message-
> From: Gordon Sim 
> Sent: 25 June 2021 11:40
> To: users@qpid.apache.org
> Subject: Re: QPID C++ Connection url
>
> On Fri, Jun 25, 2021 at 9:50 AM rahul.sin...@morganstanley.com 
>  wrote:
> > The Apache QPID C++ Messaging library states the below rule for url
> >
> > /** Simple recursive-descent parser for this grammar:
> > url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *(","
> > protocol_addr) protocol_addr = tcp_addr / rmda_addr / ssl_addr / ..
> > others plug-in tcp_addr = ["tcp:"] host [":" port] rdma_addr = "rdma:"
> > host [":" port] ssl_addr = "ssl:" host [":" port] */
> >
> > However, the broker at the other end of our communication channel expects 
> > the URL to have the fully qualified domain names for certificate handshake.
> > Their expectation is to see url in this pattern - amqps://example.xyz.com, 
> > where //example.xyz.com corresponds to the host and port.
> > However, when I try to use this pattern, I receive incorrect URL exception.
>
> Not sure what you are seeing. However you can just use host:port (which is 
> generally what I do as I find it simpler). There should certainly be no issue 
> with fully qualified hostnames either way though.
>
> > Secondly, is there a way we can specify the interface through which the 
> > host and port connection will go out.
>
> I'm not sure I understand. The hostname will resolve to an ip address and the 
> normal routing should then determine how to direct the packets.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional 
> commands, e-mail: users-h...@qpid.apache.org
>
>
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions 
> or views contained herein are not intended to be, and do not constitute, 
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform 
> and Consumer Protection Act. If you have received this communication in 
> error, please destroy all electronic and paper copies and notify the sender 
> immediately. Mistransmission is not intended to waive confidentiality or 
> privilege. Morgan Stanley reserves the right, to the extent permitted under 
> applicable law, to monitor electronic communications. This message is subject 
> to terms available at the following link: 
> http://www.morganstanley.com/disclaimers  If you cannot access these links, 
> please notify us by reply message and we will send the contents to you. By 
> communicating with Morgan Stanley you consent to the foregoing and to the 
> voice recording of conversations with personnel of Morgan Stanley.
>
> You may have certain rights regarding the information that Morgan Stanley 
> collects about you.  Please see our Privacy Pledge 
> https://www.morganstanley.com/privacy-pledge for more information about your 
> rights.
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID C++ Connection url

[Gordon Sim]

On Fri, Jun 25, 2021 at 9:50 AM rahul.sin...@morganstanley.com
 wrote:
> The Apache QPID C++ Messaging library states the below rule for url
>
> /** Simple recursive-descent parser for this grammar:
> url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *("," protocol_addr)
> protocol_addr = tcp_addr / rmda_addr / ssl_addr / .. others plug-in
> tcp_addr = ["tcp:"] host [":" port]
> rdma_addr = "rdma:" host [":" port]
> ssl_addr = "ssl:" host [":" port]
> */
>
> However, the broker at the other end of our communication channel expects the 
> URL to have the fully qualified domain names for certificate handshake.
> Their expectation is to see url in this pattern - amqps://example.xyz.com, 
> where //example.xyz.com corresponds to the host and port.
> However, when I try to use this pattern, I receive incorrect URL exception.

Not sure what you are seeing. However you can just use host:port
(which is generally what I do as I find it simpler). There should
certainly be no issue with fully qualified hostnames either way
though.

> Secondly, is there a way we can specify the interface through which the host 
> and port connection will go out.

I'm not sure I understand. The hostname will resolve to an ip address
and the normal routing should then determine how to direct the
packets.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39

[Gordon Sim]

On Thu, Jun 24, 2021 at 12:08 PM rahul.sin...@morganstanley.com
 wrote:
> ldd for libqpidmessaging.so gives me libqpid-proton-core.so.10 alongwith 
> other qpid libs- libqpidtypes.so.1, libqpidclient.so.2 and libqpidcommon.so.2.
> However, until I uncomment " protocol-defaults=amqp1.0,amqp0-10" from the 
> qpidc.conf available in installedpath/etc/qpid/qpidc.conf, the ampq1.0 is not 
> selected. This is the file whereI actually have to add additional ssl config 
> details as well, including the ssl-cert-db.
>
> This is inline with current implementation of ConnectionOptions::set method  
> in src/qpid/messaging/ConnectionOptions.cpp. There is no option for 
> "protocol" field there (which is supposed to specify the amqp1.0 option).

Yes, the protocol actually gets used to create the right type of
connection, so you need to specify it in the options passed to the
constructor, rather than trying to set it after the connection has
already been created.

> After going through the ssl.txt descriptions,
> My major issue/trouble is with the creation of certificate database (through 
> certutil tool). This should be pointed out by --ssl-cert-db in the qpidc.conf 
> and all relevant certificate and keys should be available there.
> Now, I already have created a cert (and made it available for the server at 
> other end of the connection) and have a key for it. I also have a trusted 
> cert from the server. Now, it seems that I will need to somehow inject these 
> cert and key to the cert database. However, looking at ways to do that, 
> certutil --help, I see an option to add an existing trusted certificate to 
> the database (-A option), but do not see any option to add the key to created 
> certification needed by the server at other end.

You can use pk12util to add in a pkcs12 key. (If it is pem format you
can convert it using openssl).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39

[Gordon Sim]

Have you seen this for SSL config:
https://github.com/apache/qpid-cpp/blob/main/docs/ssl.txt ?

Regarding protocol=amqp1.0 not being recognised, that sounds as if
proton was not found when compiling. If you run ldd against
libqpidmessaging.so do you see proton being listed?

On Tue, Jun 22, 2021 at 4:48 PM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> I actually set the QPID Messaging and QPID Proton install path to a machine 
> relative path eg /var/tmp/qpid. And eventually copied the resulting folder to 
> equivalent location on the test machine. This helped me to resolve the 
> problem.
> Subsequently, I have been able to run my app but unable to connect to a tcp 
> endpoint with SSL authentication. I am wondering if my connection parameters 
> are correct.
>
> const char *url = "amqp:tcp:x.x.x.x:y"; // amqp:tcp:IP:PORT
> qpid::messaging Connection conn(url);
> conn.setOption("transport", qpid::types::Variant("ssl"));
> conn.setOption("ssl_cert_name", qpid::types::Variant("AA"));
> conn.setOption("container_id", qpid::types::Variant("BBB"));
> conn.open();
>
> But this does not connect successfully. I am using AMQP1.0 and wondering if 
> the connection parameters are correct.
> The "transport" field is currently set to "ssl", however, I tried with "tcp" 
> before, but it did not work either.
> The Qpid messaging connection API suggested to use "protocol" field as 
> "amqp1.0", however, it throws an exception that this "parameter" field is not 
> recognized.
>
> I actually uncommented a line within the INSTALLED_DIR/etc/qpid/qpidc.conf to 
> select amqp 1.0
> protocol-defaults=amqp1.0,amqp0-10
>
> Any suggestions about the correctness of the API usage would be really 
> appreciated.
> Further, are there any ways to get logs out of QPID libraries so that I can 
> know how far it is going.
>
> Best Regards,
> Rahul
> -Original Message-
> From: Gordon Sim 
> Sent: 21 June 2021 20:52
> To: users@qpid.apache.org
> Subject: Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39
>
> My suggestion is to edit the src/config.h before building to specify the 
> QPIDC_MODULE_DIR path on the target system. (I thought there would be a way 
> of setting it automatically via a cmake variable but I can't seem to do that).
>
> On Mon, Jun 21, 2021 at 5:38 PM rahul.sin...@morganstanley.com 
>  wrote:
> >
> > Hello,
> > Many thanks for your response. I build apache qpid libraries and my 
> > application on a different compile machine and run my application on a 
> > different test machine. Test machine does not have access to location used 
> > on compile machine.
> >
> > While building my application, I point it to the local install folder where 
> > the output of QPID builds are stored.
> > -L points to the local qpid  install path so that shared objects could be 
> > found by the linker.
> >
> > On the compile machine, I set the LD_LIBRARY_PATH with a local path where I 
> > copy the QPID install folder. Once the binary is ready, I copy it on the 
> > test machine.
> >
> > However, when I run my app or run strace on the test machine, I see this 
> > error and the reference to the path is not from the test machine but to the 
> > path on compile machine where I actually got the QPID builds installed.
> >
> >  Details from strace
> > open("PATH_ON_COMPILE_MACHINE/install/etc/qpid/qpidc.conf", O_RDONLY)
> > = -1 EIO (Input/output error)
> > open("PATH_ON_COMPILE_MACHINE/install/etc/qpid/qpidc.conf", O_RDONLY)
> > = -1 EIO (Input/output error) Caught std::exception Invalid value for
> > module-dir: Input/output error: Can't check directory
> > PATH_ON_COMPILE_MACHINE/install/lib64/qpid/client
> >
> > Best Regards,
> > Rahul
> > -Original Message-
> > From: Gordon Sim 
> > Sent: 21 June 2021 13:32
> > To: users@qpid.apache.org
> > Subject: Re: RDMA shared object reliance for QPID AMQP C++Messaging
> > APIv1.39
> >
> > You should not need to have any client module directory. My first guess is 
> > that it is perhaps a permissions issue. Is your application running as a 
> > user able to list files under the /lib64/qpid directory?
> >
> > (The exception seems to come from stat() returning an error other than 
> > ENOENT).
> >
> > On Mon, Jun 21, 2021 at 11:34 AM rahul.sin...@morganstanley.com 
> >  wrote:
> > >
> > > Hello,
> > > I am trying on run my C++ application on linux based on QPID

Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39

[Gordon Sim]

My suggestion is to edit the src/config.h before building to specify
the QPIDC_MODULE_DIR path on the target system. (I thought there would
be a way of setting it automatically via a cmake variable but I can't
seem to do that).

On Mon, Jun 21, 2021 at 5:38 PM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> Many thanks for your response. I build apache qpid libraries and my 
> application on a different compile machine and run my application on a 
> different test machine. Test machine does not have access to location used on 
> compile machine.
>
> While building my application, I point it to the local install folder where 
> the output of QPID builds are stored.
> -L points to the local qpid  install path so that shared objects could be 
> found by the linker.
>
> On the compile machine, I set the LD_LIBRARY_PATH with a local path where I 
> copy the QPID install folder. Once the binary is ready, I copy it on the test 
> machine.
>
> However, when I run my app or run strace on the test machine, I see this 
> error and the reference to the path is not from the test machine but to the 
> path on compile machine where I actually got the QPID builds installed.
>
>  Details from strace
> open("PATH_ON_COMPILE_MACHINE/install/etc/qpid/qpidc.conf", O_RDONLY) = -1 
> EIO (Input/output error)
> open("PATH_ON_COMPILE_MACHINE/install/etc/qpid/qpidc.conf", O_RDONLY) = -1 
> EIO (Input/output error)
> Caught std::exception Invalid value for module-dir: Input/output error: Can't 
> check directory  PATH_ON_COMPILE_MACHINE/install/lib64/qpid/client
>
> Best Regards,
> Rahul
> -Original Message-
> From: Gordon Sim 
> Sent: 21 June 2021 13:32
> To: users@qpid.apache.org
> Subject: Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39
>
> You should not need to have any client module directory. My first guess is 
> that it is perhaps a permissions issue. Is your application running as a user 
> able to list files under the /lib64/qpid directory?
>
> (The exception seems to come from stat() returning an error other than 
> ENOENT).
>
> On Mon, Jun 21, 2021 at 11:34 AM rahul.sin...@morganstanley.com 
>  wrote:
> >
> > Hello,
> > I am trying on run my C++ application on linux based on QPID AMQP messaging 
> > API and connect to TCP endpoint with SSL authentication. At the moment, I 
> > am just trying to test the correct usage and do nothing more than 
> > establishing the connection. However, I get a runtime error which indicates 
> > the exe is looking for some shared object at the QPID AMQP installed 
> > directory (PATH_TO_INSTALL_DIRECTORY/lib64/qpid/client). However, I do not 
> > see any client sub-folder within the lib64/qpid path. There is only a 
> > daemon folder out there. The error I receive is "Caught std::exception 
> > Invalid value for module-dir: Input/output error: Can't check directory: 
> > PATH_TO_INSTALL_DIRECTORY/lib64/qpid/client"
> >
> > I have build both QPID Proton C v 0.34 and QPID AMQP Messaging C++ v1.39 
> > packages and point the shared objects build to the install directory.
> > Please note I do not have libibverbs and librdmacm packages which are
> > optional and required for RDMA transport protocol.  ( 
> > https://raw.githubusercontent.com/apache/qpid-cpp/main/INSTALL.txt ) Sounds 
> > like for some reasons, my qpid amqp packages do not build shared objects 
> > which are supposed to go under (installfolder)/lib64/qpid/client directory. 
> > I only need C++ and hence exclude BINDINGS for PERL,RUBY and PYTHON in my 
> > cmake options.
> >
> > In my main application, I use the following connection code so far -
> >
> > #include 
> >
> > const char *url = "amqp:tcp:IP:PORT";
> > qpid::messaging::Connection conn(url);
> >
> > Looking forward to hearing from you.
> >
> > Best Regards,
> > Rahul
> >
> > 
> > NOTICE: Morgan Stanley is not acting as a municipal advisor and the 
> > opinions or views contained herein are not intended to be, and do not 
> > constitute, advice within the meaning of Section 975 of the Dodd-Frank Wall 
> > Street Reform and Consumer Protection Act. If you have received this 
> > communication in error, please destroy all electronic and paper copies and 
> > notify the sender immediately. Mistransmission is not intended to waive 
> > confidentiality or privilege. Morgan Stanley reserves the right, to the 
> > extent required and/or permitted under applicable law, to monitor 
> > electronic communications, including telephone calls with Morgan Stanley 
> > personnel. T

Re: RDMA shared object reliance for QPID AMQP C++Messaging APIv1.39

[Gordon Sim]

You should not need to have any client module directory. My first
guess is that it is perhaps a permissions issue. Is your application
running as a user able to list files under the
/lib64/qpid directory?

(The exception seems to come from stat() returning an error other than ENOENT).

On Mon, Jun 21, 2021 at 11:34 AM rahul.sin...@morganstanley.com
 wrote:
>
> Hello,
> I am trying on run my C++ application on linux based on QPID AMQP messaging 
> API and connect to TCP endpoint with SSL authentication. At the moment, I am 
> just trying to test the correct usage and do nothing more than establishing 
> the connection. However, I get a runtime error which indicates the exe is 
> looking for some shared object at the QPID AMQP installed directory 
> (PATH_TO_INSTALL_DIRECTORY/lib64/qpid/client). However, I do not see any 
> client sub-folder within the lib64/qpid path. There is only a daemon folder 
> out there. The error I receive is "Caught std::exception Invalid value for 
> module-dir: Input/output error: Can't check directory: 
> PATH_TO_INSTALL_DIRECTORY/lib64/qpid/client"
>
> I have build both QPID Proton C v 0.34 and QPID AMQP Messaging C++ v1.39 
> packages and point the shared objects build to the install directory.
> Please note I do not have libibverbs and librdmacm packages which are 
> optional and required for RDMA transport protocol.  ( 
> https://raw.githubusercontent.com/apache/qpid-cpp/main/INSTALL.txt )
> Sounds like for some reasons, my qpid amqp packages do not build shared 
> objects which are supposed to go under (installfolder)/lib64/qpid/client 
> directory. I only need C++ and hence exclude BINDINGS for PERL,RUBY and 
> PYTHON in my cmake options.
>
> In my main application, I use the following connection code so far -
>
> #include 
>
> const char *url = "amqp:tcp:IP:PORT";
> qpid::messaging::Connection conn(url);
>
> Looking forward to hearing from you.
>
> Best Regards,
> Rahul
>
> 
> NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions 
> or views contained herein are not intended to be, and do not constitute, 
> advice within the meaning of Section 975 of the Dodd-Frank Wall Street Reform 
> and Consumer Protection Act. If you have received this communication in 
> error, please destroy all electronic and paper copies and notify the sender 
> immediately. Mistransmission is not intended to waive confidentiality or 
> privilege. Morgan Stanley reserves the right, to the extent required and/or 
> permitted under applicable law, to monitor electronic communications, 
> including telephone calls with Morgan Stanley personnel. This message is 
> subject to the Morgan Stanley General Disclaimers available at the following 
> link: http://www.morganstanley.com/disclaimers.  If you cannot access the 
> links, please notify us by reply message and we will send the contents to 
> you. By communicating with Morgan Stanley you acknowledge that you have read, 
> understand and consent, (where applicable), to the foregoing and the Morgan 
> Stanley General Disclaimers.
>
> You may have certain rights regarding the information that Morgan Stanley 
> collects about you. Please see our Privacy Pledge 
> https://www.morganstanley.com/privacy-pledge for more information about your 
> rights.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Broker-J 8.0.5

[Gordon Sim]

+1 (ran tests, c++ qpid::messaging client and proton python examples
against it).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[dispatch-router] 1.16.1 release?

[Gordon Sim]

There have been a couple of fixes since the 1.16.0 release that are
useful for users of the tcp support. Making those available as a
1.16.1 seems like a good idea to me. The fixes I would suggest are:

DISPATCH-2142
DISPATCH-2097
DISPATCH-1878 (last commit)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Message Persistence in Qpid Broker C++ (1.39)

[Gordon Sim]

On Fri, Jun 4, 2021 at 5:40 AM Namitha, Nancy  wrote:
>
> Thank Robbie and Gordon for the suggestion, when I debug further, I observed 
> that Consuming application was blocked even though the messages were there in 
> the queue it was unable to receive the messages, when I restart the consuming 
> application it would run for some time and once again go into block state, 
> which caused the queue size to grow and to be full, which caused this issue. 
> Probably I will test  with Broker J++ or active MQ.

That could be flow control or messages not being acknowledged; you
might need to issue credit or check you are accepting all the received
messages.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 1.0.0

[Gordon Sim]

On Mon, May 24, 2021 at 11:54 AM Robbie Gemmell
 wrote:
> On Wed, 19 May 2021 at 16:41, Robbie Gemmell  wrote:
> >
> > Hi folks,
> >
> > I have put together a spin for a 1.0.0 Qpid JMS client release,
> > please give it a test out and vote accordingly.
> >
> > The source and binary archives can be grabbed from:
> > https://dist.apache.org/repos/dist/dev/qpid/jms/1.0.0-rc1/


+1, ran tests and hello-world example against router


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Message Persistence in Qpid Broker C++ (1.39)

[Gordon Sim]

I would advise using the qpid java broker or one of the activemq brokers.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Message Persistence in Qpid Broker C++ (1.39)

[Gordon Sim]

On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy  wrote:
> Is Broker - J optimized for the below mentioned scenario.

I believe the java broker will indeed perform better for synchronous
publish. Best thing is to run a quick test though.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Message Persistence in Qpid Broker C++ (1.39)

[Gordon Sim]

On Wed, May 19, 2021 at 5:09 AM Namitha, Nancy  wrote:
>I have deployed Qpid Broker C++ v 1.39 package on Ubuntu 18.4. 
>  And have enabled persistence using linearstore libraries.  And I am using 
> AMQP 1.0 Client Library for GO (https://github.com/Azure/go-amqp)  for 
> sending and receiving messages.
> When I set the message to be persistent, and send it, it takes min  .5 secs 
> to push the message to the queue, the function to return.  If the Message is 
> not persistent, it takes less than  1 ms to send the message.  I am pushing 
> the message to a Persistent Queue
>
> I would like to understand if this behavior is expected if the message is set 
> to persistent, or is there any configuration or properties that needs to be 
> set to reduce the time taken to push the messages  I did not find any proper 
> documentation for persistence.

The go client sends messages synchronously, i.e. it waits for an
acknowledgement from the server before returning (you can turn off
acknowledgements using the sender settle mode, but that is probably
not what you want for persistent messages). The broker will not
acknowledge the message until it is sure it is flushed to disk. The
c++ broker is not really optimised for storing a single message at a
time, so the performance for that pattern is indeed likely to be quite
slow.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Dispatch Router 1.16.0 (RC1)

[Gordon Sim]

On Mon, May 10, 2021 at 6:01 PM Ken Giusti  wrote:
> Please cast your vote on this thread to release RC1 as the official Qpid
> Dispatch Router version  1.16.0.

+1 (verified signature and checksum, built from source ran all system
tests and installed, ran python examples against router)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Apache Qpid JMS 0.58.0

[Gordon Sim]

On Tue, Apr 6, 2021 at 5:48 PM Robbie Gemmell  wrote:
>
> Hi folks,
>
> I have put together a spin for a 0.58.0 Qpid JMS client release,
> please give it a test out and vote accordingly.
>
> The source and binary archives can be grabbed from:
> https://dist.apache.org/repos/dist/dev/qpid/jms/0.58.0-rc1/
>
> The maven artifacts are also staged for now at:
> https://repository.apache.org/content/repositories/orgapacheqpid-1217
>
> The JIRAs assigned are:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314524=12350021

+1 (verified checksum and signature, built from source including
tests, ran example against qpidd and qdrouterd)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org