[GitHub] qpid-proton pull request #151: Install tests
GitHub user alanconway opened a pull request: https://github.com/apache/qpid-proton/pull/151 Install tests Tests can be executed from install for c, cpp, ruby. Installed under INSTALL-PREFIX/share/proton-VERSION/examples. Each examples/ subdir has a stand-alone `testme` script that runs with no arguments. The script assumes that if examples for a language are installed, then proton support and all pre-requisites are also installed either: - under the same INSTALL-prefix - in standard places (/usr etc.) - locatable using standard environment variables (PATH etc.) Depending on the type of example the testme script may allow args, e.g. -v for verbose output on python-based testme scripts. To build/run all tests: cd TEMP-BUILD-DIR cmake INSTALL-PREFIX/share/proton-VERSION/examples make ctest -VV To run test that don't need separate build, e.g. ruby: cd INSTALL-PREFIX/share/proton-VERSION/examples ruby; testme TODO: python: examples need updating to be usable for self test: - servers to print actual port not command-line port - test driver to start servers on port 0, pass real port from server stdout to client go: currently an awkward mix of Go native build tools and cmake. - make go examples into standard Go executable package. - testme script will be simply `GOPATH=... go test qpid.apache.org/proton_examples` - make examples available via `go get` and on godoc.org You can merge this pull request into a Git repository by running: $ git pull https://github.com/alanconway/qpid-proton install-tests Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/151.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #151 commit 20c016c8d12aa700f0c1874c7f9259f5ad0e6169 Author: Alan Conway Date: 2018-07-06T19:06:34Z NO-JIRA: [c,cpp] Remove dead code in examples/CMakeLists.txt commit 1244c375a2dfc1042109c84fed38eae3b59c7391 Author: Alan Conway Date: 2018-07-09T22:50:27Z PROTON-1798: [c, cpp, ruby] Installable tests for proton Tests can be executed from install for c, cpp, ruby. Installed under INSTALL-PREFIX/share/proton-VERSION/examples. Each examples/ subdir has a stand-alone `testme` script that runs with no arguments. The script assumes that if examples for a language are installed, then proton support and all pre-requisites are also installed either: - under the same INSTALL-prefix - in standard places (/usr etc.) - locatable using standard environment variables (PATH etc.) Depending on the type of example the testme script may allow args, e.g. -v for verbose output on python-based testme scripts. To build/run all tests: cd TEMP-BUILD-DIR cmake INSTALL-PREFIX/share/proton-VERSION/examples make ctest -VV To run test that don't need separate build, e.g. ruby: cd INSTALL-PREFIX/share/proton-VERSION/examples ruby; testme TODO: python: examples need updating to be usable for self test: - servers to print actual port not command-line port - test driver to start servers on port 0, pass real port from server stdout to client go: currently an awkward mix of Go native build tools and cmake. - make go examples into standard Go executable package. - testme script will be simply `GOPATH=... go test qpid.apache.org/proton_examples` - make examples available via `go get` and on godoc.org --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8212) [JMS AMQP 0-x][AMQP 0-8..0-91] Consumer close can block for 60 seconds and endup in time-out exception
[
https://issues.apache.org/jira/browse/QPID-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537746#comment-16537746
]
ASF subversion and git services commented on QPID-8212:
---
Commit 9fe911a9576ac69b64b1d4322ceae8cd1f3cfbec in qpid-jms-amqp-0-x's branch
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=9fe911a ]
QPID-8212: Improve handling of received method frames
> [JMS AMQP 0-x][AMQP 0-8..0-91] Consumer close can block for 60 seconds and
> endup in time-out exception
> --
>
> Key: QPID-8212
> URL: https://issues.apache.org/jira/browse/QPID-8212
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-client-0-x-6.3.1
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Blocker
> Fix For: qpid-java-client-0-x-6.3.2
>
>
> When method {{MessageConsumer#close()}} is invoked in one thread and method
> {{Connection#close()}} is invoked in another thread, the incoming
> {{BasicCancelOk}} frame can be ignored due to {{true}} being returned from
> {{Session#isClosed()}} because of {{Connection#_closed}} flag being set to
> true on connection close. As result, the call to {{MessageConsumer#close()}}
> can block for 60 seconds and end up in exception due to not being able to
> receive {{BasicCancelOk}}. Invocation of {{Connection#close()}} also gets
> blocked as message delivery lock being hold on consumer close.
> The defect was introduced as part of changes made against QPID-8185 in commit
>
> [f89f6c2f45d11fc63551d0d61c17eceedd6bd247|https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=f89f6c2]
> Method {{AMQProtocolSession#isClosedForInput}} checks whether session is
> closed for input by calling {{AMQSession#isClosed()}}. The latter returns
> true when either {{AMQSession#_closed}} or {{AMQConnection#_closed}} holds
> {{true}}. Only {{AMQSession#_closed}} should be checked in
> {{AMQProtocolSession#isClosedForInput}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #340: Dispatch-1055: Router fails to propagage cr...
GitHub user ChugR opened a pull request: https://github.com/apache/qpid-dispatch/pull/340 Dispatch-1055: Router fails to propagage credit on link router after drain cycle In this PR the "fix" is all in transfer.c. * The router was not accounting for transfers that never arrive when drain consumes the credit without sending messages. The fix is to reset the internal credit counts when a drain cycle ends. * The router calculates if drain changed more correctly. The commit also adds a test that works when not in link route and fails in a link route. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ChugR/qpid-dispatch DISPATCH-1055-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/340.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #340 commit baa4d92a9cf6e3ce92199df60a009119b834fd96 Author: Chuck Rolke Date: 2018-06-29T21:43:24Z DISPATCH-1055: Add a test that demonstrates the credit error The test is run first without a link route to observe that it works. Then it is run with the link route and hangs. commit a9b37f030785d1bdd4d9900b5f0be41ded1b2aa9 Author: Chuck Rolke Date: 2018-07-09T20:23:08Z DISPATCH-1055: Fix drain propagated over link route Reset incremental credit given to core at end of drain cycle. Fix logic computing drain_changed flag. commit 52df18eff7f6429ab6fd99ec777136153423afe1 Author: Chuck Rolke Date: 2018-07-09T21:05:51Z fix drain_changed logic --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1888) Allow configuration of connection details via a simple config file
[ https://issues.apache.org/jira/browse/PROTON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537569#comment-16537569 ] ASF GitHub Bot commented on PROTON-1888: Github user codecov-io commented on the issue: https://github.com/apache/qpid-proton/pull/150 # [Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=h1) Report > Merging [#150](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=desc) into [master](https://codecov.io/gh/apache/qpid-proton/commit/252451f0ad06e6f29c6eb424ba31ead5e4b53545?src=pr=desc) will **increase** coverage by `0.09%`. > The diff coverage is `97.26%`. [](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=tree) ```diff @@Coverage Diff@@ ## master#150 +/- ## = + Coverage 86.51% 86.6% +0.09% = Files 247 248 +1 Lines 30443 30589 +146 = + Hits26337 26493 +156 + Misses 41064096 -10 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=tree) | Coverage Δ | | |---|---|---| | [python/tests/proton\_tests/\_\_init\_\_.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Rlc3RzL3Byb3Rvbl90ZXN0cy9fX2luaXRfXy5weQ==) | `100% <100%> (ø)` | :arrow_up: | | [python/tests/proton\_tests/connect.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Rlc3RzL3Byb3Rvbl90ZXN0cy9jb25uZWN0LnB5) | `100% <100%> (ø)` | | | [python/proton/reactor.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Byb3Rvbi9yZWFjdG9yLnB5) | `73.54% <91.66%> (+2.67%)` | :arrow_up: | | [c/src/reactor/acceptor.c](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-Yy9zcmMvcmVhY3Rvci9hY2NlcHRvci5j) | `96.61% <0%> (+11.86%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=footer). Last update [252451f...b903c72](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). > Allow configuration of connection details via a simple config file > -- > > Key: PROTON-1888 > URL: https://issues.apache.org/jira/browse/PROTON-1888 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Gordon Sim >Priority: Major > > It can be convenient to keep details of the connection to be established out > of application code, making it easier to switch between environments. Support > for a simple config file that can be used to point the application at the > right AMQP service would be useful. Ideally this would be common across a > range of clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton issue #150: PROTON-1888: allow configuration of connection detai...
Github user codecov-io commented on the issue: https://github.com/apache/qpid-proton/pull/150 # [Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=h1) Report > Merging [#150](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=desc) into [master](https://codecov.io/gh/apache/qpid-proton/commit/252451f0ad06e6f29c6eb424ba31ead5e4b53545?src=pr=desc) will **increase** coverage by `0.09%`. > The diff coverage is `97.26%`. [](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=tree) ```diff @@Coverage Diff@@ ## master#150 +/- ## = + Coverage 86.51% 86.6% +0.09% = Files 247 248 +1 Lines 30443 30589 +146 = + Hits26337 26493 +156 + Misses 41064096 -10 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=tree) | Coverage Π| | |---|---|---| | [python/tests/proton\_tests/\_\_init\_\_.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Rlc3RzL3Byb3Rvbl90ZXN0cy9fX2luaXRfXy5weQ==) | `100% <100%> (ø)` | :arrow_up: | | [python/tests/proton\_tests/connect.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Rlc3RzL3Byb3Rvbl90ZXN0cy9jb25uZWN0LnB5) | `100% <100%> (ø)` | | | [python/proton/reactor.py](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-cHl0aG9uL3Byb3Rvbi9yZWFjdG9yLnB5) | `73.54% <91.66%> (+2.67%)` | :arrow_up: | | [c/src/reactor/acceptor.c](https://codecov.io/gh/apache/qpid-proton/pull/150/diff?src=pr=tree#diff-Yy9zcmMvcmVhY3Rvci9hY2NlcHRvci5j) | `96.61% <0%> (+11.86%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Π= absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=footer). Last update [252451f...b903c72](https://codecov.io/gh/apache/qpid-proton/pull/150?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1064) Doc link route reconnect behavior
[ https://issues.apache.org/jira/browse/DISPATCH-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537547#comment-16537547 ] ASF GitHub Bot commented on DISPATCH-1064: -- GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/339 DISPATCH-1064 - Doc link route reconnect behavior In the Dispatch Router user guide, I added some information about how the router handles broker connection failures for both link routing and message routing (using autolinks) scenarios. @ted-ross can you please review for technical accuracy? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1064-doc-link-route-reconnect Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/339.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #339 commit 4a8e3535e0029567471128e7b5807fada521e034 Author: Ben Hardesty Date: 2018-07-09T20:44:49Z Doc link route and autolink connection failure behavior > Doc link route reconnect behavior > - > > Key: DISPATCH-1064 > URL: https://issues.apache.org/jira/browse/DISPATCH-1064 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > When the router is configured with a linkRoute and client connects using > failover, the link will not be reestablished should the router's connection > to the broker fail. If auto-reconnect is required, the router should be > configured with autoLink. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #339: DISPATCH-1064 - Doc link route reconnect be...
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/339 DISPATCH-1064 - Doc link route reconnect behavior In the Dispatch Router user guide, I added some information about how the router handles broker connection failures for both link routing and message routing (using autolinks) scenarios. @ted-ross can you please review for technical accuracy? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1064-doc-link-route-reconnect Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/339.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #339 commit 4a8e3535e0029567471128e7b5807fada521e034 Author: Ben Hardesty Date: 2018-07-09T20:44:49Z Doc link route and autolink connection failure behavior --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1062) Link address can be reported incorrectly as mobile+phase-0
[ https://issues.apache.org/jira/browse/DISPATCH-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1062. - Resolution: Fixed Fix Version/s: (was: Backlog) 1.3.0 > Link address can be reported incorrectly as mobile+phase-0 > -- > > Key: DISPATCH-1062 > URL: https://issues.apache.org/jira/browse/DISPATCH-1062 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.2.0 >Reporter: Ted Ross >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.3.0 > > > Local/temporary addresses and mobile addresses with phase > 0 will be > reported in "qdstat -l" as mobile with phase == 0. > To reproduce: > * Create an address prefix with "waypoint: true" > * Attach a receiver to the router with an address that matches the above > * View qdstat -a and observe that the address (phase 1) has a local consumer. > * View qdstat -l and observe that the outgoing link has the address (phase 0) > The phase in the last step should be 1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1062) Link address can be reported incorrectly as mobile+phase-0
[ https://issues.apache.org/jira/browse/DISPATCH-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537532#comment-16537532 ] ASF subversion and git services commented on DISPATCH-1062: --- Commit d9c747d4993fcf5deaca894e1d0a2c56b16b58cc in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=d9c747d ] DISPATCH-1062 - Added unit test to test if phase shows up as zero for autoLinked waypointed addresses > Link address can be reported incorrectly as mobile+phase-0 > -- > > Key: DISPATCH-1062 > URL: https://issues.apache.org/jira/browse/DISPATCH-1062 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.2.0 >Reporter: Ted Ross >Assignee: Ganesh Murthy >Priority: Major > Fix For: Backlog > > > Local/temporary addresses and mobile addresses with phase > 0 will be > reported in "qdstat -l" as mobile with phase == 0. > To reproduce: > * Create an address prefix with "waypoint: true" > * Attach a receiver to the router with an address that matches the above > * View qdstat -a and observe that the address (phase 1) has a local consumer. > * View qdstat -l and observe that the outgoing link has the address (phase 0) > The phase in the last step should be 1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1066) Document capability to restrict TLS and SSL protocol versions used in connections
[ https://issues.apache.org/jira/browse/DISPATCH-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537400#comment-16537400 ] ASF GitHub Bot commented on DISPATCH-1066: -- GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/338 DISPATCH-1066 - Document capability to configure TLS protocol version In the Dispatch Router user guide, I added some information about the "protocols" attribute for users who want to restrict the permitted versions of TLS to use with the router. @ganeshmurthy, can you please review for technical accuracy? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1066-doc-tls-protocol-restriction Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/338.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #338 commit 9c567e98607850b3c7fcffe019c355c3b72c20d2 Author: Ben Hardesty Date: 2018-07-06T18:43:29Z Doc new protocols attribute in sslProfile config procedure commit 05410582de40de3cb5278edb4efbd2e160d24221 Author: Ben Hardesty Date: 2018-07-06T19:10:46Z Update qdmanage command for sslProfile in management chapter commit bf595e8fb78008780f7dc2e4e863a76d64c7a9c6 Author: Ben Hardesty Date: 2018-07-06T20:23:27Z Add note to protocols attr description > Document capability to restrict TLS and SSL protocol versions used in > connections > - > > Key: DISPATCH-1066 > URL: https://issues.apache.org/jira/browse/DISPATCH-1066 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #338: DISPATCH-1066 - Document capability to conf...
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/338 DISPATCH-1066 - Document capability to configure TLS protocol version In the Dispatch Router user guide, I added some information about the "protocols" attribute for users who want to restrict the permitted versions of TLS to use with the router. @ganeshmurthy, can you please review for technical accuracy? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1066-doc-tls-protocol-restriction Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/338.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #338 commit 9c567e98607850b3c7fcffe019c355c3b72c20d2 Author: Ben Hardesty Date: 2018-07-06T18:43:29Z Doc new protocols attribute in sslProfile config procedure commit 05410582de40de3cb5278edb4efbd2e160d24221 Author: Ben Hardesty Date: 2018-07-06T19:10:46Z Update qdmanage command for sslProfile in management chapter commit bf595e8fb78008780f7dc2e4e863a76d64c7a9c6 Author: Ben Hardesty Date: 2018-07-06T20:23:27Z Add note to protocols attr description --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #337: DISPATCH-1065 - Update qdstat output for en...
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/337 DISPATCH-1065 - Update qdstat output for enhanced stats In the Dispatch Router user guide, I updated the command output for qdstat -g and qdstat -l. @ganeshmurthy, can you please verify? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1065-doc-router-stats Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/337.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #337 commit e805e8ad876cd587db8f87b6d5def8259ee5da25 Author: Ben Hardesty Date: 2018-07-05T20:43:02Z Update qdstat output for enhanced stats --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1065) Doc new router statistics
[ https://issues.apache.org/jira/browse/DISPATCH-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537389#comment-16537389 ] ASF GitHub Bot commented on DISPATCH-1065: -- GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/337 DISPATCH-1065 - Update qdstat output for enhanced stats In the Dispatch Router user guide, I updated the command output for qdstat -g and qdstat -l. @ganeshmurthy, can you please verify? You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1065-doc-router-stats Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/337.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #337 commit e805e8ad876cd587db8f87b6d5def8259ee5da25 Author: Ben Hardesty Date: 2018-07-05T20:43:02Z Update qdstat output for enhanced stats > Doc new router statistics > - > > Key: DISPATCH-1065 > URL: https://issues.apache.org/jira/browse/DISPATCH-1065 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > Additional statistics are available from the router via the management > protocol. New statistics include: > * Number of pre-settled deliveries dropped on a link > * Global scope counters for link and address statistics > * Per-ingress counts for settled deliveries on egress links > Managment tool doc (qdstat/qdmanage) should be updated to reflect these new > statistics. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (DISPATCH-817) Honor TTL on unroutable messages
[ https://issues.apache.org/jira/browse/DISPATCH-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed DISPATCH-817. - Resolution: Won't Fix Fix Version/s: (was: Backlog) This issue will not be fixed. Rather than allow undeliverable messages to languish in buffers, the code has been modified to release such deliveries immediately. This is more consistent with Qpid Dispatch's philosophy of being stateless. > Honor TTL on unroutable messages > > > Key: DISPATCH-817 > URL: https://issues.apache.org/jira/browse/DISPATCH-817 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 0.8.0 >Reporter: Ganesh Murthy >Priority: Major > > Consider the following scenario - > - A receiver connects to the router attaching on an address. > - A sender connects to the router attaching to the same address, the router > gives credit so that the sender can start sending messages. > - The sender starts sending messages and the receiver suddenly drops off. > - If the message has not been routed (i.e. it's in the link buffer of the > sender's link), it will remain in this buffer until there is a consumer > available to receive it or until the sender disconnects. > - If the sender stays connected and the receiver never shows up again, these > unroutable messages stay in the sender link's link buffer forever. In this > case the router must check for the TTL on these deliveries and when it > expires, the delivery should be settled with RELEASED -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-127) update to use the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-127. - Resolution: Fixed Changed parent apache pom to v19 for both master and 0.2.0 branch. > update to use the current v19 apache parent pom > --- > > Key: QPIDIT-127 > URL: https://issues.apache.org/jira/browse/QPIDIT-127 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Minor > Fix For: 0.3.0 > > > update to use the current v19 apache parent pom to better align with other > components going forward (e.g see also QPIDJMS-397) and aid in consistent use > of plugin versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-127) update to use the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537260#comment-16537260 ] ASF subversion and git services commented on QPIDIT-127: Commit 28dffad8596b26b552d6b50dd99d6be8b2b9397b in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=28dffad ] QPIDIT-127: Updated parent apache pom to v19 > update to use the current v19 apache parent pom > --- > > Key: QPIDIT-127 > URL: https://issues.apache.org/jira/browse/QPIDIT-127 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Minor > Fix For: 0.3.0 > > > update to use the current v19 apache parent pom to better align with other > components going forward (e.g see also QPIDJMS-397) and aid in consistent use > of plugin versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-127) update to use the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537255#comment-16537255 ] ASF subversion and git services commented on QPIDIT-127: Commit ca71dfa9d162e4824a1c42ce4ab88861a34d9945 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=ca71dfa ] QPIDIT-127: Updated parent apache pom to v19 > update to use the current v19 apache parent pom > --- > > Key: QPIDIT-127 > URL: https://issues.apache.org/jira/browse/QPIDIT-127 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Minor > Fix For: 0.3.0 > > > update to use the current v19 apache parent pom to better align with other > components going forward (e.g see also QPIDJMS-397) and aid in consistent use > of plugin versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-131) module versions on master dont match and are incorrect
[
https://issues.apache.org/jira/browse/QPIDIT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-131.
-
Resolution: Fixed
The pom version on master has now been set to {{0.3.0-SNAPSHOT}} as suggested.
All the .pom files are now consistent.
> module versions on master dont match and are incorrect
> --
>
> Key: QPIDIT-131
> URL: https://issues.apache.org/jira/browse/QPIDIT-131
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Task
> Components: Installation
>Affects Versions: 0.3.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: 0.3.0
>
>
> The various modules version numbers on master dont match. The root pom is
> versions 0.2.0-rc1 while the children are still at 0.1.0 by virtue of having
> stale parent definitions. Thats its own issue since 0.1.0 was already
> released so new release modules definitely shouldn't have that version.
> Separately from not aligning with each other, they should really all be at
> 0.3.0-SNAPSHOT by now but aren't yet.
> See QPIDIT-130 for some an example on how to ease managing the module
> versions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-130) 'utils' module is versioned incorrectly
[
https://issues.apache.org/jira/browse/QPIDIT-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-130.
-
Resolution: Fixed
{{utils/pom.xml}} now has same version as the parent and other poms. Thanks for
the info on using the {{mvn}} command to do this, it is so much easier!
> 'utils' module is versioned incorrectly
> ---
>
> Key: QPIDIT-130
> URL: https://issues.apache.org/jira/browse/QPIDIT-130
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Installation
>Affects Versions: 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Blocker
> Fix For: 0.2.0
>
>
> The utils module is incorrectly still versioned as 0.1.0. This has obviously
> already been released and so must be corrected to 0.2.0 to prevent conflict.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-130) 'utils' module is versioned incorrectly
[ https://issues.apache.org/jira/browse/QPIDIT-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537231#comment-16537231 ] ASF subversion and git services commented on QPIDIT-130: Commit d665eb644588483fa2e5be9dffe9cdbfcbdd6b21 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=d665eb6 ] QPIDIT-130: Fixed utils/pom.xml version to "0.2.0" > 'utils' module is versioned incorrectly > --- > > Key: QPIDIT-130 > URL: https://issues.apache.org/jira/browse/QPIDIT-130 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.2.0 > > > The utils module is incorrectly still versioned as 0.1.0. This has obviously > already been released and so must be corrected to 0.2.0 to prevent conflict. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537230#comment-16537230 ] ASF subversion and git services commented on QPIDIT-125: Commit a8fd570e86ef3c60ebb58b88d08001d44a20 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=a8fd570 ] QPIDIT-125: Updated QUICKSTART.md to include info on installing Amqp.Net Lite > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1008) Router should preserve original connection information when attempting to make failover connections
[
https://issues.apache.org/jira/browse/DISPATCH-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537192#comment-16537192
]
ASF subversion and git services commented on DISPATCH-1008:
---
Commit 5f4f69c9a33818a3293717d56cc08916c736b8d8 in qpid-dispatch's branch
refs/heads/master from [~ganeshmurthy]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=5f4f69c ]
DISPATCH-1008 - Added code to preserve failover information from previous
connections. Failover information is never lost
> Router should preserve original connection information when attempting to
> make failover connections
> ---
>
> Key: DISPATCH-1008
> URL: https://issues.apache.org/jira/browse/DISPATCH-1008
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: broker-slave.xml, broker.xml, qdrouterd-failover.conf
>
>
> # Start artemis master and slave brokers and the router with the attached
> config files.
> # Notice that the router receives an open frame from the master broker with
> the following failover information
> #
> {noformat}
> 2018-05-22 22:11:11.830106 -0230 SERVER (trace) [1]:0 <- @open(16)
> [container-id="localhost", max-frame-size=4294967295, channel-max=65535,
> idle-time-out=3,
> offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container",
> :"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS-RELAY"],
> properties={:product="apache-activemq-artemis",
> :"failover-server-list"=[{:hostname="0.0.0.8", :scheme="amqp", :port=61617,
> :"network-host"="0.0.0.0"}]"}]{noformat}
>
> # Now, kill the master broker and notice that the router correctly fails
> over to the slave broker. But the slave broker does not provide any failover
> information in its open frame and hence the router erases its original master
> broker connection information
> # When the master broker is now restarted and the slave broker is killed,
> the router attempts to repeatedly connect only to the slave broker but never
> attempts a connection to the master broker.
> # If the router did not erase its failover list but preserved the original
> master connection information, it would have connected the master broker.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537190#comment-16537190 ] ASF subversion and git services commented on QPIDIT-125: Commit 4cd85c248634beaf176dabbeef76d87cb0fe2a7f in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=4cd85c2 ] QPIDIT-125: Fix for two .pom files with incorrect version and dependecy version information > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537191#comment-16537191 ] ASF subversion and git services commented on QPIDIT-125: Commit 21bd232bdc9fd66715a94bd331e1e3c47d8ffb45 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=21bd232 ] QPIDIT-125: Updated QUICKSTART to give some details on installing Amqp.Net Lite, changed Maven pom files on master to be release 0.3.0-SNAPSHOT > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-131) module versions on master dont match and are incorrect
[ https://issues.apache.org/jira/browse/QPIDIT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPIDIT-131: --- Assignee: Kim van der Riet > module versions on master dont match and are incorrect > -- > > Key: QPIDIT-131 > URL: https://issues.apache.org/jira/browse/QPIDIT-131 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task > Components: Installation >Affects Versions: 0.3.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.3.0 > > > The various modules version numbers on master dont match. The root pom is > versions 0.2.0-rc1 while the children are still at 0.1.0 by virtue of having > stale parent definitions. Thats its own issue since 0.1.0 was already > released so new release modules definitely shouldn't have that version. > Separately from not aligning with each other, they should really all be at > 0.3.0-SNAPSHOT by now but aren't yet. > See QPIDIT-130 for some an example on how to ease managing the module > versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-129) tests reference wrong 'shim' version for Qpid JMS
[
https://issues.apache.org/jira/browse/QPIDIT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet reassigned QPIDIT-129:
---
Assignee: Kim van der Riet
> tests reference wrong 'shim' version for Qpid JMS
> -
>
> Key: QPIDIT-129
> URL: https://issues.apache.org/jira/browse/QPIDIT-129
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Installation
>Affects Versions: 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Blocker
> Fix For: 0.2.0
>
>
> The installed 0.2.0 RC2 tests look for the wrong shim, at:
> {noformat}
> /path.to/install/libexec/qpid_interop_test/shims/qpid-jms/qpid-interop-test-jms-shim-0.1.0-jar-with-dependencies.jar
> {noformat}
> While the file actually installed, after the changes in RC2 is now correctly
> named:
> {noformat}
> /path.to/install/libexec/qpid_interop_test/shims/qpid-jms/qpid-interop-test-jms-shim-0.2.0-jar-with-dependencies.jar
> {noformat}
> This causes the tests to fail (once QPIDIT-128 is worked around).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-130) 'utils' module is versioned incorrectly
[ https://issues.apache.org/jira/browse/QPIDIT-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPIDIT-130: --- Assignee: Kim van der Riet > 'utils' module is versioned incorrectly > --- > > Key: QPIDIT-130 > URL: https://issues.apache.org/jira/browse/QPIDIT-130 > Project: Apache QPID Interoperability Test Suite > Issue Type: Bug > Components: Installation >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.2.0 > > > The utils module is incorrectly still versioned as 0.1.0. This has obviously > already been released and so must be corrected to 0.2.0 to prevent conflict. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-128) misuse of JAVA_HOME causes tests to error without clear indication why
[
https://issues.apache.org/jira/browse/QPIDIT-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet reassigned QPIDIT-128:
---
Assignee: Kim van der Riet
> misuse of JAVA_HOME causes tests to error without clear indication why
> --
>
> Key: QPIDIT-128
> URL: https://issues.apache.org/jira/browse/QPIDIT-128
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0, 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.2.0
>
>
> The interop suite misuses JAVA_HOME, and in doing so Python tries to run java
> from the wrong place. This results in the tests erroring out with note of a
> file not found, but with no indication what file wasn't found. Resorting to
> some prints for debugging, it emerges that Python is being asked to run Java
> with the wrong location
> JAVA_HOME points to the root of the java installation, with the java command
> and various others then found in the bin subdir. The interop tests currently
> omit the bin subdir when JAVA_HOME was actually defined, but do include it
> (via a fragile and debatable hard coded default) when JAVA_HOME is not
> defined:
> {noformat}
> JAVA_HOME = os.getenv('JAVA_HOME', '/usr/bin') # Default only works in Linux
> JAVA_EXEC = os.path.join(JAVA_HOME, 'java')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-127) update to use the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDIT-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPIDIT-127: --- Assignee: Kim van der Riet > update to use the current v19 apache parent pom > --- > > Key: QPIDIT-127 > URL: https://issues.apache.org/jira/browse/QPIDIT-127 > Project: Apache QPID Interoperability Test Suite > Issue Type: Improvement > Components: Installation, Qpid Jms Shim >Affects Versions: 0.2.0 >Reporter: Robbie Gemmell >Assignee: Kim van der Riet >Priority: Minor > Fix For: 0.3.0 > > > update to use the current v19 apache parent pom to better align with other > components going forward (e.g see also QPIDJMS-397) and aid in consistent use > of plugin versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-1889) failure reading from composite buffer if expanded with new data after prior content was exhausted
[ https://issues.apache.org/jira/browse/PROTON-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1889. Resolution: Fixed > failure reading from composite buffer if expanded with new data after prior > content was exhausted > - > > Key: PROTON-1889 > URL: https://issues.apache.org/jira/browse/PROTON-1889 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.27.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.28.0 > > > The CompositeReadableBuffer allows aggregating incoming byte[] data (e.g > delivery frame contents) to be used by other areas. If a CRB reads to the end > of its existing content array(s) and is then further expanded with more data > as it becomes ready, the new content can't be read and instead an IOOBE > occurs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1889) failure reading from composite buffer if expanded with new data after prior content was exhausted
[ https://issues.apache.org/jira/browse/PROTON-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16537121#comment-16537121 ] ASF subversion and git services commented on PROTON-1889: - Commit c5e2f7990ca82cdf682c8ee3e27ad611447e542e in qpid-proton-j's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=c5e2f79 ] PROTON-1889: ensure array indexing is updated if needed when appending new content to the composite > failure reading from composite buffer if expanded with new data after prior > content was exhausted > - > > Key: PROTON-1889 > URL: https://issues.apache.org/jira/browse/PROTON-1889 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: proton-j-0.27.1 >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.28.0 > > > The CompositeReadableBuffer allows aggregating incoming byte[] data (e.g > delivery frame contents) to be used by other areas. If a CRB reads to the end > of its existing content array(s) and is then further expanded with more data > as it becomes ready, the new content can't be read and instead an IOOBE > occurs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1889) failure reading from composite buffer if expanded with new data after prior content was exhausted
Robbie Gemmell created PROTON-1889: -- Summary: failure reading from composite buffer if expanded with new data after prior content was exhausted Key: PROTON-1889 URL: https://issues.apache.org/jira/browse/PROTON-1889 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: proton-j-0.27.1 Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: proton-j-0.28.0 The CompositeReadableBuffer allows aggregating incoming byte[] data (e.g delivery frame contents) to be used by other areas. If a CRB reads to the end of its existing content array(s) and is then further expanded with more data as it becomes ready, the new content can't be read and instead an IOOBE occurs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Register now for ApacheCon and save $250
Greetings, Apache software enthusiasts! (You’re getting this because you’re on one or more dev@ or users@ lists for some Apache Software Foundation project.) ApacheCon North America, in Montreal, is now just 80 days away, and early bird prices end in just two weeks - on July 21. Prices will be going up from $550 to $800 so register NOW to save $250, at http://apachecon.com/acna18 And don’t forget to reserve your hotel room. We have negotiated a special rate and the room block closes August 24. http://www.apachecon.com/acna18/venue.html Our schedule includes over 100 talks and we’ll be featuring talks from dozens of ASF projects., We have inspiring keynotes from some of the brilliant members of our community and the wider tech space, including: * Myrle Krantz, PMC chair for Apache Fineract, and leader in the open source financing space * Cliff Schmidt, founder of Literacy Bridge (now Amplio) and creator of the Talking Book project * Bridget Kromhout, principal cloud developer advocate at Microsoft * Euan McLeod, Comcast engineer, and pioneer in streaming video We’ll also be featuring tracks for Geospatial science, Tomcat, Cloudstack, and Big Data, as well as numerous other fields where Apache software is leading the way. See the full schedule at http://apachecon.com/acna18/schedule.html As usual we’ll be running our Apache BarCamp, the traditional ApacheCon Hackathon, and the Wednesday evening Lighting Talks, too, so you’ll want to be there. Register today at http://apachecon.com/acna18 and we’ll see you in Montreal! -- Rich Bowen VP, Conferences, The Apache Software Foundation h...@apachecon.com @ApacheCon - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1063) Receiver unable to receive messages on waypoint address with external-address in two router case
[
https://issues.apache.org/jira/browse/DISPATCH-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536953#comment-16536953
]
Ganesh Murthy commented on DISPATCH-1063:
-
Manually tested after applying the fix and I am able to send and receive from
router B. The automated system test looks good and worked as well.
> Receiver unable to receive messages on waypoint address with external-address
> in two router case
>
>
> Key: DISPATCH-1063
> URL: https://issues.apache.org/jira/browse/DISPATCH-1063
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.1.0, 1.2.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.3.0
>
> Attachments: A2.conf, B2.conf
>
>
> Start two routers with the attached config files.
> Start a broker on port amqp and create a queue called abc.sms
> Attach a sender to Router B and send 100 messages to the "notify" address
> like this
> {noformat}
> python simple_recv.py -m100 --address 0.0.0.0:20101/notify{noformat}
> Attach a Receiver to Router B and receive 1 message from the "notify" address
> like this -
> {noformat}
> python simple_recv.py -m1 --address 0.0.0.0:20101/notify{noformat}
> The receiver never receives the message
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton pull request #150: PROTON-1888: allow configuration of connectio...
GitHub user grs opened a pull request: https://github.com/apache/qpid-proton/pull/150 PROTON-1888: allow configuration of connection details from a config ⦠â¦file The file to use can be specified using the CONNECT_CONFIG environment variable. If that is not set, it will look for a file name connect.json, first in the current directory, then in the users local configuration directory (~/.config/messaging) and then in the system config directory (/etc/messaging/) The config file is in json format and the following properties can be specified: scheme host port sasl_mechanisms user password cert_file private_key_file private_key_password ca_cert_file You can merge this pull request into a Git repository by running: $ git pull https://github.com/grs/qpid-proton default_connect_proposal Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/150.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #150 commit 52f0f270dc40017cdaffba4f9c5e865e2859df4d Author: Gordon Sim Date: 2018-05-16T15:54:19Z PROTON-1888: allow configuration of connection details from a config file The file to use can be specified using the CONNECT_CONFIG environment variable. If that is not set, it will look for a file name connect.json, first in the current directory, then in the users local configuration directory (~/.config/messaging) and then in the system config directory (/etc/messaging/) The config file is in json format and the following properties can be specified: scheme host port sasl_mechanisms user password cert_file private_key_file private_key_password ca_cert_file --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1888) Allow configuration of connection details via a simple config file
[ https://issues.apache.org/jira/browse/PROTON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536770#comment-16536770 ] ASF GitHub Bot commented on PROTON-1888: GitHub user grs opened a pull request: https://github.com/apache/qpid-proton/pull/150 PROTON-1888: allow configuration of connection details from a config … …file The file to use can be specified using the CONNECT_CONFIG environment variable. If that is not set, it will look for a file name connect.json, first in the current directory, then in the users local configuration directory (~/.config/messaging) and then in the system config directory (/etc/messaging/) The config file is in json format and the following properties can be specified: scheme host port sasl_mechanisms user password cert_file private_key_file private_key_password ca_cert_file You can merge this pull request into a Git repository by running: $ git pull https://github.com/grs/qpid-proton default_connect_proposal Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-proton/pull/150.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #150 commit 52f0f270dc40017cdaffba4f9c5e865e2859df4d Author: Gordon Sim Date: 2018-05-16T15:54:19Z PROTON-1888: allow configuration of connection details from a config file The file to use can be specified using the CONNECT_CONFIG environment variable. If that is not set, it will look for a file name connect.json, first in the current directory, then in the users local configuration directory (~/.config/messaging) and then in the system config directory (/etc/messaging/) The config file is in json format and the following properties can be specified: scheme host port sasl_mechanisms user password cert_file private_key_file private_key_password ca_cert_file > Allow configuration of connection details via a simple config file > -- > > Key: PROTON-1888 > URL: https://issues.apache.org/jira/browse/PROTON-1888 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Gordon Sim >Priority: Major > > It can be convenient to keep details of the connection to be established out > of application code, making it easier to switch between environments. Support > for a simple config file that can be used to point the application at the > right AMQP service would be useful. Ideally this would be common across a > range of clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-1888) Allow configuration of connection details via a simple config file
Gordon Sim created PROTON-1888: -- Summary: Allow configuration of connection details via a simple config file Key: PROTON-1888 URL: https://issues.apache.org/jira/browse/PROTON-1888 Project: Qpid Proton Issue Type: Improvement Components: python-binding Reporter: Gordon Sim It can be convenient to keep details of the connection to be established out of application code, making it easier to switch between environments. Support for a simple config file that can be used to point the application at the right AMQP service would be useful. Ideally this would be common across a range of clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
