RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual Studio 2013 Win64
Thank you Steve! Can you please point me out to the code which parses the log? I would like to locally add an ignore on the SSL error to make sure I have no other failures. Regarding the setup of the certificate, are there more specific information on what the certificate should contain, etc? Regards,Adel > From: shus...@riverace.com > To: users@qpid.apache.org > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > Studio 2013 Win64 > Date: Mon, 4 Apr 2016 16:11:13 + > > The test is failing because the test script looks through the log for errors > and flags the SSL error. It isn't perfect and should be worked on, but at > this point in time you can safely ignore that particular error. > > -Steve > > > -Original Message- > > From: Adel Boutros [mailto:adelbout...@live.com] > > Sent: Monday, April 04, 2016 12:06 PM > > To: users@qpid.apache.org > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > > Studio 2013 Win64 > > > > Hello Steve, > > This is the full output given. If what you are saying is correct, then I > > don't > > understand why the test is failing. > > Do you think there is an easy way to find out? Do you need some extra > > information? > > Regards,Adel > > > > > From: shus...@riverace.com > > > To: users@qpid.apache.org > > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with > > > Visual Studio 2013 Win64 > > > Date: Mon, 4 Apr 2016 15:47:16 + > > > > > > Hi Adel, > > > > > > Those messages are expected unless you set up a certificate, and do not > > indicate a failure of the actual test. > > > > > > -Steve > > > > > > > -Original Message- > > > > From: Adel Boutros [mailto:adelbout...@live.com] > > > > Sent: Sunday, April 03, 2016 2:15 PM > > > > To: users@qpid.apache.org > > > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with > > > > Visual Studio 2013 Win64 > > > > > > > > Hello, > > > > Did anyone have the time to check the below? > > > > Regards,Adel > > > > > > > > From: adelbout...@live.com > > > > To: users@qpid.apache.org > > > > Subject: Qpid C++ Broker 0.34 failing unit tests on Windows with > > > > Visual Studio > > > > 2013 Win64 > > > > Date: Wed, 30 Mar 2016 19:19:07 +0200 > > > > > > > > > > > > > > > > > > > > Hello, > > > > I have compiled Qpid C++ broker 0.34 with Boost 1.55.0 and Qpid > > > > Proton > > > > 0.12.0 using Visual Studio 2013 Win64 compiler. > > > > The compilation is successful however all unit tests are failing > > > > with the same exception which is related to certificates and SASL > > > > despite the fact that when running a configure with cmake, it didn't > > locate SASL libraries. > > > > Please note that the same tests are running correctly on Linux using > > > > gcc 4.9 Can you please assist? > > > > Full log of cmake and the test are attached to this mail ctest -R > > > > qpid-client- test -V2: 2016-03-30 19:02:17 [Broker] notice Broker > > (pid=60712) start-up2: > > > > 2016-03-30 19:02:17 [Broker] notice SASL disabled: No Authentication > > > > Performed2: 2016-03-30 19:02:17 [Security] error Failed to > > > > initialise SSL > > > > listener: Locating certificate green-win-slave in store My Cannot > > > > find object or property. > > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > > :184) > > > > 2: 2016-03-30 19:02:17 [Network] notice Listening on TCP/TCP6 port > > 539832: > > > > 2016-03-30 19:02:17 [Security] warning SASL: No Authentication > > Performed2: > > > > 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) shut-down2: > > > > WARNING: suspicious log entries in > > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\\qpid-client-test- > > > > qpidd.log:\nD:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-tes > > > > t- > > > > qpidd.log:3:2016-03-30 18:57:53 [Security] error Failed to initialise > > > > SSL > > listener: > > > > Locating certificate green-win-slave in store My Cannot find object > > > > or property. > > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > > :184) > > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > > 5:2016- > > > > 03-30 18:57:53 [Security] warning SASL: No Authentication Performed > > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > > 9:2016- > > > > 03-30 19:02:17 [Security] error Failed to initialise SSL listener: > > > > Locating certificate green-win-slave in store My Cannot find object or > > property. > > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > > :184) > > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > > 11:2016- > > > > 03-30 19:02:17 [Security] warning SASL: No Authentication Performed > > > > Regards, Adel Boutroswww.murex.com > > > > > > > > > > > > - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For >
Unroutable messages in Java Qpid Broker 6.0.0
Hello,
In the documentation of Qpid Java Broker 6.0.0, it is mentioned here that
unroutable messages will be discarded eventually.
I have a test where a queue is bound to a topic and a message is sent which
doesn't match the binding filter on purpose. Instead of the message being just
discarded, the sender is receiving an error informing him the message was
rejected.
Is this expected? shouldn't the sender be "warned" instead of getting an
exception?
Another workaround is to implement a "default" queue which will be called from
the alternate exchange but I prefer to check with you this behaviour before
implementing the workaround.
Test caseCreate topic "T"Create queue "Q"Create binding between T and Q using a
binding key BK1Have a consumer listen to QHave a sender send to T a message
with a binding key BK2
Output client-sidejavax.jms.JMSException: Unknown error from remote peer
at
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:125)
at
org.apache.qpid.jms.provider.amqp.AmqpFixedProducer.processDeliveryUpdates(AmqpFixedProducer.java:232)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.processUpdates(AmqpProvider.java:804)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider.access$1900(AmqpProvider.java:92)
at
org.apache.qpid.jms.provider.amqp.AmqpProvider$17.run(AmqpProvider.java:701) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at
java.util.concurrent.FutureTask.run(FutureTask.java:262) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Checking the code of org.apache.qpid.server.exchange.AbstractExchange#send,
when a queue is not found in the routing table of the Exchange and no alternate
exchange is defined, then the message is considered as
org.apache.qpid.amqp_1_0.type.messaging.Rejected. This is what the
org.apache.qpid.amqp_1_0.type.Outcome has as value. Then client side, the code
checks the value of the Outcome and sets an error in case it was rejected.
org.apache.qpid.jms.provider.amqp.AmqpFixedProducer#processDeliveryUpdates}
else if (outcome instanceof Rejected) {
LOG.trace("Outcome of delivery was rejected: {}", delivery);
ErrorCondition remoteError = ((Rejected) outcome).getError();
if (remoteError == null) {
remoteError = getEndpoint().getRemoteCondition();
}
deliveryError = AmqpSupport.convertToException(remoteError);
}
Regards,
Adel Boutroswww.murex.com
RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual Studio 2013 Win64
The test is failing because the test script looks through the log for errors and flags the SSL error. It isn't perfect and should be worked on, but at this point in time you can safely ignore that particular error. -Steve > -Original Message- > From: Adel Boutros [mailto:adelbout...@live.com] > Sent: Monday, April 04, 2016 12:06 PM > To: users@qpid.apache.org > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > Studio 2013 Win64 > > Hello Steve, > This is the full output given. If what you are saying is correct, then I don't > understand why the test is failing. > Do you think there is an easy way to find out? Do you need some extra > information? > Regards,Adel > > > From: shus...@riverace.com > > To: users@qpid.apache.org > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with > > Visual Studio 2013 Win64 > > Date: Mon, 4 Apr 2016 15:47:16 + > > > > Hi Adel, > > > > Those messages are expected unless you set up a certificate, and do not > indicate a failure of the actual test. > > > > -Steve > > > > > -Original Message- > > > From: Adel Boutros [mailto:adelbout...@live.com] > > > Sent: Sunday, April 03, 2016 2:15 PM > > > To: users@qpid.apache.org > > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with > > > Visual Studio 2013 Win64 > > > > > > Hello, > > > Did anyone have the time to check the below? > > > Regards,Adel > > > > > > From: adelbout...@live.com > > > To: users@qpid.apache.org > > > Subject: Qpid C++ Broker 0.34 failing unit tests on Windows with > > > Visual Studio > > > 2013 Win64 > > > Date: Wed, 30 Mar 2016 19:19:07 +0200 > > > > > > > > > > > > > > > Hello, > > > I have compiled Qpid C++ broker 0.34 with Boost 1.55.0 and Qpid > > > Proton > > > 0.12.0 using Visual Studio 2013 Win64 compiler. > > > The compilation is successful however all unit tests are failing > > > with the same exception which is related to certificates and SASL > > > despite the fact that when running a configure with cmake, it didn't > locate SASL libraries. > > > Please note that the same tests are running correctly on Linux using > > > gcc 4.9 Can you please assist? > > > Full log of cmake and the test are attached to this mail ctest -R > > > qpid-client- test -V2: 2016-03-30 19:02:17 [Broker] notice Broker > (pid=60712) start-up2: > > > 2016-03-30 19:02:17 [Broker] notice SASL disabled: No Authentication > > > Performed2: 2016-03-30 19:02:17 [Security] error Failed to > > > initialise SSL > > > listener: Locating certificate green-win-slave in store My Cannot > > > find object or property. > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > :184) > > > 2: 2016-03-30 19:02:17 [Network] notice Listening on TCP/TCP6 port > 539832: > > > 2016-03-30 19:02:17 [Security] warning SASL: No Authentication > Performed2: > > > 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) shut-down2: > > > WARNING: suspicious log entries in > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\\qpid-client-test- > > > qpidd.log:\nD:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-tes > > > t- > > > qpidd.log:3:2016-03-30 18:57:53 [Security] error Failed to initialise SSL > listener: > > > Locating certificate green-win-slave in store My Cannot find object > > > or property. > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > :184) > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > 5:2016- > > > 03-30 18:57:53 [Security] warning SASL: No Authentication Performed > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > 9:2016- > > > 03-30 19:02:17 [Security] error Failed to initialise SSL listener: > > > Locating certificate green-win-slave in store My Cannot find object or > property. > > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp > > > :184) > > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log: > > > 11:2016- > > > 03-30 19:02:17 [Security] warning SASL: No Authentication Performed > > > Regards, Adel Boutroswww.murex.com > > > > > > > > > - 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: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual Studio 2013 Win64
Hello Steve, This is the full output given. If what you are saying is correct, then I don't understand why the test is failing. Do you think there is an easy way to find out? Do you need some extra information? Regards,Adel > From: shus...@riverace.com > To: users@qpid.apache.org > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > Studio 2013 Win64 > Date: Mon, 4 Apr 2016 15:47:16 + > > Hi Adel, > > Those messages are expected unless you set up a certificate, and do not > indicate a failure of the actual test. > > -Steve > > > -Original Message- > > From: Adel Boutros [mailto:adelbout...@live.com] > > Sent: Sunday, April 03, 2016 2:15 PM > > To: users@qpid.apache.org > > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > > Studio 2013 Win64 > > > > Hello, > > Did anyone have the time to check the below? > > Regards,Adel > > > > From: adelbout...@live.com > > To: users@qpid.apache.org > > Subject: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > > Studio > > 2013 Win64 > > Date: Wed, 30 Mar 2016 19:19:07 +0200 > > > > > > > > > > Hello, > > I have compiled Qpid C++ broker 0.34 with Boost 1.55.0 and Qpid Proton > > 0.12.0 using Visual Studio 2013 Win64 compiler. > > The compilation is successful however all unit tests are failing with the > > same > > exception which is related to certificates and SASL despite the fact that > > when > > running a configure with cmake, it didn't locate SASL libraries. > > Please note that the same tests are running correctly on Linux using gcc 4.9 > > Can you please assist? > > Full log of cmake and the test are attached to this mail ctest -R > > qpid-client- > > test -V2: 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) start-up2: > > 2016-03-30 19:02:17 [Broker] notice SASL disabled: No Authentication > > Performed2: 2016-03-30 19:02:17 [Security] error Failed to initialise SSL > > listener: Locating certificate green-win-slave in store My Cannot find > > object > > or property. > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > > 2: 2016-03-30 19:02:17 [Network] notice Listening on TCP/TCP6 port 539832: > > 2016-03-30 19:02:17 [Security] warning SASL: No Authentication Performed2: > > 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) shut-down2: > > WARNING: suspicious log entries in > > D:\qpid.git\qpid\cpp\build_dir\src\tests\\qpid-client-test- > > qpidd.log:\nD:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test- > > qpidd.log:3:2016-03-30 18:57:53 [Security] error Failed to initialise SSL > > listener: > > Locating certificate green-win-slave in store My Cannot find object or > > property. > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:5:2016- > > 03-30 18:57:53 [Security] warning SASL: No Authentication Performed > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:9:2016- > > 03-30 19:02:17 [Security] error Failed to initialise SSL listener: Locating > > certificate green-win-slave in store My Cannot find object or property. > > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:11:2016- > > 03-30 19:02:17 [Security] warning SASL: No Authentication Performed > > Regards, > > Adel Boutroswww.murex.com > > > > - > > 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 >
Question: Temporary queues: set up and when do they go away?
As subject states.
Unclear how use so of the Address options as they are described.
How do I set up a temporary queue that goes away when the receiver is closed?
I am using the following in my code to set up a response queue.
What has me asking this question is that using qpid-cofig I can see that before
I run my example applications there is only 1 non-durable queue. But well
after my example applications finishes (receivers and senders are closed) I see
2 non-durable queues. Shouldn't the queue be deleted and not appear at all
when I run qpidd-configure? What am I doing incorrectly?
"const char* response_queue="#response_queue; {create: always, delete: always}"
Thanks for your help it is appreciated!
Paul
This communication (including any attachments) may contain information that is
proprietary, confidential or exempt from disclosure. If you are not the
intended recipient, please note that further dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who received
this message in error should notify the sender immediately by telephone or by
return email and delete it from his or her computer.
RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual Studio 2013 Win64
Hi Adel, Those messages are expected unless you set up a certificate, and do not indicate a failure of the actual test. -Steve > -Original Message- > From: Adel Boutros [mailto:adelbout...@live.com] > Sent: Sunday, April 03, 2016 2:15 PM > To: users@qpid.apache.org > Subject: RE: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual > Studio 2013 Win64 > > Hello, > Did anyone have the time to check the below? > Regards,Adel > > From: adelbout...@live.com > To: users@qpid.apache.org > Subject: Qpid C++ Broker 0.34 failing unit tests on Windows with Visual Studio > 2013 Win64 > Date: Wed, 30 Mar 2016 19:19:07 +0200 > > > > > Hello, > I have compiled Qpid C++ broker 0.34 with Boost 1.55.0 and Qpid Proton > 0.12.0 using Visual Studio 2013 Win64 compiler. > The compilation is successful however all unit tests are failing with the same > exception which is related to certificates and SASL despite the fact that when > running a configure with cmake, it didn't locate SASL libraries. > Please note that the same tests are running correctly on Linux using gcc 4.9 > Can you please assist? > Full log of cmake and the test are attached to this mail ctest -R qpid-client- > test -V2: 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) start-up2: > 2016-03-30 19:02:17 [Broker] notice SASL disabled: No Authentication > Performed2: 2016-03-30 19:02:17 [Security] error Failed to initialise SSL > listener: Locating certificate green-win-slave in store My Cannot find object > or property. > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > 2: 2016-03-30 19:02:17 [Network] notice Listening on TCP/TCP6 port 539832: > 2016-03-30 19:02:17 [Security] warning SASL: No Authentication Performed2: > 2016-03-30 19:02:17 [Broker] notice Broker (pid=60712) shut-down2: > WARNING: suspicious log entries in > D:\qpid.git\qpid\cpp\build_dir\src\tests\\qpid-client-test- > qpidd.log:\nD:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test- > qpidd.log:3:2016-03-30 18:57:53 [Security] error Failed to initialise SSL > listener: > Locating certificate green-win-slave in store My Cannot find object or > property. > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:5:2016- > 03-30 18:57:53 [Security] warning SASL: No Authentication Performed > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:9:2016- > 03-30 19:02:17 [Security] error Failed to initialise SSL listener: Locating > certificate green-win-slave in store My Cannot find object or property. > (D:\qpid.git\qpid\cpp\src\qpid\broker\windows\SslProtocolFactory.cpp:184) > D:\qpid.git\qpid\cpp\build_dir\src\tests\qpid-client-test-qpidd.log:11:2016- > 03-30 19:02:17 [Security] warning SASL: No Authentication Performed > Regards, > Adel Boutroswww.murex.com > > - > 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: Help!: Generation of a unique queue name... weird results..OR
Thanks Robbie. Helped to clarify what is going on!
Which spurs question about temporary queues and when queues are deleted. That
will be another question for the discussion board!
From: Robbie Gemmell [robbie.gemm...@gmail.com]
Sent: Monday, April 04, 2016 9:37 AM
To: users@qpid.apache.org
Subject: Re: Help!: Generation of a unique queue name... weird results..OR
The general process is typically to establish somewhere for responses
to go and start listening for them, send messages requiring response,
process responses as they arrive. Not unlike a traditional message in
an envelope. You can of course play with that order if for example you
were using either pre-existing queues or deterministically-named
auto-created queues.
As shown in the client example Gordon pointed to, creating a receiver
using "#" also creates a temporary queue with unique name on the
broker. Once that completes you can then ask for the address of the
temporary queue, which is where that receiver is now consuming from
and thus where replies to it should be sent. You then set that address
as the reply-to value on any outgoing messages where you want
recipients to send replies back to that queue/receiver. Folks
receiving such messages then retrieve the reply-to address from the
message and send their reponse to it.
Robbie
On 4 April 2016 at 14:47, Flores, Paul A. wrote:
> Gordon,
>
> So am I right in understanding that after I generate a "reply to" address I
> should create a receiver so as to instantiate that queue before I send the
> message populated with the "reply to" address? So the order in which a "reply
> to" address is utilized 'matters'? A unique "reply to' queue must be created
> by a receiver before a sender attempts to utilize that queue?
>
> Paul
>
>
> From: Gordon Sim [g...@redhat.com]
> Sent: Sunday, April 03, 2016 12:06 PM
> To: users@qpid.apache.org
> Subject: Re: Help!: Generation of a unique queue name... weird results..OR
>
> On 01/04/16 21:00, Flores, Paul A. wrote:
>> So here is the situation.
>>
>>
>>
>> I have a requester that is doing the following:
>>
>> const char* response_queue="#response_queue; {create: always}";
>> message.setReplyTo(Address(response_queue));
>>
>>
>>
>> The responder that receives the message but when it tries
>>
>> Address reply_to_address=request_message.getReplyTo();
>>
>> Sender reply_sender = session.createSender(reply_to_address);
>>
>>
>>
>> I am seeing:
>>
>> 2016-04-01 13:41:16 [Client] warning Exception received from broker:
>> not-found: Queue not found:
>> eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue
>> (/home/pflores/shop/qpid-cpp-0.34/src/qpid/broker/QueueRegistry.cpp:127)
>> [caused by 9 \x08:\x01]
>> Queue eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue does not exist
>>
>>
>>
>> Any insights /help/comments/suggestions?
>
> Have a look at client.cpp in examples/messaging. You can use
> receiver.getAddress() to get the actual address you are using for the
> receiver on which you are waiting for replies. The queue is only created
> when there is a receiver.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
>
> This communication (including any attachments) may contain information that
> is proprietary, confidential or exempt from disclosure. If you are not the
> intended recipient, please note that further dissemination, distribution, use
> or copying of this communication is strictly prohibited. Anyone who received
> this message in error should notify the sender immediately by telephone or by
> return email and delete it from his or her computer.
>
> -
> 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
This communication (including any attachments) may contain information that is
proprietary, confidential or exempt from disclosure. If you are not the
intended recipient, please note that further dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who received
this message in error should notify the sender immediately by telephone or by
return email and delete it from his or her computer.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
[RESULT] [VOTE] merge the proton mailing list into the users/dev lists
There were 13 binding +1 votes received and another 2 from users, with no other votes received. The vote has passed. I'll chat with infra in the days ahead about how things proceed. Robbie - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: Help!: Generation of a unique queue name... weird results..OR
The general process is typically to establish somewhere for responses
to go and start listening for them, send messages requiring response,
process responses as they arrive. Not unlike a traditional message in
an envelope. You can of course play with that order if for example you
were using either pre-existing queues or deterministically-named
auto-created queues.
As shown in the client example Gordon pointed to, creating a receiver
using "#" also creates a temporary queue with unique name on the
broker. Once that completes you can then ask for the address of the
temporary queue, which is where that receiver is now consuming from
and thus where replies to it should be sent. You then set that address
as the reply-to value on any outgoing messages where you want
recipients to send replies back to that queue/receiver. Folks
receiving such messages then retrieve the reply-to address from the
message and send their reponse to it.
Robbie
On 4 April 2016 at 14:47, Flores, Paul A. wrote:
> Gordon,
>
> So am I right in understanding that after I generate a "reply to" address I
> should create a receiver so as to instantiate that queue before I send the
> message populated with the "reply to" address? So the order in which a "reply
> to" address is utilized 'matters'? A unique "reply to' queue must be created
> by a receiver before a sender attempts to utilize that queue?
>
> Paul
>
>
> From: Gordon Sim [g...@redhat.com]
> Sent: Sunday, April 03, 2016 12:06 PM
> To: users@qpid.apache.org
> Subject: Re: Help!: Generation of a unique queue name... weird results..OR
>
> On 01/04/16 21:00, Flores, Paul A. wrote:
>> So here is the situation.
>>
>>
>>
>> I have a requester that is doing the following:
>>
>> const char* response_queue="#response_queue; {create: always}";
>> message.setReplyTo(Address(response_queue));
>>
>>
>>
>> The responder that receives the message but when it tries
>>
>> Address reply_to_address=request_message.getReplyTo();
>>
>> Sender reply_sender = session.createSender(reply_to_address);
>>
>>
>>
>> I am seeing:
>>
>> 2016-04-01 13:41:16 [Client] warning Exception received from broker:
>> not-found: Queue not found:
>> eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue
>> (/home/pflores/shop/qpid-cpp-0.34/src/qpid/broker/QueueRegistry.cpp:127)
>> [caused by 9 \x08:\x01]
>> Queue eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue does not exist
>>
>>
>>
>> Any insights /help/comments/suggestions?
>
> Have a look at client.cpp in examples/messaging. You can use
> receiver.getAddress() to get the actual address you are using for the
> receiver on which you are waiting for replies. The queue is only created
> when there is a receiver.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>
>
> This communication (including any attachments) may contain information that
> is proprietary, confidential or exempt from disclosure. If you are not the
> intended recipient, please note that further dissemination, distribution, use
> or copying of this communication is strictly prohibited. Anyone who received
> this message in error should notify the sender immediately by telephone or by
> return email and delete it from his or her computer.
>
> -
> 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: Help!: Generation of a unique queue name... weird results..OR
Gordon,
So am I right in understanding that after I generate a "reply to" address I
should create a receiver so as to instantiate that queue before I send the
message populated with the "reply to" address? So the order in which a "reply
to" address is utilized 'matters'? A unique "reply to' queue must be created
by a receiver before a sender attempts to utilize that queue?
Paul
From: Gordon Sim [g...@redhat.com]
Sent: Sunday, April 03, 2016 12:06 PM
To: users@qpid.apache.org
Subject: Re: Help!: Generation of a unique queue name... weird results..OR
On 01/04/16 21:00, Flores, Paul A. wrote:
> So here is the situation.
>
>
>
> I have a requester that is doing the following:
>
> const char* response_queue="#response_queue; {create: always}";
> message.setReplyTo(Address(response_queue));
>
>
>
> The responder that receives the message but when it tries
>
> Address reply_to_address=request_message.getReplyTo();
>
> Sender reply_sender = session.createSender(reply_to_address);
>
>
>
> I am seeing:
>
> 2016-04-01 13:41:16 [Client] warning Exception received from broker:
> not-found: Queue not found:
> eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue
> (/home/pflores/shop/qpid-cpp-0.34/src/qpid/broker/QueueRegistry.cpp:127)
> [caused by 9 \x08:\x01]
> Queue eb67d5b2-8c95-4338-9a01-f8017bbae223#response_queue does not exist
>
>
>
> Any insights /help/comments/suggestions?
Have a look at client.cpp in examples/messaging. You can use
receiver.getAddress() to get the actual address you are using for the
receiver on which you are waiting for replies. The queue is only created
when there is a receiver.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
This communication (including any attachments) may contain information that is
proprietary, confidential or exempt from disclosure. If you are not the
intended recipient, please note that further dissemination, distribution, use
or copying of this communication is strictly prohibited. Anyone who received
this message in error should notify the sender immediately by telephone or by
return email and delete it from his or her computer.
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
accept() method in Proton/Python BlockingConnection
Hi, I was playing with the Python binding for Proton - in particular with the BlockingConnection. I noticed following behavior with the BlockingReceiver: - When I use the receiver to receive several messages without settling them and call accept afterwards, it accepts only one message. My original expectation was that it would accept all unsettled messages. - When I call accept() without receiving any message, I get following exception: Traceback (most recent call last): File "/home/schojak/amqp/pycharm-projects/Python-Code-Examples/proton_binding/BlockingBroadcastReceiver.py", line 67, in br.run() File "/home/schojak/amqp/pycharm-projects/Python-Code-Examples/proton_binding/BlockingBroadcastReceiver.py", line 35, in run receiver.accept() File "/usr/lib/python2.7/dist-packages/proton/utils.py", line 143, in accept self.settle(Delivery.ACCEPTED) File "/usr/lib/python2.7/dist-packages/proton/utils.py", line 157, in settle self.fetcher.settle(state) File "/usr/lib/python2.7/dist-packages/proton/utils.py", line 116, in settle delivery = self.unsettled.popleft() IndexError: pop from an empty deque Are these two bugs? Or is this expected behavior? Thanks & Regards Jakub
Re: [c++] Multi-threaded proton and C++11
I completely agree Alan. We have recently been doing something very similar internally in C++03 and the C++11 primitives are sourly missed. We have managed to not use std::function by having a certain number of hardcoded events which can be sent to a connection engine and using custom promises/futures to retrieve the result. Overall a lot of complexity is added by reimplementing features which are available in C++11. On Fri, Apr 1, 2016 at 5:47 PM, Alan Conway wrote: > I am working on a multi-threaded broker example for proton C++ and I am > becoming more and more convinced that it doesn't make much sense to try > to do this without C++11. > > There are two classes of issue: > > API: > - inject() needs a way to represent a callback function. Without > std::function this is very difficult. > - for memory-safe multi-threaded we will need to expose > shared_ptr/unique_ptr in the public API (the proton refcounting scheme > is not thread safe.) > > Implementation: initially the multi-threaded broker impl will be > independent of the single-threaded proton core but at some point we > will want to provide some thread-safe toolkit as part of the C++ API, > which internally needs atomics, mutexes etc. > > Originally we talked about keeping proton based on C++03. I'd like to > propose we maintain that for the single-threaded but use C++11 in > thread-safe and shared_ptr extensions. > > If someone wants to add a boost version of those extensions at some > point that would be fine by me, but I plan to work initially with > C++11. > > Thoughts? > Alan. > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > >
