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 indicat
y 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
it 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,
&g
ing 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 Mess
Hello,
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:"] ho
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-desce
ache.org
Subject: Re: QPID C++ Connection url
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 C++ Connection url
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
Many thanks for your help. I got it connected now...
Best Regards,
Rahul
-Original Message-
From: Gordon Sim
Sent: 28 June 2021 20:14
To: users@qpid.apache.org
Subject: Re: QPID C++ Connection url
On Mon, Jun 28, 2021 at 7:43 PM rahul.sin...@morganstanley.com
wrote:
> On furt
Hello,
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 hav
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 bein
with Message Class in C++ but that
comes later)
Best Regards,
Rahul
-Original Message-
From: Gordon Sim
Sent: 01 July 2021 10:43
To: users@qpid.apache.org
Subject: Re: QPID C++ Subscribing to a topic
To specify a :topic capability you can use an address of the form
"ID.ExampleTopic
-
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 addin
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 ther
Ruby requirements for QPID C++
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
n Sim
Sent: 09 July 2021 15:29
To: users@qpid.apache.org
Subject: Re: Ruby requirements for QPID C++
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
Hello,
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, th
Regards,
Rahul
-Original Message-
From: Gordon Sim
Sent: 13 July 2021 12:30
To: users@qpid.apache.org
Subject: Re: QPIC CPP threading model
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
&g
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 receive
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 handl
++ or proton layer. Any quick pointer will be highly
appreciated.
Best regards,
Rahul
-Original Message-
From: Gordon Sim
Sent: 31 March 2022 11:15
To: users@qpid.apache.org
Subject: Re: QPID C++ Queue handling
On Thu, Mar 31, 2022 at 11:06 AM rahul.sin...@morganstanley.com
wrote
eue handling
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://githu
threads I think "my-queue; { node:{ type:
queue }}" is the format of that).
[1]
https://activemq.apache.org/components/artemis/documentation/latest/address-model.html
[2]
https://activemq.apache.org/components/artemis/documentation/latest/address-settings.html
On Thu, 31 Mar 202
ctors.
You can do that either by ensuring the address+queue definition is anycat, or
changing the broker side address settings [1][2] so anything auto-created is
considered 'anycast', or you could alternatively add a 'queue' type hint into
the consumer by setting the type option into t
vers which subscribed to that topic. Please
can you help how this can be achieved or in case of topic, does the qpid by
default copies the message in all the subscribed receivers.
Best Regards,
Rahul
-Original Message-----
From: rahul.sin...@morganstanley.com
Sent: 01 April 2022 11:03
s, essentially like
the JMS selector syntax. It is the server that does the selection.
The server will provide a copy of every message sent to the topic to each
subscription on the topic (i.e each subscriber if they aren't shared subs),
that is how pub/sub topics work. The client does noth
need to specify a repeatable
link name and set the terminus durability. This isnt something I have tried,
but it looks like you can set the link name (used as subscription name) and
link durability within the 'address string' given to the client, by specifying
'link options' in
27 matches
Mail list logo
