Re: Status monitoring

Hello Daniel, this should work using a last value queue. Kind Regards, Andreas Am 13. Januar 2018 12:19:57 MEZ schrieb Daniel Gavrila : > >Hello, > >My environment is: > C++ Proton v. 0.19 > C++ Broker v.1.37 configured with AMQP 1.0 > >I have to implement the following use case scenario

C++ Broker: combine bindings and routes

Hello All, Please could you help me with a problem combining bindings and routes. I am running Qpid C++ Broker 1.36.0 on Ubuntu. What I want to reach: Producer P1 sends a durable message to a durable queue Q1 at broker B1. B1 sends the message to broker B2 where consumer C1 should read the messa

qpidd (C++ Message Broker): resend of messages

Hello, I am running a qpidd message broker (C++ / version 0.28). All applications are connected via C++ messaging api on the same machine. One of the connected applications handles messages twice. I ask myself if the message broker resent messages to this application but I can not verify it.

Re: Qpid JMS - Idle timeout / inactivity handling

Hello, I have the same question but for the Qpid C++ API (version 0.28). I I tried it out and my application was kicked out. So I set the following parameters: {transport:ssl,protocol:amqp1.0,heartbeat:5} But the application was kicket out, again. Do you have any suggestions what I shou

Re: Qpid JMS - Idle timeout / inactivity handling

Hello, I have have the same question regarding the Qpid C++ API (version 0.28). I tried it out and my application was kicked out. So I set the following parameters: Am 26.10.2015 um 11:38 schrieb Robbie Gemmell: On 26 October 2015 at 10:14, Erik Aschenbrenner wrote: Dear Qpid-Users, I'm

Re: C++ messaging API: SASL mechanism not set correctly

OK, me too. strange. Am 27.08.2015 um 17:42 schrieb Gordon Sim: On 08/27/2015 04:36 PM, Andreas Welchlin wrote: Did you try with AMQP 1.0 or with AMQP 0.10? 0-10 - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

Re: C++ messaging API: SASL mechanism not set correctly

Did you try with AMQP 1.0 or with AMQP 0.10? Am 27.08.2015 um 17:38 schrieb Gordon Sim: On 08/27/2015 04:09 PM, Andreas Welchlin wrote: Hi All, now I can answer my own question: instead of: mConnection = new Connection("amqp:ssl:"); mConnection->setOption(QPID_OPTION_SA

Re: C++ messaging API: SASL mechanism not set correctly

ugust 2015 11:50:06 MESZ, schrieb Gordon Sim : On 08/26/2015 01:40 PM, Andreas Welchlin wrote: Hello, I tried to connect to a AMQP Broker via SSL using AMQP 0.10. I used C++ and the Qpid Messaging API version 0.28. It seems like I set the SASL mechanism in a wrong way. I tried the following:

C++ messaging API: SASL mechanism not set correctly

Hello, I tried to connect to a AMQP Broker via SSL using AMQP 0.10. I used C++ and the Qpid Messaging API version 0.28. It seems like I set the SASL mechanism in a wrong way. I tried the following: const char* QPID_OPTION_TRANSPORT = "transport"; const char* QPID_OPTION_SASL_MECHANISMS = "sas

Re: QpidSender::send() blocks

Sim: On 08/07/2015 09:11 AM, Andreas Welchlin wrote: Hello, I am using the C++ messaging API 0.28 to send AMQP 1.0 messages to an ActiveMQ message broker. Everything worked fine for days but one time the QpidSender::send() command blocked. The sync flag was set to true. The docu says that the

QpidSender::send() blocks

Hello, I am using the C++ messaging API 0.28 to send AMQP 1.0 messages to an ActiveMQ message broker. Everything worked fine for days but one time the QpidSender::send() command blocked. The sync flag was set to true. The docu says that the send call blocks until the server confirms receip

Re: Undefined symbol SystemInfo::getInterfaceAddresses

Hi Raphael, this is an issue only on Solaris 10. Since Solaris 11 it is implemented. Please look into JIIRA: https://issues.apache.org/jira/browse/QPID-6115?filter=-2 and read my last comment. Unfortunately my Solaris implementations never went into the Qpid Branch. Andrew Stitcher planned t

Re: C++ Messaging API: Reading from two different message brokers (now thread safety)

waiting in session.nextReceiver()? Do you see any problems there? Regards, Andreas On 07/21/2015 10:15 AM, Andreas Welchlin wrote: Hello, I wrote an application which reads from two different message brokers. So I used two connections and therefore I got also two sessions. When I have just one session

C++ Messaging API: Reading from two different message brokers

Hello, I wrote an application which reads from two different message brokers. So I used two connections and therefore I got also two sessions. When I have just one session I can just call "qpid::messaging::Session::nextReceiver()". But this is not possible with two sessions. I could call next

C++ API: Connect via SSL to two different Brokers

Hello, I am using the qpid C++ messaging API to connect to AMQP Brokers. There is one process which connects to our internal message broker and at the same time to a third party message broker. So the program openes two sessions and connets to both of them. So far no problem. Now I want to c

Re: qpid 0.28 messaging api: Use Message Selectors with ActiveMQ

That is perfectly right. I tested it and it works. Excellent. Thank you! Andreas Am 05.03.2015 um 13:59 schrieb Gordon Sim: On 03/05/2015 12:50 PM, Andreas Welchlin wrote: Hi Rob, thank you for your answer. I moved the quote and tried this: topicname; {assert: always, link:{filter

Re: qpid 0.28 messaging api: Use Message Selectors with ActiveMQ

of the uniqueAppID attribute is the same as the value of the (presumably not present) ttt_1425468013373341 attribute I'm not familiar enough with the C++ messaging API / addressing to know the syntax for nested quotes/escaping... perhaps someone else can help there. Hope this helps, Rob

qpid 0.28 messaging api: Use Message Selectors with ActiveMQ

Hello, I am using the qpid 0.28 messaging api to connect to an ActiveMQ message broker at a third party. The protocol is AMQP 1.0. This post describes exactly what I need: http://mail-archives.apache.org/mod_mbox/qpid-users/201502.mbox/%3ccafitrpsud4uuqg8e6yjgfz1bnxytvophp6g43no-xbsm5w+...@ma

Re: Transaction Support for AMQP 1.0 (C++ Broker and Client)

, 2014-10-23 at 16:19 +0200, Andreas Welchlin wrote: Hi List, I saw the following message when I wanted to create a transactional session: "Transactions not yet supported" I am currently using qpid 0.28 with AMQP 1.0. In former times when I used AMQP 0.10 the transaction support

Transaction Support for AMQP 1.0 (C++ Broker and Client)

Hi List, I saw the following message when I wanted to create a transactional session: "Transactions not yet supported" I am currently using qpid 0.28 with AMQP 1.0. In former times when I used AMQP 0.10 the transaction support was there. What can I do to get transaction support with AMQP

Re: Duplicate Messages

Hi Steve, I wonder how to check for duplicates, as well. I create topics using --sequence like: qpid-config -b localhost exchange topic test_topic --durable --sequence I understood that the the order of messages is guaranteed, then. This means a duplicate message can only be the

Re: qpid-0.28 - Linker Problem on Solaris

I can also add topics and queues using qpid-config. Unfortunately "make test" fails completely and I will have to dig into this, but I will do it a bit later. Regards, Andreas Am 23.09.2014 um 17:49 schrieb Andrew Stitcher: On Tue, 2014-09-23 at 13:16 +0200, Andreas Welchlin wr

Re: qpid-0.28 - Linker Problem on Solaris

VERSION_EQUAL 4.1.2) Please could someone insert these lines into CMakeLists in the repository? Regards, Andreas PS: If you want to be able to test on Solaris - it is pretty ease to use a predefined virtual machine which is available on the Oracle homepage. Am 22.09.2014 um 15:47 schrieb An

qpid-0.28 - Linker Problem on Solaris

Hi List, I tried to compile qpid-0.28 on Solaris (uname -a prints: SunOS solaris 5.11 11.2 i86pc i386 i86pc). First I amended and compiled proton 0.7 which worked fine. I would like to share this but first I want to do some tests using QPID. Afterwards I tried to compile qpid-0.28: 1.) I

Re: Send a message using C++ which will be a JMS TextMessage

Hallo Gordon, wow, you are so fast! I just went to the kitchen to get a coffee and when I came back I had the correct answer :o) Thank you very much! It works exactly like you said. Regards Andreas Am 08.09.2014 um 15:55 schrieb Gordon Sim: On 09/08/2014 02:43 PM, Andreas Welchlin wrote

