[jira] [Updated] (PROTON-1745) [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon

[ https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1745: Fix Version/s: proton-c-0.20.0 > [proton-c, regression] PN_CONNECTION_BOUND event is emitted too

[jira] [Commented] (PROTON-1745) [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon

[ https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329877#comment-16329877 ] Cliff Jansen commented on PROTON-1745: -- Try the attached patch and see if that works.  If so, we

[jira] [Updated] (PROTON-1745) [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon

[ https://issues.apache.org/jira/browse/PROTON-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen updated PROTON-1745: - Attachment: p1745_0.diff > [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon

[jira] [Commented] (QPID-8074) [Qpid JMS AMQP 0-x] Build framework to run JMS client system tests

[ https://issues.apache.org/jira/browse/QPID-8074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329559#comment-16329559 ] ASF subversion and git services commented on QPID-8074: --- Commit

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329552#comment-16329552 ] ASF subversion and git services commented on QPID-6933: --- Commit

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329548#comment-16329548 ] ASF subversion and git services commented on QPID-6933: --- Commit

[jira] [Commented] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329430#comment-16329430 ] Alex Rudyy commented on QPID-8062: -- Attached a patch changing {{ReceivingDestination}} to throw

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8062: - Attachment: 0001-QPID-8062-Broker-J-AMQP-1.0-Move-responsibility-to-c.patch > [Broker-J][AMQP 1.0] Fix

[jira] [Commented] (PROTON-1746) Add ability to build both Python 2.x and Python 3.x bindings in a single build

[ https://issues.apache.org/jira/browse/PROTON-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329300#comment-16329300 ] Kim van der Riet commented on PROTON-1746: -- Currently the bindings install in

[jira] [Created] (PROTON-1746) Add ability to build both Python 2.x and Python 3.x bindings in a single build

Kim van der Riet created PROTON-1746: Summary: Add ability to build both Python 2.x and Python 3.x bindings in a single build Key: PROTON-1746 URL: https://issues.apache.org/jira/browse/PROTON-1746

[jira] [Created] (PROTON-1745) [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon

Chuck Rolke created PROTON-1745: --- Summary: [proton-c, regression] PN_CONNECTION_BOUND event is emitted too soon Key: PROTON-1745 URL: https://issues.apache.org/jira/browse/PROTON-1745 Project: Qpid

[jira] [Commented] (PROTON-1700) [cpp] Reconnecting container does not respond to stop

[ https://issues.apache.org/jira/browse/PROTON-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329183#comment-16329183 ] ASF subversion and git services commented on PROTON-1700: - Commit

[jira] [Commented] (QPIDIT-109) Add ability to run Proton Python shims under Python 3

[ https://issues.apache.org/jira/browse/QPIDIT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329187#comment-16329187 ] ASF subversion and git services commented on QPIDIT-109: Commit

[jira] [Updated] (QPIDIT-109) Add ability to run Proton Python shims under Python 3

[ https://issues.apache.org/jira/browse/QPIDIT-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-109: Issue Type: Improvement (was: Bug) > Add ability to run Proton Python shims under Python 3

[jira] [Updated] (QPIDJMS-357) add support for acknowledging individual messages

[ https://issues.apache.org/jira/browse/QPIDJMS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-357: --- Description: The "client acknowledgement" session acknowledgement mode allows for messages

[jira] [Commented] (QPIDJMS-357) add support for acknowledging individual messages

[ https://issues.apache.org/jira/browse/QPIDJMS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329173#comment-16329173 ] ASF subversion and git services commented on QPIDJMS-357: - Commit

[jira] [Created] (QPIDJMS-357) add support for acknowledging individual messages

Robbie Gemmell created QPIDJMS-357: -- Summary: add support for acknowledging individual messages Key: QPIDJMS-357 URL: https://issues.apache.org/jira/browse/QPIDJMS-357 Project: Qpid JMS

[jira] [Resolved] (QPIDJMS-355) Use the new Proton-J SaslListener API to simplify the sasl code

[ https://issues.apache.org/jira/browse/QPIDJMS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-355. -- Resolution: Fixed > Use the new Proton-J SaslListener API to simplify the sasl code >

[jira] [Commented] (QPIDJMS-356) Add support for a new session mode to make all consumers presettled

[ https://issues.apache.org/jira/browse/QPIDJMS-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16329130#comment-16329130 ] ASF subversion and git services commented on QPIDJMS-356: - Commit

[jira] [Created] (QPIDJMS-356) Add support for a new session mode to make all consumers presettled

Timothy Bish created QPIDJMS-356: Summary: Add support for a new session mode to make all consumers presettled Key: QPIDJMS-356 URL: https://issues.apache.org/jira/browse/QPIDJMS-356 Project: Qpid

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8062: - Description: As per section "2.2.2 Routing Errors" of "Using the Anonymous Terminus for Message Routing

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received message

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8062: - Summary: [Broker-J][AMQP 1.0] Fix handling of routing errors when target destination cannot route received

[jira] [Assigned] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional c

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8062: Assignee: Keith Wall (was: Alex Rudyy) > [Broker-J][AMQP 1.0] When a pre-settled message published

[jira] [Assigned] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional c

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8062: Assignee: Alex Rudyy (was: Keith Wall) > [Broker-J][AMQP 1.0] When a pre-settled message published

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional ca

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8062: - Status: Reviewable (was: In Progress) > [Broker-J][AMQP 1.0] When a pre-settled message published over

[jira] [Assigned] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional c

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8062: Assignee: Keith Wall > [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous >

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional ca

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8062: - Affects Version/s: qpid-java-broker-7.0.0 > [Broker-J][AMQP 1.0] When a pre-settled message published over

[jira] [Updated] (QPID-8062) [Broker-J][AMQP 1.0] When a pre-settled message published over "anonymous relay" is rejected by the destination, the Broker should detach the link for non-transactional ca

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8062: - Fix Version/s: qpid-java-broker-7.0.1 > [Broker-J][AMQP 1.0] When a pre-settled message published over

[jira] [Resolved] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8046. -- Resolution: Fixed > [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial >

[jira] [Commented] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger

[ https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328834#comment-16328834 ] Keith Wall commented on QPID-8017: -- Merged to 7.0.x branch. > [Broker-J] [BDB] JE log events written at

[jira] [Commented] (QPID-8017) [Broker-J] [BDB] JE log events written at JUL level FINE and below not included in the log produced by a BrokerLogger

[ https://issues.apache.org/jira/browse/QPID-8017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328833#comment-16328833 ] ASF subversion and git services commented on QPID-8017: --- Commit

[jira] [Comment Edited] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall edited comment on QPID-8080 at 1/17/18 1:58 PM: --- This problem will

[jira] [Comment Edited] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall edited comment on QPID-8080 at 1/17/18 1:58 PM: --- This problem will

[jira] [Commented] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328794#comment-16328794 ] Keith Wall commented on QPID-8080: -- This problem will manifest in a number of places: recovery dequeuing a

[jira] [Updated] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8080: - Description: Broker-J can crash when JDBC message store is configured with a connection pool NONE and a

[jira] [Updated] (QPID-8080) [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit

[ https://issues.apache.org/jira/browse/QPID-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8080: - Description: Broker-J can crash when JDBC message store is configured with a connection pool NONE and a

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328665#comment-16328665 ] ASF subversion and git services commented on QPID-8046: --- Commit

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328666#comment-16328666 ] ASF subversion and git services commented on QPID-8046: --- Commit

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328667#comment-16328667 ] ASF subversion and git services commented on QPID-8046: --- Commit

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328668#comment-16328668 ] Keith Wall commented on QPID-8046: -- Changes looked reasonable to me, ported to 7.0.x, > [Broker-J] Allow

[jira] [Commented] (QPID-8046) [Broker-J] Allow SASL mechanisms PLAIN and XOAUTH2 to not require initial response

[ https://issues.apache.org/jira/browse/QPID-8046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328644#comment-16328644 ] ASF subversion and git services commented on QPID-8046: --- Commit

[jira] [Resolved] (QPID-8061) [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing alternate binding crashes the Broker

[ https://issues.apache.org/jira/browse/QPID-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8061. -- Resolution: Fixed > [Broker-J] [AMQP 0-8..0-9-1] Declaring exchange with not existing alternate >

[jira] [Commented] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328617#comment-16328617 ] ASF subversion and git services commented on QPID-8025: --- Commit

[jira] [Resolved] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8025. -- Resolution: Fixed > [Java Broker] Improve detach error message on unsubscribing from JMS shared > subs

[jira] [Commented] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328555#comment-16328555 ] Keith Wall commented on QPID-8025: -- Change looks reasonable to me. > [Java Broker] Improve detach error

[jira] [Updated] (QPID-8025) [Java Broker] Improve detach error message on unsubscribing from JMS shared subs

[ https://issues.apache.org/jira/browse/QPID-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8025: - Priority: Minor (was: Major) > [Java Broker] Improve detach error message on unsubscribing from JMS

[jira] [Resolved] (QPID-8076) [0-91] [Publisher Confirms] basic.ack returned to client before message is sync'd to disk

[ https://issues.apache.org/jira/browse/QPID-8076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8076. -- Resolution: Fixed Changes look reasonable for me > [0-91] [Publisher Confirms] basic.ack returned to

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328529#comment-16328529 ] ASF subversion and git services commented on QPID-6933: --- Commit

[jira] [Commented] (QPID-6933) Factor out a JMS client neutral messaging test suite from system tests

[ https://issues.apache.org/jira/browse/QPID-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328440#comment-16328440 ] ASF subversion and git services commented on QPID-6933: --- Commit