[jira] [Commented] (QPIDIT-62) Add AMQP.Net Lite client shims

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

[jira] [Commented] (DISPATCH-209) Three+ router test is needed in the system test suite.

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

[GitHub] qpid-dispatch pull request #134: DISPATCH-209 : dynamic request response tes...

GitHub user mgoulish opened a pull request: https://github.com/apache/qpid-dispatch/pull/134 DISPATCH-209 : dynamic request response test phew. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mgoulish/qpid-dispatch DISPATCH-209-H

[jira] [Resolved] (PROTON-1378) Two reactor final events generated

[ https://issues.apache.org/jira/browse/PROTON-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen resolved PROTON-1378. -- Resolution: Fixed > Two reactor final events generated > -- >

[jira] [Updated] (PROTON-766) Proton-c Windows IO prints misleading error messages

[ https://issues.apache.org/jira/browse/PROTON-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-766: --- Fix Version/s: (was: 0.17.0) 0.18.0 > Proton-c Windows IO prints misleading

[jira] [Updated] (PROTON-840) Fix Windows components to use transport logging

[ https://issues.apache.org/jira/browse/PROTON-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-840: --- Fix Version/s: (was: 0.17.0) 0.18.0 > Fix Windows components to use transport

[GitHub] qpid-dispatch issue #133: Dispatch 209 d

Github user mgoulish commented on the issue: https://github.com/apache/qpid-dispatch/pull/133 wtf --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[GitHub] qpid-dispatch pull request #133: Dispatch 209 d

Github user mgoulish closed the pull request at: https://github.com/apache/qpid-dispatch/pull/133 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] qpid-dispatch pull request #133: Dispatch 209 d

GitHub user mgoulish opened a pull request: https://github.com/apache/qpid-dispatch/pull/133 Dispatch 209 d dynamic request-response test You can merge this pull request into a Git repository by running: $ git pull https://github.com/mgoulish/qpid-dispatch DISPATCH-209-D

[jira] [Commented] (PROTON-1378) Two reactor final events generated

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

[jira] [Created] (PROTON-1378) Two reactor final events generated

Cliff Jansen created PROTON-1378: Summary: Two reactor final events generated Key: PROTON-1378 URL: https://issues.apache.org/jira/browse/PROTON-1378 Project: Qpid Proton Issue Type: Bug

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

On 20 December 2016 at 18:34, Gordon Sim wrote: > On 20/12/16 18:20, Keith W wrote: >> >> On 20 December 2016 at 10:14, Gordon Sim wrote: >>> >>> On 19/12/16 15:57, Keith W wrote: By debugging the Java Broker's translation module, I can see that

[jira] [Commented] (QPIDJMS-239) Client ack session occasionally seen to redeliver recovered messages out of order

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

[jira] [Commented] (QPID-7558) [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the same database

[ https://issues.apache.org/jira/browse/QPID-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15767381#comment-15767381 ] Lorenz Quack commented on QPID-7558: Should we provide similar functionality for BDB? > [Java Broker]

[jira] [Updated] (QPID-7576) Metadata loaded twice for recovered message

[ https://issues.apache.org/jira/browse/QPID-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7576: --- Assignee: (was: Lorenz Quack) > Metadata loaded twice for recovered message >

[jira] [Assigned] (QPID-7576) Metadata loaded twice for recovered message

[ https://issues.apache.org/jira/browse/QPID-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack reassigned QPID-7576: -- Assignee: Lorenz Quack > Metadata loaded twice for recovered message >

[jira] [Updated] (QPID-7576) Metadata loaded twice for recovered message

[ https://issues.apache.org/jira/browse/QPID-7576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7576: --- Status: Reviewable (was: In Progress) > Metadata loaded twice for recovered message >

[jira] [Commented] (QPID-7576) Metadata loaded twice for recovered message

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

[jira] [Updated] (QPID-7558) [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the same database

[ https://issues.apache.org/jira/browse/QPID-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-7558: --- Attachment: 0001-QPID-7558-Java-Broker-whitelist-validValuePattern-fo.patch patch to add whitelisting

[GitHub] qpid-dispatch pull request #132: DISPATCH-557 - Moved management of connecti...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/132 DISPATCH-557 - Moved management of connections from python agent to r… …outer core You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

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

[jira] [Resolved] (PROTON-1376) [C, windows] Release 0.16 build fail - src/protocol.h clobbered

[ https://issues.apache.org/jira/browse/PROTON-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved PROTON-1376. - Resolution: Fixed Fix Version/s: 0.17.0 Fixed at Commit 9377d85 > [C, windows] Release

[jira] [Resolved] (QPID-7595) [C++ Windows] CMake required version is too low for installation

[ https://issues.apache.org/jira/browse/QPID-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved QPID-7595. --- Resolution: Fixed Fix Version/s: qpid-cpp-1.36.0 qpid-cpp-1.35.1 Fixed at

[jira] [Commented] (DISPATCH-557) High connection rates cause problems in the Python management agent

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

[GitHub] qpid-dispatch pull request #128: DISPATCH-557 - Moved management of connecti...

Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/128 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Resolved] (DISPATCH-598) Router crash when calling sender and session close methods in onLinkFLow()

[ https://issues.apache.org/jira/browse/DISPATCH-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-598. --- Resolution: Fixed > Router crash when calling sender and session close methods in onLinkFLow() >

[jira] [Commented] (DISPATCH-598) Router crash when calling sender and session close methods in onLinkFLow()

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

[GitHub] qpid-dispatch pull request #131: DISPATCH-598 - Added code to temporarily fi...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/131 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (DISPATCH-598) Router crash when calling sender and session close methods in onLinkFLow()

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

[jira] [Updated] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7592: - Affects Version/s: qpid-java-6.0 > [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS

[jira] [Updated] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7592: - Affects Version/s: qpid-java-6.0.6 qpid-java-6.1.1

[jira] [Updated] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7592: - Status: Reviewable (was: In Progress) > [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived

[jira] [Commented] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766699#comment-15766699 ] Keith Wall commented on QPID-7592: -- Rob and I paired on this change. > [AMQP1.0] leak from

[jira] [Resolved] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7592. -- Resolution: Fixed > [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS > auto-ack

[jira] [Assigned] (QPID-7592) [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS auto-ack consuming session.

[ https://issues.apache.org/jira/browse/QPID-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7592: Assignee: Keith Wall > [AMQP1.0] leak from Session_1_0#_outgoingUnsettled for long lived JMS >

[jira] [Updated] (QPID-7593) Ending an AMQP1.0 connection with consumer leaks the connection, session and objects related to the consumer

[ https://issues.apache.org/jira/browse/QPID-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7593: - Status: Reviewable (was: In Progress) > Ending an AMQP1.0 connection with consumer leaks the connection,

[jira] [Assigned] (QPID-7593) Ending an AMQP1.0 connection with consumer leaks the connection, session and objects related to the consumer

[ https://issues.apache.org/jira/browse/QPID-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7593: Assignee: Keith Wall > Ending an AMQP1.0 connection with consumer leaks the connection, session and

[jira] [Commented] (QPID-7593) Ending an AMQP1.0 connection with consumer leaks the connection, session and objects related to the consumer

[ https://issues.apache.org/jira/browse/QPID-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766697#comment-15766697 ] Keith Wall commented on QPID-7593: -- In the fix above, we opted to prevent the removed QueueConsumerNode

[jira] [Updated] (QPID-7593) Ending an AMQP1.0 connection with consumer leaks the connection, session and objects related to the consumer

[ https://issues.apache.org/jira/browse/QPID-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7593: - Summary: Ending an AMQP1.0 connection with consumer leaks the connection, session and objects related to