[GitHub] [qpid-dispatch] codecov-io commented on issue #547: NO JIRA: Fix typo and minor issues in doc
codecov-io commented on issue #547: NO JIRA: Fix typo and minor issues in doc URL: https://github.com/apache/qpid-dispatch/pull/547#issuecomment-516184344 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/547?src=pr=h1) Report > Merging [#547](https://codecov.io/gh/apache/qpid-dispatch/pull/547?src=pr=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/7c67a39aaafc161f15071b1da0baf2a023252b07?src=pr=desc) will **increase** coverage by `0.02%`. > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/547?src=pr=tree) ```diff @@Coverage Diff @@ ## master #547 +/- ## == + Coverage 86.53% 86.55% +0.02% == Files 88 88 Lines 1964019640 == + Hits1699517000 +5 + Misses 2645 2640 -5 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/547?src=pr=tree) | Coverage Δ | | |---|---|---| | [src/router\_node.c](https://codecov.io/gh/apache/qpid-dispatch/pull/547/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9ub2RlLmM=) | `92.87% <0%> (+0.12%)` | :arrow_up: | | [src/router\_core/connections.c](https://codecov.io/gh/apache/qpid-dispatch/pull/547/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2Nvbm5lY3Rpb25zLmM=) | `94.47% <0%> (+0.23%)` | :arrow_up: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/547/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `94.37% <0%> (+0.25%)` | :arrow_up: | | [src/router\_core/agent\_link.c](https://codecov.io/gh/apache/qpid-dispatch/pull/547/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2xpbmsuYw==) | `67.33% <0%> (+0.5%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/547?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-dispatch/pull/547?src=pr=footer). Last update [7c67a39...5cce917](https://codecov.io/gh/apache/qpid-dispatch/pull/547?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] bhardesty opened a new pull request #547: NO JIRA: Fix typo and minor issues in doc
bhardesty opened a new pull request #547: NO JIRA: Fix typo and minor issues in doc URL: https://github.com/apache/qpid-dispatch/pull/547 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895541#comment-16895541 ] ASF GitHub Bot commented on DISPATCH-1389: -- kgiusti commented on pull request #546: DISPATCH-1389: optimize qd_iterator_advance, qd_iterator_ncopy and URL: https://github.com/apache/qpid-dispatch/pull/546 qd_iterator_equal to use multi-byte operations when the iterator view is in the raw data. Results of two-hop router test on my development system: current master: 5.165: msgs sent=50 msgs/sec= 96797.306 with this patch: 4.844: msgs sent=50 msgs/sec= 103228.321 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] kgiusti opened a new pull request #546: DISPATCH-1389: optimize qd_iterator_advance, qd_iterator_ncopy and
kgiusti opened a new pull request #546: DISPATCH-1389: optimize qd_iterator_advance, qd_iterator_ncopy and URL: https://github.com/apache/qpid-dispatch/pull/546 qd_iterator_equal to use multi-byte operations when the iterator view is in the raw data. Results of two-hop router test on my development system: current master: 5.165: msgs sent=50 msgs/sec= 96797.306 with this patch: 4.844: msgs sent=50 msgs/sec= 103228.321 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895511#comment-16895511 ] ASF subversion and git services commented on DISPATCH-1389: --- Commit 7c67a39aaafc161f15071b1da0baf2a023252b07 in qpid-dispatch's branch refs/heads/master from Ken Giusti [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=7c67a39 ] DISPATCH-1389: optimize the STATE_IN_BODY codepath in qd_iterator_octet This closes #541 > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895512#comment-16895512 ] ASF GitHub Bot commented on DISPATCH-1389: -- asfgit commented on pull request #541: DISPATCH-1389: optimize the STATE_IN_BODY codepath in qd_iterator_octet URL: https://github.com/apache/qpid-dispatch/pull/541 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] asfgit closed pull request #541: DISPATCH-1389: optimize the STATE_IN_BODY codepath in qd_iterator_octet
asfgit closed pull request #541: DISPATCH-1389: optimize the STATE_IN_BODY codepath in qd_iterator_octet URL: https://github.com/apache/qpid-dispatch/pull/541 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2081) Hang in Windows proactor during connect
[ https://issues.apache.org/jira/browse/PROTON-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved PROTON-2081. -- Resolution: Fixed Fix Version/s: proton-c-0.29.0 > Hang in Windows proactor during connect > --- > > Key: PROTON-2081 > URL: https://issues.apache.org/jira/browse/PROTON-2081 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.28.0 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > Fix For: proton-c-0.29.0 > > > The bug is a simple race between threads. The necessary context for the > connect completion routine should be set before the async connect is > initiated, not after. If the completion routine runs ahead of the context > setup, the successful connect data is mistaken for a drained completion on a > closed connection. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2081) Hang in Windows proactor during connect
[ https://issues.apache.org/jira/browse/PROTON-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895467#comment-16895467 ] ASF subversion and git services commented on PROTON-2081: - Commit 85726a4539a037fd2965f91748d0c8ae4d3d90a3 in qpid-proton's branch refs/heads/master from Clifford Jansen [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=85726a4 ] PROTON-2081: Hang in Windows proactor during connect - thread race > Hang in Windows proactor during connect > --- > > Key: PROTON-2081 > URL: https://issues.apache.org/jira/browse/PROTON-2081 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.28.0 > Environment: Windows >Reporter: Cliff Jansen >Assignee: Cliff Jansen >Priority: Major > > The bug is a simple race between threads. The necessary context for the > connect completion routine should be set before the async connect is > initiated, not after. If the completion routine runs ahead of the context > setup, the successful connect data is mistaken for a drained completion on a > closed connection. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2081) Hang in Windows proactor during connect
Cliff Jansen created PROTON-2081: Summary: Hang in Windows proactor during connect Key: PROTON-2081 URL: https://issues.apache.org/jira/browse/PROTON-2081 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.28.0 Environment: Windows Reporter: Cliff Jansen Assignee: Cliff Jansen The bug is a simple race between threads. The necessary context for the connect completion routine should be set before the async connect is initiated, not after. If the completion routine runs ahead of the context setup, the successful connect data is mistaken for a drained completion on a closed connection. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7042) [Java Broker, Documentation] Add documentation about virtual host aliases
[ https://issues.apache.org/jira/browse/QPID-7042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895435#comment-16895435 ] Chris O'Brien commented on QPID-7042: - Similar to QPID-7510, I had some difficulty figuring out how to correctly configure a port's virtualhostaliases. More detailed documentation on how this config block decides which virtualhost to route connections to would be much appreciated. > [Java Broker, Documentation] Add documentation about virtual host aliases > - > > Key: QPID-7042 > URL: https://issues.apache.org/jira/browse/QPID-7042 > Project: Qpid > Issue Type: Improvement > Components: Broker-J, Java Documentation >Reporter: Lorenz Quack >Priority: Major > Fix For: Future > > > Currently there is no documentation about the virtualhostalias attribute of > AMQPPorts. Since the port won't properly work without it I think we need a > minimum amount of documentation. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1282) Support for building on macOS
[ https://issues.apache.org/jira/browse/DISPATCH-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895316#comment-16895316 ] ASF GitHub Bot commented on DISPATCH-1282: -- jdanekrh commented on issue #459: DISPATCH-1282 - Support for building on macOS URL: https://github.com/apache/qpid-dispatch/pull/459#issuecomment-516004987 @RoddieKieley Thank you for the review. I've opened followup Jira for fixing tests https://issues.apache.org/jira/browse/DISPATCH-1384 Unless anyone complains, I'll look into the unittest2 fragility, and then merge this PR and then continue fixing the tests in subsequent PRs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support for building on macOS > - > > Key: DISPATCH-1282 > URL: https://issues.apache.org/jira/browse/DISPATCH-1282 > Project: Qpid Dispatch > Issue Type: New Feature >Affects Versions: 1.5.0 >Reporter: Jiri Daněk >Priority: Major > Labels: macOS > > Currently, Dispatch compilation fails on "rt" library being unavailable. > All Dispatch dependencies (Qpid Proton, libwebsockets, ...) can be built on > macOS. > I am attaching a patch which allows to compile dispatch on OSX and run it. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] jdanekrh edited a comment on issue #459: DISPATCH-1282 - Support for building on macOS
jdanekrh edited a comment on issue #459: DISPATCH-1282 - Support for building on macOS URL: https://github.com/apache/qpid-dispatch/pull/459#issuecomment-516004987 @RoddieKieley Thank you for the review. I've opened followup Jira for fixing tests https://issues.apache.org/jira/browse/DISPATCH-1384 Unless anyone complains, I'll look into the unittest2 fragility, and then merge this PR and then continue fixing the tests in subsequent PRs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1282) Support for building on macOS
[ https://issues.apache.org/jira/browse/DISPATCH-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895281#comment-16895281 ] ASF GitHub Bot commented on DISPATCH-1282: -- jdanekrh commented on issue #459: DISPATCH-1282 - Support for building on macOS URL: https://github.com/apache/qpid-dispatch/pull/459#issuecomment-516004987 @RoddieKieley Thank you for the review. I've opened followup Jira for fixing tests https://issues.apache.org/jira/browse/DISPATCH-1384 Unless anyone complains, I'd merge this PR and then continue fixing the tests in subsequent PRs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Support for building on macOS > - > > Key: DISPATCH-1282 > URL: https://issues.apache.org/jira/browse/DISPATCH-1282 > Project: Qpid Dispatch > Issue Type: New Feature >Affects Versions: 1.5.0 >Reporter: Jiri Daněk >Priority: Major > Labels: macOS > > Currently, Dispatch compilation fails on "rt" library being unavailable. > All Dispatch dependencies (Qpid Proton, libwebsockets, ...) can be built on > macOS. > I am attaching a patch which allows to compile dispatch on OSX and run it. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] jdanekrh commented on issue #459: DISPATCH-1282 - Support for building on macOS
jdanekrh commented on issue #459: DISPATCH-1282 - Support for building on macOS URL: https://github.com/apache/qpid-dispatch/pull/459#issuecomment-516004987 @RoddieKieley Thank you for the review. I've opened followup Jira for fixing tests https://issues.apache.org/jira/browse/DISPATCH-1384 Unless anyone complains, I'd merge this PR and then continue fixing the tests in subsequent PRs. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895267#comment-16895267 ] ASF subversion and git services commented on DISPATCH-1389: --- Commit e29257a8b2ec21831ad60d563f78df0d7e4c793a in qpid-dispatch's branch refs/heads/master from Ken Giusti [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=e29257a ] DISPATCH-1389: export qd_buffer_t access methods inline The qd_buffer_t structure is defined in the header file as a public structure. There are several trivial methods that are called frequently enough that there is a benefit to performance by inlining them. This closes #544 > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895268#comment-16895268 ] ASF GitHub Bot commented on DISPATCH-1389: -- asfgit commented on pull request #544: DISPATCH-1389: export qd_buffer_t access methods inline URL: https://github.com/apache/qpid-dispatch/pull/544 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] asfgit closed pull request #544: DISPATCH-1389: export qd_buffer_t access methods inline
asfgit closed pull request #544: DISPATCH-1389: export qd_buffer_t access methods inline URL: https://github.com/apache/qpid-dispatch/pull/544 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8348) [Broker-J] Add ability to reload keystore/truststore
[ https://issues.apache.org/jira/browse/QPID-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8348: Assignee: Alex Rudyy > [Broker-J] Add ability to reload keystore/truststore > > > Key: QPID-8348 > URL: https://issues.apache.org/jira/browse/QPID-8348 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Assignee: Alex Rudyy >Priority: Major > Labels: keystore, truststore > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.5 > > > Currently there is no way to reload already loaded keystore or truststore. It > should be possible to reload keystore on configured path of > keystore/truststore by REST API (Access Control Provider has similar > functionality). -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8348) [Broker-J] Add ability to reload keystore/truststore
[ https://issues.apache.org/jira/browse/QPID-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8348: - Status: Reviewable (was: In Progress) > [Broker-J] Add ability to reload keystore/truststore > > > Key: QPID-8348 > URL: https://issues.apache.org/jira/browse/QPID-8348 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Assignee: Alex Rudyy >Priority: Major > Labels: keystore, truststore > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.5 > > > Currently there is no way to reload already loaded keystore or truststore. It > should be possible to reload keystore on configured path of > keystore/truststore by REST API (Access Control Provider has similar > functionality). -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for me
[
https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8345:
-
Status: Reviewable (was: In Progress)
> [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue
> when receiver’s desired snd-settle-mode is set to settled and transactions
> are not used for message receiving
> --
>
> Key: QPID-8345
> URL: https://issues.apache.org/jira/browse/QPID-8345
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1,
> qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5,
> qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3,
> qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.8,
> qpid-java-broker-7.1.5
>
>
> When receiving link desired {{snd-settle-mode}} is set to {{settled}} and
> transactions are not used for message receiving, the broker sending link
> sends the messages pre-settled.
> However, the consumed messages are left in acquired state on the queue after
> sending them to consumer. Such messages stack in {{acquired}} state until
> broker is restarted. After the restart, the persistent message became
> available for consumption again.
> The broker should remove sent pre-settled messages from the queue queue. If
> consumer default outcome is set explicitly to other value than {{accepted}}
> or null, than the transfer state should be set to {{accepted}} in order to
> notify the receiver about sender behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for me
[
https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8345:
-
Fix Version/s: qpid-java-broker-7.0.8
qpid-java-broker-8.0.0
> [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue
> when receiver’s desired snd-settle-mode is set to settled and transactions
> are not used for message receiving
> --
>
> Key: QPID-8345
> URL: https://issues.apache.org/jira/browse/QPID-8345
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1,
> qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5,
> qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3,
> qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.8,
> qpid-java-broker-7.1.5
>
>
> When receiving link desired {{snd-settle-mode}} is set to {{settled}} and
> transactions are not used for message receiving, the broker sending link
> sends the messages pre-settled.
> However, the consumed messages are left in acquired state on the queue after
> sending them to consumer. Such messages stack in {{acquired}} state until
> broker is restarted. After the restart, the persistent message became
> available for consumption again.
> The broker should remove sent pre-settled messages from the queue queue. If
> consumer default outcome is set explicitly to other value than {{accepted}}
> or null, than the transfer state should be set to {{accepted}} in order to
> notify the receiver about sender behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8344) [Broker-J] Generation of virtal host registry dump fails
[
https://issues.apache.org/jira/browse/QPID-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8344:
-
Status: Reviewable (was: In Progress)
> [Broker-J] Generation of virtal host registry dump fails
>
>
> Key: QPID-8344
> URL: https://issues.apache.org/jira/browse/QPID-8344
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> Generation of link registry dump fail with the following stack trace
> {noformat}
> 2019-07-20 18:44:44,378 WARN [qtp505675560-137]
> (o.a.q.s.m.p.s.r.AbstractServlet) - Unexpected exception processing request
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer
> found for class
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump$ContainerDump
> and no properties discovered to create BeanSerializer (to avoid exception,
> disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain:
> java.util.Collections$SingletonMap["containers"]->java.util.Collections$UnmodifiableMap["testContainer-31"])
> at
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException.from(InvalidDefinitionException.java:77)
> at
> com.fasterxml.jackson.databind.SerializerProvider.reportBadDefinition(SerializerProvider.java:1191)
> at
> com.fasterxml.jackson.databind.DatabindContext.reportBadDefinition(DatabindContext.java:313)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.failForEmpty(UnknownSerializer.java:71)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.serialize(UnknownSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider._serialize(DefaultSerializerProvider.java:480)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:319)
> at
> com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3906)
> at
> com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:3177)
> at
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump.write(LinkRegistryImpl.java:279)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.writeTypedContent(AbstractServlet.java:296)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.sendResponse(RestServlet.java:251)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.doGet(RestServlet.java:119)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.doGet(AbstractServlet.java:128)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "dele
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8343:
-
Description:
When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
set to true and property {{dynamic-node-properties}} contains entry
{{lifetime-policy}} with value set to either {{delete-on-close}} or
{{delete-on-no-links}} or {{delete-on-no-messages}} or
{{delete-on-no-links-or-messages}}, the broker creates a durable temporary
queue.
Such temporary queues should be non-durable unless terminus expiry policy is
set to never.
was:
When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
set to true and property {{dynamic-node-properties}} contains entry
{{lifetime-policy}} with value set to either {{delete-on-close}} or
{{delete-on-no-links}} or {{delete-on-no-messages}} or
{{delete-on-no-links-or-messages}}, the broker creates a durable temporary
queue.
Such temporary queues should be non-durable.
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.9,
> qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> Such temporary queues should be non-durable unless terminus expiry policy is
> set to never.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895254#comment-16895254 ] ASF GitHub Bot commented on DISPATCH-1389: -- asfgit commented on pull request #542: DISPATCH-1389: force inlining of local compose functions URL: https://github.com/apache/qpid-dispatch/pull/542 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1389) Optimize the parsing of message annotations
[ https://issues.apache.org/jira/browse/DISPATCH-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895253#comment-16895253 ] ASF subversion and git services commented on DISPATCH-1389: --- Commit bd3828d3e305d24b647f86615399ae51a402ba71 in qpid-dispatch's branch refs/heads/master from Ken Giusti [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=bd3828d ] DISPATCH-1389: force inlining of local compose functions This closes #542 > Optimize the parsing of message annotations > --- > > Key: DISPATCH-1389 > URL: https://issues.apache.org/jira/browse/DISPATCH-1389 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > > Parsing message annotations, especially on the inter router incoming link, > are quite expensive. > For example, in a simple standalone router test the time it takes on average > (on my puny laptop) to receive a message and hand it off to the core is ~1 > usec: > TestRouterA: link MyReceiver count=50 rx=1.094 > Compare that time to the same operation performed on the inbound router link > on a two-hop router configuration: > TestRouterB: link MyReceiver count=50 rx=7.035 > On average it's 7x slower. Most of this time appears to be spent > manipulating inbound message annotations. > > This Jira tracks work towards improving the performance of message annotation > processing. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] asfgit closed pull request #542: DISPATCH-1389: force inlining of local compose functions
asfgit closed pull request #542: DISPATCH-1389: force inlining of local compose functions URL: https://github.com/apache/qpid-dispatch/pull/542 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "dele
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8343:
-
Fix Version/s: qpid-java-broker-7.0.9
qpid-java-broker-8.0.0
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.9,
> qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> The node expiry policy is not set. Thus, default {{session-end}} should be
> used. Durability is not set either.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "dele
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8343:
-
Status: Reviewable (was: In Progress)
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.9,
> qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> The node expiry policy is not set. Thus, default {{session-end}} should be
> used. Durability is not set either.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "dele
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8343:
-
Description:
When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
set to true and property {{dynamic-node-properties}} contains entry
{{lifetime-policy}} with value set to either {{delete-on-close}} or
{{delete-on-no-links}} or {{delete-on-no-messages}} or
{{delete-on-no-links-or-messages}}, the broker creates a durable temporary
queue.
Such temporary queues should be non-durable.
was:
When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
set to true and property {{dynamic-node-properties}} contains entry
{{lifetime-policy}} with value set to either {{delete-on-close}} or
{{delete-on-no-links}} or {{delete-on-no-messages}} or
{{delete-on-no-links-or-messages}}, the broker creates a durable temporary
queue.
The node expiry policy is not set. Thus, default {{session-end}} should be
used. Durability is not set either.
Such temporary queues should be non-durable.
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.9,
> qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "del
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8343:
Assignee: Alex Rudyy
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.0.9,
> qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> The node expiry policy is not set. Thus, default {{session-end}} should be
> used. Durability is not set either.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for
[
https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895145#comment-16895145
]
ASF subversion and git services commented on QPID-8345:
---
Commit 67a3a525a717835003e506105fb5d4763cda1ac5 in qpid-broker-j's branch
refs/heads/7.0.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=67a3a52 ]
QPID-8345: [Broker-J][AMQP 1.0] Dequeue messages sent non-transactionally as
pre-settled
(cherry picked from commit ca0d0d7ec22c31364c1adc32f5dffee0392ff230)
> [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue
> when receiver’s desired snd-settle-mode is set to settled and transactions
> are not used for message receiving
> --
>
> Key: QPID-8345
> URL: https://issues.apache.org/jira/browse/QPID-8345
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1,
> qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5,
> qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3,
> qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> When receiving link desired {{snd-settle-mode}} is set to {{settled}} and
> transactions are not used for message receiving, the broker sending link
> sends the messages pre-settled.
> However, the consumed messages are left in acquired state on the queue after
> sending them to consumer. Such messages stack in {{acquired}} state until
> broker is restarted. After the restart, the persistent message became
> available for consumption again.
> The broker should remove sent pre-settled messages from the queue queue. If
> consumer default outcome is set explicitly to other value than {{accepted}}
> or null, than the transfer state should be set to {{accepted}} in order to
> notify the receiver about sender behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "de
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895146#comment-16895146
]
ASF subversion and git services commented on QPID-8343:
---
Commit 21becf4e443120c29ef212913764a345bdf85e76 in qpid-broker-j's branch
refs/heads/7.0.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=21becf4 ]
QPID-8343: [Broker-J][AMQP 1.0] Derive dynamic node durability from terminus
expiry policy
(cherry picked from commit bf75f490170beb91f72547c00c365bf024cbaa1f)
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> The node expiry policy is not set. Thus, default {{session-end}} should be
> used. Durability is not set either.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
Re: C types for timestamps and durations
Thanks for the comments, I've tried to put it in practice in https://github.com/apache/qpid-proton/pull/180 -- Mit freundlichen Grüßen / Kind regards Jiri Daněk
[jira] [Commented] (PROTON-2076) Proton stopped building with -DTHREADERCISER=ON after test_main.cpp was added
[
https://issues.apache.org/jira/browse/PROTON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895129#comment-16895129
]
Jiri Daněk commented on PROTON-2076:
One more issue not fixed by the PR above. Since this is the only c-language
test, all other tests are built using cpp, -std=c99 and this happens
{noformat}
/home/jdanek/projects/qpid-proton/c/tests/threaderciser.c: In function
‘pool_pick’:
/home/jdanek/projects/qpid-proton/c/tests/threaderciser.c:176:3: error: ISO C90
forbids mixed declarations and code [-Wpedantic]
pool_entry *entry = NULL;
^
{noformat}
> Proton stopped building with -DTHREADERCISER=ON after test_main.cpp was added
> -
>
> Key: PROTON-2076
> URL: https://issues.apache.org/jira/browse/PROTON-2076
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Reporter: Jiri Daněk
>Priority: Major
>
> Enhancement PROTON-2048 broke compilation with cmake option -DTHREADERCISER=ON
> {noformat}
> [ 69%] Linking CXX executable c-threaderciser
> [ 69%] Building CXX object
> cpp/CMakeFiles/credit_test.dir/src/credit_test.cpp.o
> [ 69%] Building CXX object
> cpp/CMakeFiles/connection_driver_test.dir/src/connection_driver_test.cpp.o
> /nix/store/0y7jmqnj48ikjh37n3dl9kqw9hnn68nq-binutils-2.31.1/bin/ld:
> CMakeFiles/test_main.dir/test_main.cpp.o: in function `main':
> /home/jdanek/repos/qpid/qpid-proton/tests/include/catch.hpp:11466: multiple
> definition of `main';
> CMakeFiles/c-threaderciser.dir/threaderciser.c.o:/home/jdanek/repos/qpid/qpid-proton/c/tests/threaderciser.c:508:
> first defined here
> collect2: error: ld returned 1 exit status
> make[2]: *** [c/tests/CMakeFiles/c-threaderciser.dir/build.make:107:
> c/tests/c-threaderciser] Error 1
> make[1]: *** [CMakeFiles/Makefile2:1746:
> c/tests/CMakeFiles/c-threaderciser.dir/all] Error 2
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8344) [Broker-J] Generation of virtal host registry dump fails
[
https://issues.apache.org/jira/browse/QPID-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8344:
Assignee: Alex Rudyy
> [Broker-J] Generation of virtal host registry dump fails
>
>
> Key: QPID-8344
> URL: https://issues.apache.org/jira/browse/QPID-8344
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> Generation of link registry dump fail with the following stack trace
> {noformat}
> 2019-07-20 18:44:44,378 WARN [qtp505675560-137]
> (o.a.q.s.m.p.s.r.AbstractServlet) - Unexpected exception processing request
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer
> found for class
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump$ContainerDump
> and no properties discovered to create BeanSerializer (to avoid exception,
> disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain:
> java.util.Collections$SingletonMap["containers"]->java.util.Collections$UnmodifiableMap["testContainer-31"])
> at
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException.from(InvalidDefinitionException.java:77)
> at
> com.fasterxml.jackson.databind.SerializerProvider.reportBadDefinition(SerializerProvider.java:1191)
> at
> com.fasterxml.jackson.databind.DatabindContext.reportBadDefinition(DatabindContext.java:313)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.failForEmpty(UnknownSerializer.java:71)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.serialize(UnknownSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider._serialize(DefaultSerializerProvider.java:480)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:319)
> at
> com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3906)
> at
> com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:3177)
> at
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump.write(LinkRegistryImpl.java:279)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.writeTypedContent(AbstractServlet.java:296)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.sendResponse(RestServlet.java:251)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.doGet(RestServlet.java:119)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.doGet(AbstractServlet.java:128)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for m
[
https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8345:
Assignee: Alex Rudyy
> [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue
> when receiver’s desired snd-settle-mode is set to settled and transactions
> are not used for message receiving
> --
>
> Key: QPID-8345
> URL: https://issues.apache.org/jira/browse/QPID-8345
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1,
> qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5,
> qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3,
> qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> When receiving link desired {{snd-settle-mode}} is set to {{settled}} and
> transactions are not used for message receiving, the broker sending link
> sends the messages pre-settled.
> However, the consumed messages are left in acquired state on the queue after
> sending them to consumer. Such messages stack in {{acquired}} state until
> broker is restarted. After the restart, the persistent message became
> available for consumption again.
> The broker should remove sent pre-settled messages from the queue queue. If
> consumer default outcome is set explicitly to other value than {{accepted}}
> or null, than the transfer state should be set to {{accepted}} in order to
> notify the receiver about sender behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8344) [Broker-J] Generation of virtal host registry dump fails
[
https://issues.apache.org/jira/browse/QPID-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895123#comment-16895123
]
ASF subversion and git services commented on QPID-8344:
---
Commit 63c674bddd504b3eb160c66040b66f9994190286 in qpid-broker-j's branch
refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=63c674b ]
QPID-8344: [Broker-J] Fix link registry dump generation
(cherry picked from commit 679d577b5ed1a25ff75035922a07813227c844bd)
> [Broker-J] Generation of virtal host registry dump fails
>
>
> Key: QPID-8344
> URL: https://issues.apache.org/jira/browse/QPID-8344
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.0, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> Generation of link registry dump fail with the following stack trace
> {noformat}
> 2019-07-20 18:44:44,378 WARN [qtp505675560-137]
> (o.a.q.s.m.p.s.r.AbstractServlet) - Unexpected exception processing request
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer
> found for class
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump$ContainerDump
> and no properties discovered to create BeanSerializer (to avoid exception,
> disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain:
> java.util.Collections$SingletonMap["containers"]->java.util.Collections$UnmodifiableMap["testContainer-31"])
> at
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException.from(InvalidDefinitionException.java:77)
> at
> com.fasterxml.jackson.databind.SerializerProvider.reportBadDefinition(SerializerProvider.java:1191)
> at
> com.fasterxml.jackson.databind.DatabindContext.reportBadDefinition(DatabindContext.java:313)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.failForEmpty(UnknownSerializer.java:71)
> at
> com.fasterxml.jackson.databind.ser.impl.UnknownSerializer.serialize(UnknownSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serializeFields(MapSerializer.java:722)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:643)
> at
> com.fasterxml.jackson.databind.ser.std.MapSerializer.serialize(MapSerializer.java:33)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider._serialize(DefaultSerializerProvider.java:480)
> at
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:319)
> at
> com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3906)
> at
> com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:3177)
> at
> org.apache.qpid.server.protocol.v1_0.LinkRegistryImpl$LinkRegistryDump.write(LinkRegistryImpl.java:279)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.writeTypedContent(AbstractServlet.java:296)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.sendResponse(RestServlet.java:251)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.RestServlet.doGet(RestServlet.java:119)
> at
> org.apache.qpid.server.management.plugin.servlet.rest.AbstractServlet.doGet(AbstractServlet.java:128)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8348) [Broker-J] Add ability to reload keystore/truststore
[ https://issues.apache.org/jira/browse/QPID-8348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895125#comment-16895125 ] ASF subversion and git services commented on QPID-8348: --- Commit 73c7dca003e625823ae9248212d74fb0b003293a in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=73c7dca ] QPID-8348: [Broker-J] Add ability to reload keystore/truststore (cherry picked from commit ca6626ee2a5f317ed0426b2219236364b859969f) > [Broker-J] Add ability to reload keystore/truststore > > > Key: QPID-8348 > URL: https://issues.apache.org/jira/browse/QPID-8348 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Priority: Major > Labels: keystore, truststore > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.5 > > > Currently there is no way to reload already loaded keystore or truststore. It > should be possible to reload keystore on configured path of > keystore/truststore by REST API (Access Control Provider has similar > functionality). -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8343) [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations for lifetime policies "delete-on-close", "delete-on-no-links", "delete-on-no-messages" or "de
[
https://issues.apache.org/jira/browse/QPID-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895124#comment-16895124
]
ASF subversion and git services commented on QPID-8343:
---
Commit 656edb576f20f6d983b611b9f8d6024bbb8c8ea4 in qpid-broker-j's branch
refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=656edb5 ]
QPID-8343: [Broker-J][AMQP 1.0] Derive dynamic node durability from terminus
expiry policy
(cherry picked from commit bf75f490170beb91f72547c00c365bf024cbaa1f)
> [Broker-J][AMQP 1.0] Broker mistakenly creates durable dynamic destinations
> for lifetime policies "delete-on-close", "delete-on-no-links",
> "delete-on-no-messages" or "delete-on-no-links-or-messages"
> --
>
> Key: QPID-8343
> URL: https://issues.apache.org/jira/browse/QPID-8343
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> When {{source}} or {{target}} of incoming {{attach}} has property {{dynamic}}
> set to true and property {{dynamic-node-properties}} contains entry
> {{lifetime-policy}} with value set to either {{delete-on-close}} or
> {{delete-on-no-links}} or {{delete-on-no-messages}} or
> {{delete-on-no-links-or-messages}}, the broker creates a durable temporary
> queue.
> The node expiry policy is not set. Thus, default {{session-end}} should be
> used. Durability is not set either.
> Such temporary queues should be non-durable.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8345) [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue when receiver’s desired snd-settle-mode is set to settled and transactions are not used for
[
https://issues.apache.org/jira/browse/QPID-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895122#comment-16895122
]
ASF subversion and git services commented on QPID-8345:
---
Commit 9b67c9a1a465d722443c6ad272b6c1b3528f29d7 in qpid-broker-j's branch
refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=9b67c9a ]
QPID-8345: [Broker-J][AMQP 1.0] Dequeue messages sent non-transactionally as
pre-settled
(cherry picked from commit ca0d0d7ec22c31364c1adc32f5dffee0392ff230)
> [Broker-J][AMQP 1.0] Consumed messages are left in acquired state on a queue
> when receiver’s desired snd-settle-mode is set to settled and transactions
> are not used for message receiving
> --
>
> Key: QPID-8345
> URL: https://issues.apache.org/jira/browse/QPID-8345
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
>Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1,
> qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5,
> qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1,
> qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3,
> qpid-java-broker-7.1.4
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-7.1.5
>
>
> When receiving link desired {{snd-settle-mode}} is set to {{settled}} and
> transactions are not used for message receiving, the broker sending link
> sends the messages pre-settled.
> However, the consumed messages are left in acquired state on the queue after
> sending them to consumer. Such messages stack in {{acquired}} state until
> broker is restarted. After the restart, the persistent message became
> available for consumption again.
> The broker should remove sent pre-settled messages from the queue queue. If
> consumer default outcome is set explicitly to other value than {{accepted}}
> or null, than the transfer state should be set to {{accepted}} in order to
> notify the receiver about sender behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
