Re: Negative Bytes Credit
I will try to get that information to you asap. Do you know if this error messages signifies something impactful? Functionally, the broker appears to be doing fine. Our throughput has not not decreased and most vitals, e.g. heap memory, look okay. -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: Qpid Broker-J - configure alternate binding in Node auto creation policy
Hi Timo, Surprisingly, you can "auto-create" both your main queue and dead letter queue using auto-creation policies. For instance, for your main queues you can create policy matching regular expression like so "^.*(? wrote: > Hi, > > I'm trying to set up qpid broker-J so that each of my queues gets a > DLQ/alternate Binding. I'm using an auto create policy to have queues > dynamically created on first use by a JMS client. > > Unfortunately I haven't found a way to accomplish this. Ideally I'm looking > for something similar to the deadLetterStrategy in ActiveMQ, where I can > configure a prefix in one global setting that gets used to set up and name > DLQs. > > As described > here:http://activemq.apache.org/message-redelivery-and-dlq-handling > > Is there anything similar in QPid? What would be the alternative? Use AMQP > management calls from the client to create my queues and setup > alternateBindings? > > Thanks > Timo > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > - > 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
[RESULT] [VOTE] Release Apache Qpid Dispatch 1.8.0
There were 5 binding +1 votes, no other votes received. The vote has passed. I will add the files to the dist release repo and create the final tag shortly. The website will be updated after the release has had time to sync to the mirrors. Thanks to everybody for testing/voting. - 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.8.0 (RC1)
+1 * Validated signatures and checksums * Checked for presence of LICENSE and NOTICE files * Ran mvn apache-rat:check, no files with missing license headers found. * Built from source against Proton 0.28.0 in Fedora 29 and ran system tests. On Fri, Jun 7, 2019 at 11:23 AM Ganesh Murthy wrote: > > Hello All, > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.8.0. > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > The following features, improvements, and bug fixes are introduced in 1.8.0: > > Features - >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > Improvements - > DISPATCH-1308 - Console access to the force-close a connection feature > DISPATCH-1320 - Make it easier to use separate logos for upstream > and downstream masthead > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > when they are found in nonstandard location > DISPATCH-1329 - Edge router system test needs skip test convenience > switches > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > popup > DISPATCH-1341 - Add list of delayed links to console's overview page > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > DISPATCH-1356 - Remove the dotted line around routers that > indicates the router is fixed. > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > Bug fixes - > DISPATCH-974 - Getting connections via the router management > protocol causes AMQP framing errors > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - system_tests_ssl > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > DISPATCH-1317 - HTTP system test is failing on python2.6 > DISPATCH-1318 - edge_router system test failing > DISPATCH-1322 - Edge router drops disposition when remote receiver closes > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > autoLink entity. Add address and externalAddress instead. > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > DISPATCH-1325 - Sender connections to edge router that connect > 'too soon' never get credit > DISPATCH-1326 - Anonymous messages are released by edge router > even if there is a receiver for the messages > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > decrement on link detach > DISPATCH-1334 - Background map on topology page incorrect height > DISPATCH-1335 - After adding client, topology page shows new icon > in upper-left corner > DISPATCH-1339 - Multiple consoles attached to a router are showing > as separate icons > > > Thanks. - 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.8.0 (RC1)
+1 from me build and unit test on Ubuntu 18 ok oslo.messaging smoke test ok On Fri, Jun 7, 2019 at 11:24 AM Ganesh Murthy wrote: > Hello All, > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.8.0. > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > The following features, improvements, and bug fixes are introduced in > 1.8.0: > > Features - >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > Improvements - > DISPATCH-1308 - Console access to the force-close a connection feature > DISPATCH-1320 - Make it easier to use separate logos for upstream > and downstream masthead > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > when they are found in nonstandard location > DISPATCH-1329 - Edge router system test needs skip test convenience > switches > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > popup > DISPATCH-1341 - Add list of delayed links to console's overview page > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > DISPATCH-1356 - Remove the dotted line around routers that > indicates the router is fixed. > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > Bug fixes - > DISPATCH-974 - Getting connections via the router management > protocol causes AMQP framing errors > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > system_tests_ssl > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > DISPATCH-1317 - HTTP system test is failing on python2.6 > DISPATCH-1318 - edge_router system test failing > DISPATCH-1322 - Edge router drops disposition when remote receiver > closes > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > autoLink entity. Add address and externalAddress instead. > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > DISPATCH-1325 - Sender connections to edge router that connect > 'too soon' never get credit > DISPATCH-1326 - Anonymous messages are released by edge router > even if there is a receiver for the messages > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > decrement on link detach > DISPATCH-1334 - Background map on topology page incorrect height > DISPATCH-1335 - After adding client, topology page shows new icon > in upper-left corner > DISPATCH-1339 - Multiple consoles attached to a router are showing > as separate icons > > > Thanks. > > - > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > > -- -K
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
On Tue, Jun 11, 2019 at 12:21 PM Michael Goulish wrote: > executive summary: I change my vote to *+1* > > but with JIRAs. > > > OK! I have something. > > I didn't remember it, but my notes show that I have seen this exact failure > before, also after a clean install. > ( I mean the authz failure. The other one, the http failure is already > explained.) > > So this means that the problem has got to be with my machine setup --- > there is some package that the authz test requires that I do not install > after a clean OS upgrade. > > I do have a great plethora of SASL and SSL packages installed, so I don't > know what it might be, and I am having trouble tracing into the Python > code. If anyone has a clue, please let me know. > > But, since the problem is limited to the test not warning about a required > package, I will do two things: > > 1. raise a JIRA, > > 2. and change my vote to > > *+1* > YAY! Thanks Mick > > > > > On Tue, Jun 11, 2019 at 12:04 PM Ganesh Murthy wrote: > > > On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish > > wrote: > > > > > Of course I will not change my vote based on a suggestion ( from me and > > > Gordon ) that the failure I am seeing might be caused by a missing > > > package. > > > > > > What I will do is start looking into this to see if that is indeed the > > > case. > > > And then we will make a change that detects and warns about that case. > > > And then I will change my vote. > > > > > Agreed, fair enough. > > > > > > > > > > > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke > wrote: > > > > > > > +1 > > > > > > > > * Checked checksums > > > > * Build/test Fedora 29, python 3 > > > > * Fails system_tests_http (known problem, not a regression) > > > > * Build/test Fedora 28, python 2 > > > > * Occasional test fail system_tests_fallback_dest > > > > known problem in new test code and not in mission code; fix is > > > already > > > > on master; not a regression > > > > > > > > > > > > - Original Message - > > > > > From: "Ganesh Murthy" > > > > > To: users@qpid.apache.org, d...@qpid.apache.org > > > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > > > > > Hello All, > > > > > Please cast your vote on this thread to release RC1 as the > > > > > official Qpid Dispatch Router version 1.8.0. > > > > > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > > > > > The following features, improvements, and bug fixes are introduced > in > > > > 1.8.0: > > > > > > > > > > Features - > > > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > > > > > Improvements - > > > > > DISPATCH-1308 - Console access to the force-close a connection > > > > feature > > > > > DISPATCH-1320 - Make it easier to use separate logos for > upstream > > > > > and downstream masthead > > > > > DISPATCH-1321 - Set rpath for qpid-proton (and other > > dependencies) > > > > > when they are found in nonstandard location > > > > > DISPATCH-1329 - Edge router system test needs skip test > > convenience > > > > > switches > > > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > > > client > > > > > popup > > > > > DISPATCH-1341 - Add list of delayed links to console's overview > > > page > > > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > > > DISPATCH-1356 - Remove the dotted line around routers that > > > > > indicates the router is fixed. > > > > > DISPATCH-1357 - Change the name of the 'Kill' feature to > 'Close' > > > > > > > > > > Bug fixes - > > > > > DISPATCH-974 - Getting connections via the router management > > > > > protocol causes AMQP framing errors > > > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > > > system_tests_ssl > > > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > > > DISPATCH-1318 - edge_router system test failing > > > > > DISPATCH-1322 - Edge router drops disposition when remote > > receiver > > > > closes > > > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > > > autoLink entity. Add address and externalAddress instead. > > > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape > > function > > > > > DISPATCH-1325 - Sender connections to edge router that connect > > > > > 'too soon' never get credit > > > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > > > even if there is a receiver for the messages > > > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > > > decrement on link detach > > > > > DISPATCH-1334 - Background map on topology page incorrect > height > > > > > DISPATCH-1335 - After adding client
Re: how to maintain reliability with ASYNC operation?
That would be the very point that I corrected myself on earlier, where I had somehow misread the second question numbered 2 originally. Per the correction, the same answer to the first question 2 applied there also, which was "This is the same as the default. Persistent messages will be sent synchronously, except inside a transaction. Non-persistent messages will be sent asynchronously." Governing those cases is the reason the forceSyncSend option exists. Robbie On Tue, 11 Jun 2019 at 17:23, akabhishek1 wrote: > > Hi Robbie, > > Based on your input, i did some testing and got different test result in > terms of TPS(transaction per second) for below conditions > > 1. jms.forceSyncSend=true + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, > DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1200. > > 2. NO Setting @Connection Level + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, > DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1800. > > > As both conditions tend to SYNCHRONOUS. I wondered to see different test > result with variance of 600TPS. My sourceCode is completely same for both > conditions except setting at connection level. > > Expectation - As both conditions tend to SYNCHRONOUS, so i am expecting > approx. same TPS for both conditions. > > Could you please provide some insights, why i am getting different Test > throughput as both are synchronous? Am i missing something? > > Client - qpid-jms-client-0.43.0 > Java8 > Broker - Azure ServiceBus(Premium) > > Regards, > Abhishek Kumar > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > - > 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 to maintain reliability with ASYNC operation?
Hi Robbie, Based on your input, i did some testing and got different test result in terms of TPS(transaction per second) for below conditions 1. jms.forceSyncSend=true + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1200. 2. NO Setting @Connection Level + send(jmsMsg, PERSISTENT, DEFAULT_PRIORITY, DEFAULT_TIME_TO_LIVE) -- > I got TPS around 1800. As both conditions tend to SYNCHRONOUS. I wondered to see different test result with variance of 600TPS. My sourceCode is completely same for both conditions except setting at connection level. Expectation - As both conditions tend to SYNCHRONOUS, so i am expecting approx. same TPS for both conditions. Could you please provide some insights, why i am getting different Test throughput as both are synchronous? Am i missing something? Client - qpid-jms-client-0.43.0 Java8 Broker - Azure ServiceBus(Premium) Regards, Abhishek Kumar -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - 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.8.0 (RC1)
executive summary: I change my vote to *+1* but with JIRAs. OK! I have something. I didn't remember it, but my notes show that I have seen this exact failure before, also after a clean install. ( I mean the authz failure. The other one, the http failure is already explained.) So this means that the problem has got to be with my machine setup --- there is some package that the authz test requires that I do not install after a clean OS upgrade. I do have a great plethora of SASL and SSL packages installed, so I don't know what it might be, and I am having trouble tracing into the Python code. If anyone has a clue, please let me know. But, since the problem is limited to the test not warning about a required package, I will do two things: 1. raise a JIRA, 2. and change my vote to *+1* On Tue, Jun 11, 2019 at 12:04 PM Ganesh Murthy wrote: > On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish > wrote: > > > Of course I will not change my vote based on a suggestion ( from me and > > Gordon ) that the failure I am seeing might be caused by a missing > > package. > > > > What I will do is start looking into this to see if that is indeed the > > case. > > And then we will make a change that detects and warns about that case. > > And then I will change my vote. > > > Agreed, fair enough. > > > > > > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > > > > > +1 > > > > > > * Checked checksums > > > * Build/test Fedora 29, python 3 > > > * Fails system_tests_http (known problem, not a regression) > > > * Build/test Fedora 28, python 2 > > > * Occasional test fail system_tests_fallback_dest > > > known problem in new test code and not in mission code; fix is > > already > > > on master; not a regression > > > > > > > > > - Original Message - > > > > From: "Ganesh Murthy" > > > > To: users@qpid.apache.org, d...@qpid.apache.org > > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > > > Hello All, > > > > Please cast your vote on this thread to release RC1 as the > > > > official Qpid Dispatch Router version 1.8.0. > > > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > > > The following features, improvements, and bug fixes are introduced in > > > 1.8.0: > > > > > > > > Features - > > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > > > Improvements - > > > > DISPATCH-1308 - Console access to the force-close a connection > > > feature > > > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > > > and downstream masthead > > > > DISPATCH-1321 - Set rpath for qpid-proton (and other > dependencies) > > > > when they are found in nonstandard location > > > > DISPATCH-1329 - Edge router system test needs skip test > convenience > > > > switches > > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > > client > > > > popup > > > > DISPATCH-1341 - Add list of delayed links to console's overview > > page > > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > > DISPATCH-1356 - Remove the dotted line around routers that > > > > indicates the router is fixed. > > > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > > > > > Bug fixes - > > > > DISPATCH-974 - Getting connections via the router management > > > > protocol causes AMQP framing errors > > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > > system_tests_ssl > > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > > DISPATCH-1318 - edge_router system test failing > > > > DISPATCH-1322 - Edge router drops disposition when remote > receiver > > > closes > > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > > autoLink entity. Add address and externalAddress instead. > > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape > function > > > > DISPATCH-1325 - Sender connections to edge router that connect > > > > 'too soon' never get credit > > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > > even if there is a receiver for the messages > > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > > decrement on link detach > > > > DISPATCH-1334 - Background map on topology page incorrect height > > > > DISPATCH-1335 - After adding client, topology page shows new icon > > > > in upper-left corner > > > > DISPATCH-1339 - Multiple consoles attached to a router are > showing > > > > as separate icons > > > > > > > > > > > > Thanks. > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr..
Re: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1)
On Tue, Jun 11, 2019 at 11:58 AM Michael Goulish wrote: > Of course I will not change my vote based on a suggestion ( from me and > Gordon ) that the failure I am seeing might be caused by a missing > package. > > What I will do is start looking into this to see if that is indeed the > case. > And then we will make a change that detects and warns about that case. > And then I will change my vote. > Agreed, fair enough. > > > > On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > > > +1 > > > > * Checked checksums > > * Build/test Fedora 29, python 3 > > * Fails system_tests_http (known problem, not a regression) > > * Build/test Fedora 28, python 2 > > * Occasional test fail system_tests_fallback_dest > > known problem in new test code and not in mission code; fix is > already > > on master; not a regression > > > > > > - Original Message - > > > From: "Ganesh Murthy" > > > To: users@qpid.apache.org, d...@qpid.apache.org > > > Sent: Friday, June 7, 2019 11:23:40 AM > > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > > > Hello All, > > > Please cast your vote on this thread to release RC1 as the > > > official Qpid Dispatch Router version 1.8.0. > > > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > > > The following features, improvements, and bug fixes are introduced in > > 1.8.0: > > > > > > Features - > > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > > > Improvements - > > > DISPATCH-1308 - Console access to the force-close a connection > > feature > > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > > and downstream masthead > > > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > > > when they are found in nonstandard location > > > DISPATCH-1329 - Edge router system test needs skip test convenience > > > switches > > > DISPATCH-1340 - Show settlement rate and delayed deliveries in > client > > > popup > > > DISPATCH-1341 - Add list of delayed links to console's overview > page > > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > > DISPATCH-1356 - Remove the dotted line around routers that > > > indicates the router is fixed. > > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > > > Bug fixes - > > > DISPATCH-974 - Getting connections via the router management > > > protocol causes AMQP framing errors > > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > > system_tests_ssl > > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > > DISPATCH-1318 - edge_router system test failing > > > DISPATCH-1322 - Edge router drops disposition when remote receiver > > closes > > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > > autoLink entity. Add address and externalAddress instead. > > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > > > DISPATCH-1325 - Sender connections to edge router that connect > > > 'too soon' never get credit > > > DISPATCH-1326 - Anonymous messages are released by edge router > > > even if there is a receiver for the messages > > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > > decrement on link detach > > > DISPATCH-1334 - Background map on topology page incorrect height > > > DISPATCH-1335 - After adding client, topology page shows new icon > > > in upper-left corner > > > DISPATCH-1339 - Multiple consoles attached to a router are showing > > > as separate icons > > > > > > > > > Thanks. > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > > For additional commands, e-mail: dev-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 Dispatch Router 1.8.0 (RC1)
On 11/06/2019 3:56 pm, Michael Goulish wrote: And this leaves the authz failure -- which could be due to some missing package, except that the build system should detect those & throw a warning so I have some way to fix. You can get more information about the test failures from the various logs under tests/system_test.dir/system_tests_authz_service_plugin/AuthServicePluginAuthzTest/ especially setUpClass/ What cyrus-sasl plugins do you have under /usr/lib64/sasl2/? Though given that the auth plugin tests worked but authz did not it seems unlikely to be that... probably something to do with the startup of the authservice.py script (see tests/system_test.dir/system_tests_authz_service_plugin/AuthServicePluginAuthzTest/setUpClass/env-2.out perhaps?) - 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.8.0 (RC1)
Of course I will not change my vote based on a suggestion ( from me and Gordon ) that the failure I am seeing might be caused by a missing package. What I will do is start looking into this to see if that is indeed the case. And then we will make a change that detects and warns about that case. And then I will change my vote. On Tue, Jun 11, 2019 at 11:28 AM Chuck Rolke wrote: > +1 > > * Checked checksums > * Build/test Fedora 29, python 3 > * Fails system_tests_http (known problem, not a regression) > * Build/test Fedora 28, python 2 > * Occasional test fail system_tests_fallback_dest > known problem in new test code and not in mission code; fix is already > on master; not a regression > > > - Original Message - > > From: "Ganesh Murthy" > > To: users@qpid.apache.org, d...@qpid.apache.org > > Sent: Friday, June 7, 2019 11:23:40 AM > > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > > > Hello All, > > Please cast your vote on this thread to release RC1 as the > > official Qpid Dispatch Router version 1.8.0. > > > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > > > The following features, improvements, and bug fixes are introduced in > 1.8.0: > > > > Features - > >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > > > Improvements - > > DISPATCH-1308 - Console access to the force-close a connection > feature > > DISPATCH-1320 - Make it easier to use separate logos for upstream > > and downstream masthead > > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > > when they are found in nonstandard location > > DISPATCH-1329 - Edge router system test needs skip test convenience > > switches > > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > > popup > > DISPATCH-1341 - Add list of delayed links to console's overview page > > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > > DISPATCH-1356 - Remove the dotted line around routers that > > indicates the router is fixed. > > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > > > Bug fixes - > > DISPATCH-974 - Getting connections via the router management > > protocol causes AMQP framing errors > > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > > system_tests_ssl > > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > > DISPATCH-1317 - HTTP system test is failing on python2.6 > > DISPATCH-1318 - edge_router system test failing > > DISPATCH-1322 - Edge router drops disposition when remote receiver > closes > > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > > autoLink entity. Add address and externalAddress instead. > > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > > DISPATCH-1325 - Sender connections to edge router that connect > > 'too soon' never get credit > > DISPATCH-1326 - Anonymous messages are released by edge router > > even if there is a receiver for the messages > > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > > decrement on link detach > > DISPATCH-1334 - Background map on topology page incorrect height > > DISPATCH-1335 - After adding client, topology page shows new icon > > in upper-left corner > > DISPATCH-1339 - Multiple consoles attached to a router are showing > > as separate icons > > > > > > Thanks. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > > For additional commands, e-mail: dev-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 Dispatch Router 1.8.0 (RC1)
+1 * Checked checksums * Build/test Fedora 29, python 3 * Fails system_tests_http (known problem, not a regression) * Build/test Fedora 28, python 2 * Occasional test fail system_tests_fallback_dest known problem in new test code and not in mission code; fix is already on master; not a regression - Original Message - > From: "Ganesh Murthy" > To: users@qpid.apache.org, d...@qpid.apache.org > Sent: Friday, June 7, 2019 11:23:40 AM > Subject: [VOTE] Release Qpid Dispatch Router 1.8.0 (RC1) > > Hello All, > Please cast your vote on this thread to release RC1 as the > official Qpid Dispatch Router version 1.8.0. > > RC1 of Qpid Dispatch Router version 1.8.0 can be found here: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ > > The following features, improvements, and bug fixes are introduced in 1.8.0: > > Features - >DISPATCH-1337 - Fallback Destination for Unreachable Addresses > > Improvements - > DISPATCH-1308 - Console access to the force-close a connection feature > DISPATCH-1320 - Make it easier to use separate logos for upstream > and downstream masthead > DISPATCH-1321 - Set rpath for qpid-proton (and other dependencies) > when they are found in nonstandard location > DISPATCH-1329 - Edge router system test needs skip test convenience > switches > DISPATCH-1340 - Show settlement rate and delayed deliveries in client > popup > DISPATCH-1341 - Add list of delayed links to console's overview page > DISPATCH-1348 - Avoid qdr_error_t allocation if not necessary > DISPATCH-1356 - Remove the dotted line around routers that > indicates the router is fixed. > DISPATCH-1357 - Change the name of the 'Kill' feature to 'Close' > > Bug fixes - > DISPATCH-974 - Getting connections via the router management > protocol causes AMQP framing errors > DISPATCH-1230 - System test failing with OpenSSL >= 1.1 - > system_tests_ssl > DISPATCH-1312 - Remove cmake option USE_MEMORY_POOL > DISPATCH-1317 - HTTP system test is failing on python2.6 > DISPATCH-1318 - edge_router system test failing > DISPATCH-1322 - Edge router drops disposition when remote receiver closes > DISPATCH-1323 - Deprecate addr and externalAddr attributes of > autoLink entity. Add address and externalAddress instead. > DISPATCH-1324 - [tools] Scraper uses deprecated cgi.escape function > DISPATCH-1325 - Sender connections to edge router that connect > 'too soon' never get credit > DISPATCH-1326 - Anonymous messages are released by edge router > even if there is a receiver for the messages > DISPATCH-1330 - Q2 stall due to incorrect msg buffer ref count > decrement on link detach > DISPATCH-1334 - Background map on topology page incorrect height > DISPATCH-1335 - After adding client, topology page shows new icon > in upper-left corner > DISPATCH-1339 - Multiple consoles attached to a router are showing > as separate icons > > > Thanks. > > - > To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-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 Dispatch Router 1.8.0 (RC1)
On Tue, Jun 11, 2019 at 11:01 AM Gordon Sim wrote: > On 11/06/2019 3:56 pm, Michael Goulish wrote: > > My version of libwebsockets is 3.1.0-2, which is the version with a known > > crash here (Gordon pointed out), but then we should detect that and skip > > the test, rather than show a failure. > > > > And this leaves the authz failure -- which could be due to some missing > > package, except that the build system should detect those & throw a > warning > > so I have some way to fix. > > Agreed that both those suggestions would be nice improvements. The > libwebsockets issue is not a blocker though. I suspect you are right > about the root cause of the authz failures but it would be nice to try > and track those down. If so they also would not be blockers for the > release. > Hi Mick, Based on Gordon's response, would you consider changing your vote to a +1 ? Thanks. > > - > 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.8.0 (RC1)
On 11/06/2019 3:56 pm, Michael Goulish wrote: My version of libwebsockets is 3.1.0-2, which is the version with a known crash here (Gordon pointed out), but then we should detect that and skip the test, rather than show a failure. And this leaves the authz failure -- which could be due to some missing package, except that the build system should detect those & throw a warning so I have some way to fix. Agreed that both those suggestions would be nice improvements. The libwebsockets issue is not a blocker though. I suspect you are right about the root cause of the authz failures but it would be nice to try and track those down. If so they also would not be blockers for 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.8.0 (RC1)
My version of libwebsockets is 3.1.0-2, which is the version with a known
crash here (Gordon pointed out), but then we should detect that and skip
the test, rather than show a failure.
And this leaves the authz failure -- which could be due to some missing
package, except that the build system should detect those & throw a warning
so I have some way to fix.
On Tue, Jun 11, 2019 at 8:12 AM Michael Goulish wrote:
>
> * -1*
>
>
> I built against latest released proton ( 0.28.0 ) and I am running on a
> new clean-install of Fedora 30.
>
> I have two test failures.
>
> I imagine that the 100% authz failure is because I do not have something
> installed, but there were no warnings from cmake.
>
>
> Here's the output:
>
>
>
> 97% tests passed, 2 tests failed out of 58
>
> Total Test time (real) = 841.96 sec
>
> The following tests FAILED:
> 39 - system_tests_authz_service_plugin (Failed)
> 52 - system_tests_http (Failed)
>
>
>
>
>
>
> test 39
> Start 39: system_tests_authz_service_plugin
>
> 39: Test command: /usr/bin/python
> "/home/mick/latest/qpid-dispatch-1.8.0/build/tests/run.py" "unit2" "-v"
> "system_tests_authz_service_plugin"
> 39: Test timeout computed to be: 1500
> 39: test_authorized
> (system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
> ... FAIL
> 39: test_dynamic_source_anonymous_sender
> (system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
> ... FAIL
> 39: test_unauthorized
> (system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
> ... FAIL
> 39: test_unauthorized_anonymous_sender_target
> (system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
> ... FAIL
> 39: test_wildcard
> (system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
> ... FAIL
> 39: test_authorized
> (system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
> 39: test_dynamic_source_anonymous_sender
> (system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
> 39: test_unauthorized
> (system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
> 39: test_unauthorized_anonymous_sender_target
> (system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
> 39: test_wildcard
> (system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
> 39: . and so on .
>
>
>
>
>
> 52: test_https_get (system_tests_http.RouterTestHttp) ... ERROR
> 52: ERROR
> 52: test_listen_error (system_tests_http.RouterTestHttp)
> 52: Make sure a router exits if an initial HTTP listener fails, doesn't
> hang ... ok
> 52:
> 52: ==
> 52: ERROR: test_https_get (system_tests_http.RouterTestHttp)
> 52: --
> 52: Traceback (most recent call last):
> 52: File
> "/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
> 252, in test_https_get
> 52: self.assert_get("http://localhost:%s"; % r.ports[0])
> 52: File
> "/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
> 83, in assert_get
> 52: self.assertEqual(u'HTTP test\n',
> self.get("%s/system_tests_http.txt" % url))
> 52: File
> "/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
> 54, in get
> 52: http_data = urlopen(url, cafile=cls.ssl_file('ca-certificate.pem'))
> 52: File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen
> 52: return opener.open(url, data, timeout)
> 52: File "/usr/lib64/python2.7/urllib2.py", line 429, in open
> 52: response = self._open(req, data)
> 52: File "/usr/lib64/python2.7/urllib2.py", line 447, in _open
> 52: '_open', req)
> 52: File "/usr/lib64/python2.7/urllib2.py", line 407, in _call_chain
> 52: result = func(*args)
> 52: File "/usr/lib64/python2.7/urllib2.py", line 1230, in http_open
> 52: return self.do_open(httplib.HTTPConnection, req)
> 52: File "/usr/lib64/python2.7/urllib2.py", line 1203, in do_open
> 52: r = h.getresponse(buffering=True)
> 52: File "/usr/lib64/python2.7/httplib.py", line 1121, in getresponse
> 52: response.begin()
> 52: File "/usr/lib64/python2.7/httplib.py", line 438, in begin
> 52: version, status, reason = self._read_status()
> 52: File "/usr/lib64/python2.7/httplib.py", line 394, in _read_status
> 52: line = self.fp.readline(_MAXLINE + 1)
> 52: File "/usr/lib64/python2.7/socket.py", line 480, in readline
> 52: data = self._sock.recv(self._rbufsize)
> 52: socket.error: [Errno 104] Connection reset by peer
> 52:
> 52: ==
>
>
> 52: RuntimeError: Errors during teardown:
> 52:
> 52: Process 10637 error: exit code -11, expected -1
> 52: qdrouterd -c https-test-router.conf -I
> /home/mick/latest/qpid-dispatch-1.8.0/python
> 52:
> /home/mick/latest/qpid-dispatch-1.8.0/build/tests/system_test.dir/system_tests_http/RouterTestHttp/test_https_g
Re: how to maintain reliability with ASYNC operation?
Hi Robbie, Thank you so much for your all inputs. I really appreciate your fast response. We are doing testing based on your inputs. We will come back again, if we have any other questions. Regards, Abhishek Kumar -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: sender.close() hangs
I ran the server example against rabbitmq (with a modified client to get around the lack of support for dynamic addresses). It looks like the issue is that rabbit responds to a detach with close=true by sending a detach without setting the close. The qpid::messaging client uses proton and currently relies on the endpoint state of the link to determine that it is closed. When receiving a detach with close not set (which is equivalent to close=false), there is no way that I can see to determine that this has happened by querying the proton object. (A PN_LINK_REMOTE_DETACH event would be generated, but events aren't used in qpid::messaging at present as they did not exist when it was first written). I think the rabbitmq-server is not doing the expected thing here. From 2.6.6 in AMQP 1.0 spec: A peer closes a link by sending the detach frame with the handle for the specified link, and the closed flag set to true. The partner will destroy the corresponding link endpoint, and reply with its own detach frame with the closed flag set to true.[1] However I do also think that proton should have a way of determining that a given link is not attached on the remote side, which it currently does not (apart from an event). There is already a JIRA for this from some time back: https://issues.apache.org/jira/browse/PROTON-773 If that were fixed then the qpid::messaging client could be fixed to not hang in this case even though the server is not sending the detach with close=true as would be expected. I'd recommend raising an issue against the 1.0 plugin for rabbitmq. My guess is it should be a simple fix there. I will see if I can propose (or get anyone else to propose) a change to proton to allow the detached (but not closed) state to be determined by some request. [1] It also says: Note that one peer MAY send a closing detach while its partner is sending a non-closing detach. In this case, the partner MUST signal that it has closed the link by reattaching and then sending a closing detach. Though that isn't really the case here as it is clear the server is responding to the detach from the client rather than deliberatiely initiating a non-closing detach itself. - 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.8.0 (RC1)
* -1*
I built against latest released proton ( 0.28.0 ) and I am running on a
new clean-install of Fedora 30.
I have two test failures.
I imagine that the 100% authz failure is because I do not have something
installed, but there were no warnings from cmake.
Here's the output:
97% tests passed, 2 tests failed out of 58
Total Test time (real) = 841.96 sec
The following tests FAILED:
39 - system_tests_authz_service_plugin (Failed)
52 - system_tests_http (Failed)
test 39
Start 39: system_tests_authz_service_plugin
39: Test command: /usr/bin/python
"/home/mick/latest/qpid-dispatch-1.8.0/build/tests/run.py" "unit2" "-v"
"system_tests_authz_service_plugin"
39: Test timeout computed to be: 1500
39: test_authorized
(system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
... FAIL
39: test_dynamic_source_anonymous_sender
(system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
... FAIL
39: test_unauthorized
(system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
... FAIL
39: test_unauthorized_anonymous_sender_target
(system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
... FAIL
39: test_wildcard
(system_tests_authz_service_plugin.AuthServicePluginAuthzDeprecatedTest)
... FAIL
39: test_authorized
(system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
39: test_dynamic_source_anonymous_sender
(system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
39: test_unauthorized
(system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
39: test_unauthorized_anonymous_sender_target
(system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
39: test_wildcard
(system_tests_authz_service_plugin.AuthServicePluginAuthzTest) ... FAIL
39: . and so on .
52: test_https_get (system_tests_http.RouterTestHttp) ... ERROR
52: ERROR
52: test_listen_error (system_tests_http.RouterTestHttp)
52: Make sure a router exits if an initial HTTP listener fails, doesn't
hang ... ok
52:
52: ==
52: ERROR: test_https_get (system_tests_http.RouterTestHttp)
52: --
52: Traceback (most recent call last):
52: File
"/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
252, in test_https_get
52: self.assert_get("http://localhost:%s"; % r.ports[0])
52: File
"/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
83, in assert_get
52: self.assertEqual(u'HTTP test\n',
self.get("%s/system_tests_http.txt" % url))
52: File
"/home/mick/latest/qpid-dispatch-1.8.0/tests/system_tests_http.py", line
54, in get
52: http_data = urlopen(url, cafile=cls.ssl_file('ca-certificate.pem'))
52: File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen
52: return opener.open(url, data, timeout)
52: File "/usr/lib64/python2.7/urllib2.py", line 429, in open
52: response = self._open(req, data)
52: File "/usr/lib64/python2.7/urllib2.py", line 447, in _open
52: '_open', req)
52: File "/usr/lib64/python2.7/urllib2.py", line 407, in _call_chain
52: result = func(*args)
52: File "/usr/lib64/python2.7/urllib2.py", line 1230, in http_open
52: return self.do_open(httplib.HTTPConnection, req)
52: File "/usr/lib64/python2.7/urllib2.py", line 1203, in do_open
52: r = h.getresponse(buffering=True)
52: File "/usr/lib64/python2.7/httplib.py", line 1121, in getresponse
52: response.begin()
52: File "/usr/lib64/python2.7/httplib.py", line 438, in begin
52: version, status, reason = self._read_status()
52: File "/usr/lib64/python2.7/httplib.py", line 394, in _read_status
52: line = self.fp.readline(_MAXLINE + 1)
52: File "/usr/lib64/python2.7/socket.py", line 480, in readline
52: data = self._sock.recv(self._rbufsize)
52: socket.error: [Errno 104] Connection reset by peer
52:
52: ==
52: RuntimeError: Errors during teardown:
52:
52: Process 10637 error: exit code -11, expected -1
52: qdrouterd -c https-test-router.conf -I
/home/mick/latest/qpid-dispatch-1.8.0/python
52:
/home/mick/latest/qpid-dispatch-1.8.0/build/tests/system_test.dir/system_tests_http/RouterTestHttp/test_https_get/https-test-router-5.cmd
Re: Negative Bytes Credit
Hi Sidarth, It looks like a defect to me. Can you provide any code reproducing the issue? Any sample app or test case would be of great help? Any information about your consumption use case would be helpful as well. Kind Regards, Alex On Mon, 10 Jun 2019 at 22:05, sidarthsc wrote: > Hi, > > We recently upgraded to version 7.0.7 of the Java broker. We are using a > customized version of version 0.16 of the client. Yes, it's ancient, and we > are considering upgrading, but that is difficult for us for multiple > reasons. We noticed the following error in our logs after upgrading from > 7.0.6 to 7.0.7: > > ERROR [IO-/10.252.224.25:43564] - Bytes credit used value was negative: > -497 > > Could you help us figure out the meaning of this error? > > Thanks > > > > > -- > Sent from: > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > - > 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.8.0 (RC1)
On 07/06/2019 4:23 pm, Ganesh Murthy wrote: Hello All, Please cast your vote on this thread to release RC1 as the official Qpid Dispatch Router version 1.8.0. RC1 of Qpid Dispatch Router version 1.8.0 can be found here: https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.8.0-rc1/ +1, verified signature and checksum, built from source ran all tests (hit failures on fallback and edge router tests on first run but was then unable to reproduce those) and installed, ran relevant python proton and qpid:messaging c++ examples against it, ran it through CI for enmasse.io - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: how to maintain reliability with ASYNC operation?
On Mon, 10 Jun 2019 at 16:30, Robbie Gemmell wrote: > > We discussed much of this last year already, the situation hasn't > changed any since then. > > Initial summary points here, then more comments inline below. > > - Providing a CompletionListener is an explicit request that the send > be asynchronous, thats the only reason for providing it. > - The '"jms.forceSyncSend' etc URI options are for controlling send > calls not using a CompletionListener, and were present from before the > client ever supported JMS 2.0 (when CompletionListener support was > added and reliable async sends became possible) to govern certain > cases it can send asynchronously (see later). > - If you use a CompletionListener, the send response will come via the > CompletionListener. This is mandated by JMS, and logical since that is > precisely what it exists to facilitate (see also next point). > - If you want a reliable send result to come via the send method > return, then you are implicitly saying that you do not want the send > to be asynchronous at all, but rather synchronous, and thus also that > you do not want to use a CompletionListener. > - Even when you do use a CompletionListener, the send method can still > throw an exception, since there is work required to send the message > which can fail before the point that happens and responsibility passes > to the CompletionListener callback. If send doesnt throw, the result > is then notified via the CompletionListener. > > As with last year, you seem to want async sends to behave exactly the > same as sync sends do, but they dont as they are different. You need > to decide which approach you actually need/want, synchronous or > reliable async, and use or handle it accordingly. I hope it is clear > that they will perform essentially the same if all you do is simply > send one message and await its response before doing anything else. > > Robbie > > On Mon, 10 Jun 2019 at 15:09, akabhishek1 > wrote: > > > > Hi Robbie, > > > > Thank you so much for quick response. However, we have couple of open > > questions related with Qpid. If you provide us input that will be too great. > > We are using "qpid-jms-client-0.40.0" and sending message to Azure Service > > Bus. > > > > 1. Condition - if "jms.forceSyncSend=true" + send(Message message, > > CompletionListener completionListener); > >Q- Is message will process in SYNC or ASYNC? As i am using > > "jms.forceSyncSend=true", so could we get response in CompletionListener or > > in same thread? > > > >I have done testing locally with "qpid-jms-client-0.40.0" and i am > > getting response in CompletionListener-onCompletion/onException. > > > >As per Qpid documentation, "jms.forceSyncSend" should override all > > asynchronous send conditions, > >But it is not doing at this moment because i am getting response back > > with CompletionListener . Is this BUG?? > > > > It is not a bug. As explained above and last year, that option does > not control CompletionListener-using sends. Providing a > CompletionListener means it is asynchronous and you get the eventual > result back via it. That is explicit in its operation and is the only > reason for providing it. > > > > > 2. Condition - if "jms.forceAsyncSend=false" + Send with NO > > CompletionListener, > >Q -Could you please confirm, in this scenario QPID will send message in > > SYNC or ASYNC? > > > > This is the same as the default. Persistent messages will be sent > synchronously, except inside a transaction. Non-persistent messages > will be sent asynchronously. > > > > 2. Condition - if "jms.forceSyncSend=false" + Send with NO > > CompletionListener, > >Q -Could you please confirm, in this scenario QPID will send message in > > SYNC or ASYNC? > > > > All sends without a CompletionListener will be synchronous. I must have misread this bit (maybe mangled it together with another question), thinking the option was being set true. As it is not, the comment should have been the same as the previous one above. > > > > > 3. Can we make assumption that, If we are send message with > > CompletionListener, then Qpid always send message to broker in ASYNC way or > > it can be SYNC also with "jms.forceSyncSend=true"? > > > > There is no assumption here, it is asynchronous. CompletionListener > only exists to facilitate reliable asynchronous send, providing one is > an explicit request for an async send, and as before that option is > not there to govern that in any way (and still wouldnt do what you > seem to want if it were; results come via CompletionListener) > > > 4. SYNCHRONOUS - What is the internal behaviour of Qpid in SYNC messaging? > > Is qpid waiting for successful response back from broker or it is working > > like NON blocking IO concept? > > > > Sync sends return at the application level upon receipt of > acknowledgement from the recipient peer (e.g a broker). > > (The underlying transport is not blocking.) > > > 5. Is there anyway to identify to nature of
