[jira] [Commented] (DISPATCH-89) Model the legacy topic exchange behavior of qpidd

[ https://issues.apache.org/jira/browse/DISPATCH-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327905#comment-16327905 ] ASF GitHub Bot commented on DISPATCH-89: Github user kgiusti commented on a diff in the pull

[GitHub] qpid-dispatch pull request #244: DISPATCH-89: Exchange Binding forwarder (ex...

Github user kgiusti commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/244#discussion_r161905217 --- Diff: tests/system_tests_exchange_bindings.py --- @@ -0,0 +1,676 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one

[GitHub] qpid-dispatch pull request #244: DISPATCH-89: Exchange Binding forwarder (ex...

Github user kgiusti commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/244#discussion_r161904967 --- Diff: src/router_core/exchange_bindings.c --- @@ -0,0 +1,1336 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one +

[jira] [Updated] (DISPATCH-915) connection rhost not calculated soon enough

[ https://issues.apache.org/jira/browse/DISPATCH-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated DISPATCH-915: - Summary: connection rhost not calculated soon enough (was: connectoin rhost not calculated

[jira] [Created] (DISPATCH-915) connectoin rhost not calculated soon enough

Chuck Rolke created DISPATCH-915: Summary: connectoin rhost not calculated soon enough Key: DISPATCH-915 URL: https://issues.apache.org/jira/browse/DISPATCH-915 Project: Qpid Dispatch Issue

[jira] [Commented] (DISPATCH-89) Model the legacy topic exchange behavior of qpidd

[ https://issues.apache.org/jira/browse/DISPATCH-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327872#comment-16327872 ] ASF GitHub Bot commented on DISPATCH-89: Github user ganeshmurthy commented on a diff in the pull

[GitHub] qpid-dispatch pull request #244: DISPATCH-89: Exchange Binding forwarder (ex...

Github user ganeshmurthy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/244#discussion_r161897073 --- Diff: tests/system_tests_exchange_bindings.py --- @@ -0,0 +1,676 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one

[GitHub] qpid-dispatch pull request #244: DISPATCH-89: Exchange Binding forwarder (ex...

Github user ganeshmurthy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/244#discussion_r161883427 --- Diff: src/router_core/exchange_bindings.c --- @@ -0,0 +1,1336 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one

[jira] [Created] (PROTON-1744) bug in c-proactor-tests

Cliff Jansen created PROTON-1744: Summary: bug in c-proactor-tests Key: PROTON-1744 URL: https://issues.apache.org/jira/browse/PROTON-1744 Project: Qpid Proton Issue Type: Bug

[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327584#comment-16327584 ] Ganesh Murthy commented on DISPATCH-878: If you want to have two listeners on port: 0, give

[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327578#comment-16327578 ] ASF GitHub Bot commented on DISPATCH-878: - GitHub user ganeshmurthy opened a pull request:

[GitHub] qpid-dispatch pull request #245: DISPATCH-878 - Added code to display the ac...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/245 DISPATCH-878 - Added code to display the actual listening port if 0(z… …ero) is set as the listening port You can merge this pull request into a Git repository by running: $

[jira] [Resolved] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8079. -- Resolution: Fixed Changes look good to me > [Broker-J] If the future associated with an AsyncCommand

[jira] [Commented] (DISPATCH-89) Model the legacy topic exchange behavior of qpidd

[ https://issues.apache.org/jira/browse/DISPATCH-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327500#comment-16327500 ] ASF GitHub Bot commented on DISPATCH-89: GitHub user kgiusti opened a pull request:

[GitHub] qpid-dispatch pull request #244: DISPATCH-89: Exchange Binding forwarder (ex...

GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/244 DISPATCH-89: Exchange Binding forwarder (experimental) Adds a forwarder that models the pre AMQP 1.0 model of exchanges and bindings. Exchanges can be added via management and bound to

[jira] [Assigned] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-878: -- Assignee: Ganesh Murthy > qdrouterd should log real port if port 0 was specified for

[jira] [Resolved] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8070. -- Resolution: Fixed > Qpid java broker is unable to reconnect to database after kill -9 then restart >

[jira] [Commented] (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

[ https://issues.apache.org/jira/browse/QPID-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327450#comment-16327450 ] Alex Rudyy commented on QPID-8062: -- Here is the link to a discussion preceding raising of the issue

[jira] [Assigned] (DISPATCH-911) New management call to return overall router network statistics

[ https://issues.apache.org/jira/browse/DISPATCH-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-911: -- Assignee: Ganesh Murthy > New management call to return overall router network

[jira] [Assigned] (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 reassigned QPIDIT-109: --- Assignee: Kim van der Riet > Add ability to run Proton Python shims under Python 3 >

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

Kim van der Riet created QPIDIT-109: --- Summary: Add ability to run Proton Python shims under Python 3 Key: QPIDIT-109 URL: https://issues.apache.org/jira/browse/QPIDIT-109 Project: Apache QPID

[jira] [Resolved] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

[ https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPIDIT-65. Resolution: Fixed Resolved. > Add command-line controls to JMS_hdrs_props_test to control

[jira] [Commented] (QPIDIT-65) Add command-line controls to JMS_hdrs_props_test to control test more precisely

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

[jira] [Commented] (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:comment-tabpanel=16327315#comment-16327315 ] ASF subversion and git services commented on QPIDJMS-355: - Commit

[jira] [Resolved] (DISPATCH-914) qd_connector_t leaks mutexes

[ https://issues.apache.org/jira/browse/DISPATCH-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-914. - Resolution: Fixed > qd_connector_t leaks mutexes > > >

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

Timothy Bish created QPIDJMS-355: Summary: Use the new Proton-J SaslListener API to simplify the sasl code Key: QPIDJMS-355 URL: https://issues.apache.org/jira/browse/QPIDJMS-355 Project: Qpid JMS

[jira] [Resolved] (QPID-8071) Java Qpid library does not report that session was closed

[ https://issues.apache.org/jira/browse/QPID-8071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8071. -- Resolution: Won't Fix Development of the Qpid JMS AMQP 0-x client is ceased.  As discussed please use

[jira] [Commented] (DISPATCH-914) qd_connector_t leaks mutexes

[ https://issues.apache.org/jira/browse/DISPATCH-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327276#comment-16327276 ] ASF GitHub Bot commented on DISPATCH-914: - Github user asfgit closed the pull request at:

[jira] [Commented] (DISPATCH-914) qd_connector_t leaks mutexes

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

[GitHub] qpid-dispatch pull request #243: DISPATCH-914: correctly free mutex from qd_...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/243 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (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 ] Keith Wall updated QPID-8076: - Status: Reviewable (was: In Progress) > [0-91] [Publisher Confirms] basic.ack returned to client before

[jira] [Updated] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8070: - Affects Version/s: qpid-java-6.1.5 > Qpid java broker is unable to reconnect to database after kill -9

[jira] [Updated] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8070: - Fix Version/s: (was: qpid-java-6.1.5) qpid-python-1.35.0

[jira] [Updated] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8070: - Fix Version/s: (was: qpid-python-1.35.0) > Qpid java broker is unable to reconnect to database after

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327266#comment-16327266 ] Keith Wall commented on QPID-8070: -- Changes looked reasonable to me.  Port to 7.0.x and 6.1.x branches

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

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

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

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

[jira] [Commented] (DISPATCH-914) qd_connector_t leaks mutexes

[ https://issues.apache.org/jira/browse/DISPATCH-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327247#comment-16327247 ] ASF GitHub Bot commented on DISPATCH-914: - GitHub user kgiusti opened a pull request:

[GitHub] qpid-dispatch pull request #243: DISPATCH-914: correctly free mutex from qd_...

GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/243 DISPATCH-914: correctly free mutex from qd_connector_t You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-914

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

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

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

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

[jira] [Commented] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

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

[jira] [Created] (DISPATCH-914) qd_connector_t leaks mutexes

Ken Giusti created DISPATCH-914: --- Summary: qd_connector_t leaks mutexes Key: DISPATCH-914 URL: https://issues.apache.org/jira/browse/DISPATCH-914 Project: Qpid Dispatch Issue Type: Bug

[jira] [Updated] (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 ] Keith Wall updated QPID-8076: - Fix Version/s: qpid-java-broker-7.0.0 > [0-91] [Publisher Confirms] basic.ack returned to client before

[jira] [Assigned] (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 ] Keith Wall reassigned QPID-8076: Assignee: Keith Wall > [0-91] [Publisher Confirms] basic.ack returned to client before message is

[jira] [Resolved] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8077. -- Resolution: Invalid > [AMQ 0-91] [Publisher Confirms] Improve validations when switching to > confirms

[jira] [Assigned] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8079: Assignee: Keith Wall > [Broker-J] If the future associated with an AsyncCommand completes >

[jira] [Updated] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8079: - Status: Reviewable (was: In Progress) > [Broker-J] If the future associated with an AsyncCommand

[jira] [Commented] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327190#comment-16327190 ] Keith Wall commented on QPID-8079: -- Given this defect does not currently cause a defect, I don't think

[jira] [Commented] (PROTON-1703) [cpp] Remove auto_settle from receiver options

[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327188#comment-16327188 ] Robbie Gemmell commented on PROTON-1703: Note that the change was made then reverted to avoid

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

[ https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8032: - Description: Some AMQP 1.0 messaging use-cases would benefit from the {{AsyncAutoCommitTransactions}}

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

[ https://issues.apache.org/jira/browse/QPID-8032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8032: - Status: Reviewable (was: In Progress) > [AMQP1.0] AsyncAutoCommitTransaction optimisation >

[jira] [Closed] (PROTON-390) Suppress or Fix the warnings openssl.c produce

[ https://issues.apache.org/jira/browse/PROTON-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-390. - Resolution: Done Fix Version/s: (was: proton-c-future) The Travis CI build on OSX

[jira] [Assigned] (DISPATCH-908) Router loses dispositions over receive link on qpid-interop-test 2-node test

[ https://issues.apache.org/jira/browse/DISPATCH-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-908: -- Assignee: Ganesh Murthy > Router loses dispositions over receive link on

[jira] [Commented] (DISPATCH-907) cannot set address phase via qdmanage tool

[ https://issues.apache.org/jira/browse/DISPATCH-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327163#comment-16327163 ] ASF GitHub Bot commented on DISPATCH-907: - Github user ganeshmurthy closed the pull request at:

[GitHub] qpid-dispatch pull request #242: DISPATCH-907 - Added code to qdmanage to ha...

Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/242 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (DISPATCH-907) cannot set address phase via qdmanage tool

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

[jira] [Closed] (DISPATCH-913) system_tests_delivery_abort failing

[ https://issues.apache.org/jira/browse/DISPATCH-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke closed DISPATCH-913. Resolution: Cannot Reproduce Tests working again with the current master branches:

[jira] [Resolved] (DISPATCH-907) cannot set address phase via qdmanage tool

[ https://issues.apache.org/jira/browse/DISPATCH-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-907. Resolution: Fixed > cannot set address phase via qdmanage tool >

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

Alex Rudyy created QPID-8080: Summary: [Broker-J] Broker can crash when JDBC message store opens to many SQL connections to the RDBMS exceeding the maximum connection limit Key: QPID-8080 URL:

[jira] [Commented] (QPID-8038) [Broker-J][System Tests] Add protocol system test suites for AMQP 0-x

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

[jira] [Commented] (QPID-7948) [Java Broker] [AMQP0-9] [Publish Confirms] Client hangs if message sent to topic within no subscribers

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

[jira] [Commented] (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:comment-tabpanel=16327104#comment-16327104 ] ASF subversion and git services commented on QPID-8076: --- Commit

[jira] [Commented] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

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

[jira] [Closed] (PROTON-803) Message codec improvements

[ https://issues.apache.org/jira/browse/PROTON-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-803. - Resolution: Duplicate Fix Version/s: (was: proton-j-future) Closing this out. Various

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

[jira] [Commented] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327055#comment-16327055 ] Keith Wall commented on QPID-8077: -- Invalid.  I see now that QPID-6164 went beyond Rabbit's capabilities

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:54 AM:

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:54 AM:

[jira] [Updated] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8079: - Priority: Minor (was: Major) > [Broker-J] If the future associated with an AsyncCommand completes >

[jira] [Comment Edited] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall edited comment on QPID-8079 at 1/16/18 11:49 AM:

[jira] [Commented] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

[ https://issues.apache.org/jira/browse/QPID-8079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327037#comment-16327037 ] Keith Wall commented on QPID-8079: -- {{ServerTransaction.EnqueueAction}} are used in three places:

[jira] [Created] (QPID-8079) [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back

Keith Wall created QPID-8079: Summary: [Broker-J] If the future associated with an AsyncCommand completes abnormally, the associated action is not rolled-back Key: QPID-8079 URL:

[jira] [Updated] (QPID-8078) error by compiling

[ https://issues.apache.org/jira/browse/QPID-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Gavrila updated QPID-8078: - Environment: linearstore option is enabled gcc 4.8.5 with c++11 flag enabled   The problem is 

[ANNOUNCE] Apache Qpid Proton-J 0.25.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Proton-J 0.25.0. Apache Qpid Proton-J is a messaging library for the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464, http://www.amqp.org). It can be used in a wide

[jira] [Created] (QPID-8078) error by compiling

Daniel Gavrila created QPID-8078: Summary: error by compiling Key: QPID-8078 URL: https://issues.apache.org/jira/browse/QPID-8078 Project: Qpid Issue Type: Bug Components: C++

[jira] [Updated] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode.

[ https://issues.apache.org/jira/browse/QPID-8077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8077: - Summary: [AMQ 0-91] [Publisher Confirms] Improve validations when switching to confirms mode. (was: [AMQ

[jira] [Created] (QPID-8077) [AMQ 0-91] [Publisher Confirms] Improve validations when switch to confirms mode.

Keith Wall created QPID-8077: Summary: [AMQ 0-91] [Publisher Confirms] Improve validations when switch to confirms mode. Key: QPID-8077 URL: https://issues.apache.org/jira/browse/QPID-8077 Project: Qpid

[jira] [Commented] (PROTON-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version

[ https://issues.apache.org/jira/browse/PROTON-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326997#comment-16326997 ] Robbie Gemmell commented on PROTON-1729: As this is about a downstream packaging effort I

[jira] [Closed] (PROTON-1729) [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version

[ https://issues.apache.org/jira/browse/PROTON-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-1729. -- > [OSX] Update MacPorts Portfile to utilize tagged 0.19.0 version >

[jira] [Updated] (PROTON-1725) [ruby] broker example does not work if run outside home directory

[ https://issues.apache.org/jira/browse/PROTON-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1725: --- Fix Version/s: proton-c-0.19.0 > [ruby] broker example does not work if run outside home

[jira] [Assigned] (PROTON-1732) [OSX] Enable swig for the Travis CI build

[ https://issues.apache.org/jira/browse/PROTON-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-1732: -- Assignee: Andrew Stitcher Fix Version/s: (was: proton-c-future)

[jira] [Updated] (PROTON-1742) there is no send example that works well with selected_recv

[ https://issues.apache.org/jira/browse/PROTON-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1742: --- Fix Version/s: (was: proton-c-0.21.0) proton-c-0.20.0

[jira] [Updated] (PROTON-1702) Fix epoll proactor listener for rearming and overflow per socket

[ https://issues.apache.org/jira/browse/PROTON-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1702: --- Fix Version/s: (was: proton-j-0.19.0) proton-c-0.19.0 Corrected

[jira] [Commented] (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:comment-tabpanel=16326952#comment-16326952 ] Keith Wall commented on QPID-8076: -- My analysis is partly duff.   The problem actually only affects the HA

[jira] [Updated] (QPID-8070) Qpid java broker is unable to reconnect to database after kill -9 then restart

[ https://issues.apache.org/jira/browse/QPID-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8070: - Status: Reviewable (was: In Progress) > Qpid java broker is unable to reconnect to database after kill -9