[jira] [Commented] (DISPATCH-179) Refactor Router Core

[ https://issues.apache.org/jira/browse/DISPATCH-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002736#comment-15002736 ] ASF subversion and git services commented on DISPATCH-179: -- Com

[jira] [Commented] (DISPATCH-179) Refactor Router Core

[ https://issues.apache.org/jira/browse/DISPATCH-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002596#comment-15002596 ] ASF GitHub Bot commented on DISPATCH-179: - Github user asfgit closed the pull re

[jira] [Commented] (DISPATCH-179) Refactor Router Core

[ https://issues.apache.org/jira/browse/DISPATCH-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002595#comment-15002595 ] ASF subversion and git services commented on DISPATCH-179: -- Com

[GitHub] qpid-dispatch pull request: DISPATCH-179 - Added code to display l...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/32 --- 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 i

[GitHub] qpid-dispatch pull request: DISPATCH-179 - Added code to display l...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/32 DISPATCH-179 - Added code to display links when requested through a m… …anagement link query (like qdstat -l) You can merge this pull request into a Git repository by running: $

[jira] [Commented] (DISPATCH-179) Refactor Router Core

[ https://issues.apache.org/jira/browse/DISPATCH-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15002566#comment-15002566 ] ASF GitHub Bot commented on DISPATCH-179: - GitHub user ganeshmurthy opened a pul

[GitHub] qpid-dispatch pull request: Tross dispatch 179 1 gmurthy

Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/31 --- 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 fea

[GitHub] qpid-dispatch pull request: Tross dispatch 179 1 gmurthy

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/31 Tross dispatch 179 1 gmurthy You can merge this pull request into a Git repository by running: $ git pull https://github.com/ganeshmurthy/qpid-dispatch tross-DISPATCH-179-1-gmurthy

[jira] [Resolved] (QPID-6804) PerfTests potentially underestimate consumtion rate

[ https://issues.apache.org/jira/browse/QPID-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-6804. Resolution: Fixed > PerfTests potentially underestimate consumtion rate > ---

[jira] [Resolved] (QPID-6839) When the Selector thread hits an unknown exception it should log the exception and traceback.

[ https://issues.apache.org/jira/browse/QPID-6839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-6839. -- Resolution: Fixed > When the Selector thread hits an unknown exception it should log the > exception and

[jira] [Commented] (QPID-6804) PerfTests potentially underestimate consumtion rate

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

[jira] [Resolved] (QPID-6819) Schedule socket accepts on the thread pool

[ https://issues.apache.org/jira/browse/QPID-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-6819. Resolution: Fixed > Schedule socket accepts on the thread pool >

[jira] [Comment Edited] (QPID-6819) Schedule socket accepts on the thread pool

[ https://issues.apache.org/jira/browse/QPID-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998585#comment-14998585 ] Lorenz Quack edited comment on QPID-6819 at 11/12/15 11:39 AM: --

[jira] [Commented] (QPID-6819) Schedule socket accepts on the thread pool

[ https://issues.apache.org/jira/browse/QPID-6819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001987#comment-15001987 ] Lorenz Quack commented on QPID-6819: After talking to Keith, I retract the above review

[jira] [Commented] (QPID-6829) [Java Broker] SystemMessageSources$Consumer needs to implement flush()

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

[jira] [Resolved] (QPID-6829) [Java Broker] SystemMessageSources$Consumer needs to implement flush()

[ https://issues.apache.org/jira/browse/QPID-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack resolved QPID-6829. Resolution: Fixed > [Java Broker] SystemMessageSources$Consumer needs to implement flush() >

[jira] [Commented] (QPID-6829) [Java Broker] SystemMessageSources$Consumer needs to implement flush()

[ https://issues.apache.org/jira/browse/QPID-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001945#comment-15001945 ] Rob Godfrey commented on QPID-6829: --- Patch looks good to me > [Java Broker] SystemMessag

[jira] [Updated] (QPID-6841) [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may causes messages to become stuck

[ https://issues.apache.org/jira/browse/QPID-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-6841: -- Assignee: Keith Wall (was: Rob Godfrey) > [Java Broker] Calling recover on a subscription to a Sorted or

[jira] [Commented] (QPID-6841) [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may causes messages to become stuck

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

[jira] [Updated] (QPID-6841) [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may causes messages to become stuck

[ https://issues.apache.org/jira/browse/QPID-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-6841: -- Status: Reviewable (was: In Progress) > [Java Broker] Calling recover on a subscription to a Sorted or P

[jira] [Created] (QPID-6841) [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may causes messages to become stuck

Rob Godfrey created QPID-6841: - Summary: [Java Broker] Calling recover on a subscription to a Sorted or Priority Queue may causes messages to become stuck Key: QPID-6841 URL: https://issues.apache.org/jira/browse/QPID

[jira] [Updated] (QPID-6840) [Java Broker] Interleave calls to processPending with attempts to write outstanding data

[ https://issues.apache.org/jira/browse/QPID-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-6840: -- Assignee: Lorenz Quack (was: Rob Godfrey) > [Java Broker] Interleave calls to processPending with attemp

[jira] [Commented] (QPID-6840) [Java Broker] Interleave calls to processPending with attempts to write outstanding data

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

[jira] [Updated] (QPID-6840) [Java Broker] Interleave calls to processPending with attempts to write outstanding data

[ https://issues.apache.org/jira/browse/QPID-6840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-6840: -- Status: Reviewable (was: In Progress) > [Java Broker] Interleave calls to processPending with attempts t

[jira] [Created] (QPID-6840) [Java Broker] Interleave calls to processPending with attempts to write outstanding data

Rob Godfrey created QPID-6840: - Summary: [Java Broker] Interleave calls to processPending with attempts to write outstanding data Key: QPID-6840 URL: https://issues.apache.org/jira/browse/QPID-6840 Projec

[jira] [Updated] (QPID-6829) [Java Broker] SystemMessageSources$Consumer needs to implement flush()

[ https://issues.apache.org/jira/browse/QPID-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-6829: --- Attachment: 0001-QPID-6829-Java-Broker-Implement-AbstractSystemMessag.patch > [Java Broker] SystemMessa

[jira] [Assigned] (QPID-6829) [Java Broker] SystemMessageSources$Consumer needs to implement flush()

[ https://issues.apache.org/jira/browse/QPID-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack reassigned QPID-6829: -- Assignee: Lorenz Quack > [Java Broker] SystemMessageSources$Consumer needs to implement flush()