Send a message using C++ which will be a JMS TextMessage

Hi List, I am sending messages to a JMS Service which runs at a third party. I use C++ qpid 0.28 with amqp 1.0. When the message is created it looks like this: std::string messageContent("example text"); qpidMessage.setContentType("text/plain"); qpidMessage.setContent(qpid::types::

Re: Unknown protocol: ssl for C++ client

Hi Nidhal, try to give the connection a property list as string like: Connection connection(brokerUrl, "{transport:ssl}"); On my system this works. Please be aware that the property name is "transport" and not "protocol". Regards, Andreas Am 18.08.2014 um 12:57 schrieb nidhal.kort:

Re: C++ Client: SSL connection configuration

Thank you, Gordon! I added the CA-Certificates and it helped. Am 29.07.2014 um 14:05 schrieb Gordon Sim: On 07/29/2014 12:32 PM, Andreas Welchlin wrote: Hi All, currently I am trying to connect to a third party AMQP broker using a c++ client with qpid 0.28. The broker is configured to use

C++ Client: SSL connection configuration

Hi All, currently I am trying to connect to a third party AMQP broker using a c++ client with qpid 0.28. The broker is configured to use ssl. The client uses a self signed certificate. This certificate is available in the broker. I created the self signed certificate and added it into my ce

Re: QPid 0.28 amqp1.0 - sending map from java to c++ does not work

Am 21.07.2014 13:52, schrieb Gordon Sim: On 07/21/2014 12:28 PM, Andreas Welchlin wrote: No, I am not using getContentObject but the decode function: Ok, that is the problem. You need to use getContentObject() for AMQP 1.0 messages. You can use that for 0-10 also and it works regardless of

Re: QPid 0.28 amqp1.0 - sending map from java to c++ does not work

Hi Gordon, Cool! I tried it and it works. Thank you very much! This workaround helps me very much. Cheers Andreas Am 21.07.2014 13:28, schrieb Andreas Welchlin: Hi Gordon, thank you for your answer. I am also using the c++ broker (0.28). >How are you getting the content using q

Re: QPid 0.28 amqp1.0 - sending map from java to c++ does not work

mSystemMessageId.assign(map["SytemMsgId"].asString()); mContent = map["content"].asString(); } Regards, Andreas Am 21.07.2014 13:20, schrieb Gordon Sim: On 07/18/2014 02:25 PM, Andreas Welchlin wrote: Hi List, I used Hello.java from "qpid-java-amqp-1-0-client-jms-0.28.

Re: QPid 0.28 amqp1.0 - sending map from java to c++ does not work

for (QpidMapCIt it = properties.begin(); it != properties.end(); ++it) { fields.push_back(MsgField(it->first, it->second.asString())); } } Do you think this is a bug in QPID or is there something wrong with my code? Regards, Andreas Am 18.07.2014 15:25, schrieb Andreas Welc

QPid 0.28 amqp1.0 - sending map from java to c++ does not work

