[jira] [Commented] (DISPATCH-847) Fix issues discovered by Coverity

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

[jira] [Commented] (DISPATCH-847) Fix issues discovered by Coverity

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

[jira] [Resolved] (DISPATCH-801) Stand-alone version of the console does not open at all when running offline

[ https://issues.apache.org/jira/browse/DISPATCH-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-801. --- Resolution: Fixed > Stand-alone version of the console does not open at all when running

[jira] [Resolved] (DISPATCH-834) Create config tool to create/read/update/delete router config files

[ https://issues.apache.org/jira/browse/DISPATCH-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-834. --- Resolution: Fixed Fix Version/s: 1.1.0 > Create config tool to

[jira] [Updated] (QPID-7934) [Java Broker] [ACL] A recovered RuleBasedVirtualHostAccessControlProvider doesn't tell the virtualhost about updates to its rule-state

[ https://issues.apache.org/jira/browse/QPID-7934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7934: - Summary: [Java Broker] [ACL] A recovered RuleBasedVirtualHostAccessControlProvider doesn't tell the

[jira] [Created] (DISPATCH-875) Document address and link route wildcards

Ben Hardesty created DISPATCH-875: - Summary: Document address and link route wildcards Key: DISPATCH-875 URL: https://issues.apache.org/jira/browse/DISPATCH-875 Project: Qpid Dispatch Issue

[jira] [Commented] (QPID-8018) [Java Client, AMQP 0-x] Clarify error message when connection times out

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

[jira] [Commented] (QPID-8034) [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

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

[jira] [Resolved] (DISPATCH-590) List of log modules on the overview page is occationally doubled

[ https://issues.apache.org/jira/browse/DISPATCH-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-590. --- Resolution: Fixed Fix Version/s: 1.1.0 > List of log modules on the overview page is

[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=16249770#comment-16249770 ] Keith Wall commented on QPID-8017: -- The existence of both Broker and VirtualHostInclusionRules make

[jira] [Commented] (QPID-7905) [Java Client AMQP 0-x] Connection#start is not thread-safe

[ https://issues.apache.org/jira/browse/QPID-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249766#comment-16249766 ] Alex Rudyy commented on QPID-7905: -- Whilst looking into the potential fix for the reported problem, the

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-8017: - Fix Version/s: Future > [Broker-J] [BDB] JE log events written at JUL level FINE and below not >

[jira] [Commented] (QPID-8034) [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

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

[jira] [Updated] (QPID-8034) [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

[ https://issues.apache.org/jira/browse/QPID-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8034: - Status: Reviewable (was: In Progress) > [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

[jira] [Assigned] (QPID-8034) [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

[ https://issues.apache.org/jira/browse/QPID-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8034: Assignee: Keith Wall > [Qpid JMS AMQP 0-x] Update bundling to follow project conventions >

[jira] [Created] (QPID-8034) [Qpid JMS AMQP 0-x] Update bundling to follow project conventions

Keith Wall created QPID-8034: Summary: [Qpid JMS AMQP 0-x] Update bundling to follow project conventions Key: QPID-8034 URL: https://issues.apache.org/jira/browse/QPID-8034 Project: Qpid Issue

[jira] [Resolved] (QPID-8020) [Broker-J] Rename binary and source distribution bundles for broker-j

[ https://issues.apache.org/jira/browse/QPID-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8020. -- Resolution: Fixed > [Broker-J] Rename binary and source distribution bundles for broker-j >

[jira] [Updated] (QPID-8020) [Broker-J] Rename binary and source distribution bundles for broker-j

[ https://issues.apache.org/jira/browse/QPID-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8020: - Issue Type: Improvement (was: Bug) > [Broker-J] Rename binary and source distribution bundles for

[jira] [Updated] (QPID-8020) [Broker-J] Rename binary and source distribution bundles for broker-j

[ https://issues.apache.org/jira/browse/QPID-8020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8020: - Fix Version/s: qpid-java-broker-7.0.0 > [Broker-J] Rename binary and source distribution bundles for

[jira] [Resolved] (QPID-7779) [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not supported

[ https://issues.apache.org/jira/browse/QPID-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7779. -- Resolution: Fixed I reviewed the committed changes. The changes in code look good to me. I made an

[jira] [Commented] (QPID-7779) [Qpid JMS Client 0-x] [0-8..0-91] sasl_mechs and other SASL connection options not supported

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

[jira] [Updated] (QPID-8033) [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown from ConnectionStartMethoHandler due to unsupported sasl mechanisms

[ https://issues.apache.org/jira/browse/QPID-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8033: - Description: {{AMQTimeoutException}} is reported after waiting for "maximum state wait time", when

[jira] [Updated] (QPID-8033) [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown from ConnectionStartMethoHandler due to unsupported sasl mechanisms

[ https://issues.apache.org/jira/browse/QPID-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8033: - Description: {{AMQTimeoutException}} is reported after waiting for "maximum state wait time", when

[jira] [Updated] (QPID-8033) [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown from ConnectionStartMethoHandler due to unsupported sasl mechanisms

[ https://issues.apache.org/jira/browse/QPID-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8033: - Summary: [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown from

[jira] [Updated] (QPID-8033) [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown by the client (for example, due to unsupported sasl mechanisms)

[ https://issues.apache.org/jira/browse/QPID-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8033: - Component/s: (was: Java Broker) Java Client > [Qpid JMS AMQP 0-x] An establishment of

[jira] [Updated] (QPID-8033) [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown by the client (for example, due to unsupported sasl mechanisms)

[ https://issues.apache.org/jira/browse/QPID-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8033: - Summary: [Qpid JMS AMQP 0-x] An establishment of connection times out if an exception is thrown by the

[jira] [Created] (QPID-8033) [Qpid JMS Client for AMQP 0-x] An establishment of connection times out if an exception is thrown by the client due to invalid configuration settings, etc

Alex Rudyy created QPID-8033: Summary: [Qpid JMS Client for AMQP 0-x] An establishment of connection times out if an exception is thrown by the client due to invalid configuration settings, etc Key: QPID-8033 URL:

[jira] [Commented] (QPID-7964) [Java Client, AMQP 0-x] SCRAM SASL implementation incorrectly encodes "=" and "," for passwords

[ https://issues.apache.org/jira/browse/QPID-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16249557#comment-16249557 ] Keith Wall commented on QPID-7964: -- Change and new tests looks good. > [Java Client, AMQP 0-x] SCRAM

[jira] [Resolved] (QPID-7964) [Java Client, AMQP 0-x] SCRAM SASL implementation incorrectly encodes "=" and "," for passwords

[ https://issues.apache.org/jira/browse/QPID-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7964. -- Resolution: Fixed > [Java Client, AMQP 0-x] SCRAM SASL implementation incorrectly encodes "=" and > ","

[jira] [Resolved] (QPID-7899) [Java 0-8...0-9-1 Client] Message#setJMSCorrelationIDAsBytes() erroneously converts the bytes to string

[ https://issues.apache.org/jira/browse/QPID-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7899. -- Resolution: Fixed Changes look reasonable to me > [Java 0-8...0-9-1 Client]

[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=16249542#comment-16249542 ] ASF subversion and git services commented on QPID-6933: --- Commit

[jira] [Commented] (DISPATCH-590) List of log modules on the overview page is occationally doubled

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

[jira] [Resolved] (QPID-7897) [Java 0-8...0-9-1 Client] Message#getJMSCorrelationIDAsBytes() erroneously first converts to string before retreiving bytes

[ https://issues.apache.org/jira/browse/QPID-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7897. -- Resolution: Fixed The changes look reasonable to me > [Java 0-8...0-9-1 Client]

[jira] [Comment Edited] (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=16249418#comment-16249418 ] Alex Rudyy edited comment on QPID-8017 at 11/13/17 11:28 AM: - Keith's idea

[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=16249418#comment-16249418 ] Alex Rudyy commented on QPID-8017: -- Keith's idea about propagation of log level configuration into JUL

[jira] [Resolved] (QPID-8021) [Broker-J] [BDB] Make BDB store module compatible with JE release 7.4.5 [6.1.x]

[ https://issues.apache.org/jira/browse/QPID-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8021. -- Resolution: Fixed I reviewed the changes and made an additional commit to set helper hosts consistently

[jira] [Commented] (QPID-8021) [Broker-J] [BDB] Make BDB store module compatible with JE release 7.4.5 [6.1.x]

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

[jira] [Resolved] (QPID-7853) Message enqueued twice to the same queue leads to Broker failure

[ https://issues.apache.org/jira/browse/QPID-7853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7853. -- Resolution: Fixed The change looks good to me > Message enqueued twice to the same queue leads to

[jira] [Created] (QPID-8032) [AMQP1.0] AsyncAutoCommitTransaction optimisation

Keith Wall created QPID-8032: Summary: [AMQP1.0] AsyncAutoCommitTransaction optimisation Key: QPID-8032 URL: https://issues.apache.org/jira/browse/QPID-8032 Project: Qpid Issue Type: Improvement