Hi List, I used Hello.java from "qpid-java-amqp-1-0-client-jms-0.28.tar.gz" to send an amqp 1.0 message which contains a map to an exchange. Java Code: --- MapMessage mapmessage = producer

Java Qpid 0.28 amqp1.0 JMS

Hi List, when moving a JMS program to the amqp 1.0 the following needs to be changed (I just want to mention this on the mailing list because it cost me some hours to find out). If you used an older version of qpid-all.jar your property file may contain someting like: destination.topic

Qpid Client API logging

Hi All, Sometimes I find it very useful to switch the client api logging on. The user interface is powerful but also not too comfortable. So what about providing a little interface for easy usage as an example in the next Qpid release? Maybe something like this header file QpidApiLogger.h:

Re: qpid broker ssl plugin - start using systemctl fails

erver_db/secmod.db", O_RDONLY) = 11 My fault was that the upper directory /home/noname hat no read permission for "group" and "other". Now it runs with systemctl as user qpidd. Thank you very much, Gordon! Am 10.06.2014 13:38, schrieb Andreas Welchlin: Am 1

Re: qpid broker ssl plugin - start using systemctl fails

Am 10.06.2014 11:49, schrieb Gordon Sim: On 06/10/2014 10:38 AM, Andreas Welchlin wrote: Am 10.06.2014 11:37, schrieb Gordon Sim: On 06/10/2014 10:13 AM, Andreas Welchlin wrote: Am 10.06.2014 10:51, schrieb Gordon Sim: On 06/10/2014 09:28 AM, Andreas Welchlin wrote: Am 09.06.2014 10:38

Re: qpid broker ssl plugin - start using systemctl fails

Am 10.06.2014 11:37, schrieb Gordon Sim: On 06/10/2014 10:13 AM, Andreas Welchlin wrote: Am 10.06.2014 10:51, schrieb Gordon Sim: On 06/10/2014 09:28 AM, Andreas Welchlin wrote: Am 09.06.2014 10:38, schrieb Gordon Sim: On 06/07/2014 09:22 PM, Andreas Welchlin wrote: Hi All, I started the

Re: qpid broker ssl plugin - start using systemctl fails

Am 10.06.2014 10:51, schrieb Gordon Sim: On 06/10/2014 09:28 AM, Andreas Welchlin wrote: Am 09.06.2014 10:38, schrieb Gordon Sim: On 06/07/2014 09:22 PM, Andreas Welchlin wrote: Hi All, I started the qpidd broker on a fedora 9 using "sytemctl start qpidd.service". But the initial

Re: qpid broker ssl plugin - start using systemctl fails

Am 09.06.2014 10:38, schrieb Gordon Sim: On 06/07/2014 09:22 PM, Andreas Welchlin wrote: Hi All, I started the qpidd broker on a fedora 9 using "sytemctl start qpidd.service". But the initialisation of the SSL plugin failed: [Security] error Failed to initialise SSL plugin: Failed:

qpid broker ssl plugin - start using systemctl fails

Hi All, I started the qpidd broker on a fedora 9 using "sytemctl start qpidd.service". But the initialisation of the SSL plugin failed: [Security] error Failed to initialise SSL plugin: Failed: NSS error [-8015] (/builddir/build/BUILD/qpid-0.24/cpp/src/qpid/sys/ssl/util.cpp:100) When I sta

Re: Connection setOption "protocol" is not possible

Thank you, Gordon! Am 05.06.2014 12:44, schrieb Gordon Sim: On 06/05/2014 10:40 AM, Andreas Welchlin wrote: I tried to establish an AMQP connection using ssl. So I used (after reading the book "Using the Qpid Messaging API"): Connection connection("localhost:5672");

Connection setOption "protocol" is not possible

Hi All, I tried to establish an AMQP connection using ssl. So I used (after reading the book "Using the Qpid Messaging API"): Connection connection("localhost:5672"); connection.setOption("protocol", "ssl"); connection.open(); But this failed with an exception: "Invalid option: protocol not