[jira] [Created] (DISPATCH-170) qdrouterd should not require a restart after the destination broker restarts

linuxta created DISPATCH-170: Summary: qdrouterd should not require a restart after the destination broker restarts Key: DISPATCH-170 URL: https://issues.apache.org/jira/browse/DISPATCH-170 Project: Qpid

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

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

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

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

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

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

[GitHub] qpid-dispatch pull request: DISPATCH-159: Introducing on a hierarc...

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

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

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

[GitHub] qpid-dispatch pull request: DISPATCH-159: Introducing on a hierarc...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/9 DISPATCH-159: Introducing on a hierarchical/graduated address hashing… … scheme which retrieves the address based on the hash by progressively first exact matching or later prefix matc

[jira] [Commented] (QPID-6743) Java client may log a spurious SSLPeerUnverifiedException warning during SSL connection handshake

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

[jira] [Updated] (QPID-6743) Java client may log a spurious SSLPeerUnverifiedException warning during SSL connection handshake

[ https://issues.apache.org/jira/browse/QPID-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6743: - Description: A defect in SSLReceiver may mean that the client may log a spurious {{javax.net.ssl.SSLPeerUn

[jira] [Updated] (QPID-6743) Java client may log a spurious SSLPeerUnverifiedException warning during SSL connection handshake

[ https://issues.apache.org/jira/browse/QPID-6743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6743: - Description: A defect in SSLReceiver may mean that the client may log a spurious {{javax.net.ssl.SSLPeerUn

[jira] [Created] (QPID-6743) Java client may log a spurious SSLPeerUnverifiedException warning during SSL connection handshake

Keith Wall created QPID-6743: Summary: Java client may log a spurious SSLPeerUnverifiedException warning during SSL connection handshake Key: QPID-6743 URL: https://issues.apache.org/jira/browse/QPID-6743

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

[ https://issues.apache.org/jira/browse/DISPATCH-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875922#comment-14875922 ] Jakub Scholz commented on DISPATCH-159: --- I think that as a concept, this would wor

[jira] [Updated] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/QPID-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack updated QPID-6742: --- Attachment: plot.py script for plotting memory test results with gnuplot > [Java Broker] Determine hea

[jira] [Commented] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

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

[jira] [Commented] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

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

[jira] [Commented] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

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

[jira] [Commented] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

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

[jira] [Commented] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

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

[jira] [Assigned] (QPIDJMS-51) Improve the QueueBrowser implementation

[ https://issues.apache.org/jira/browse/QPIDJMS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned QPIDJMS-51: - Assignee: Robbie Gemmell (was: Timothy Bish) > Improve the QueueBrowser implementation >

[jira] [Updated] (QPIDJMS-51) Improve the QueueBrowser implementation

[ https://issues.apache.org/jira/browse/QPIDJMS-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-51: -- Fix Version/s: 0.6.0 > Improve the QueueBrowser implementation > ---

[jira] [Commented] (DISPATCH-159) Enhance the address prefix used for link routing to support different patterns

[ https://issues.apache.org/jira/browse/DISPATCH-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875845#comment-14875845 ] Ganesh Murthy commented on DISPATCH-159: I am working on a hierarchical/graduate

[jira] [Created] (QPIDJMS-112) have receiveNoWait and receive(timeout) drain credit to ensure no message is available

Robbie Gemmell created QPIDJMS-112: -- Summary: have receiveNoWait and receive(timeout) drain credit to ensure no message is available Key: QPIDJMS-112 URL: https://issues.apache.org/jira/browse/QPIDJMS-112

[jira] [Commented] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

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

[jira] [Commented] (QPIDJMS-110) Incorrect error handling when the sender.send(...) call / message transfer causes an error

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

[jira] [Commented] (QPIDJMS-111) ensure outstanding sync ops get updated when the connection fails

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

[jira] [Created] (QPIDJMS-111) ensure outstanding sync ops get updated when the connection fails

Robbie Gemmell created QPIDJMS-111: -- Summary: ensure outstanding sync ops get updated when the connection fails Key: QPIDJMS-111 URL: https://issues.apache.org/jira/browse/QPIDJMS-111 Project: Qpid J

[jira] [Updated] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/QPID-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6742: - Attachment: more-data.tar.gz > [Java Broker] Determine heap and direct memory consumption by Java Broker >

[jira] [Updated] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/QPID-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6742: - Attachment: (was: more-data.tar.gz) > [Java Broker] Determine heap and direct memory consumption by Jav

[jira] [Commented] (QPID-6732) Change performance test framework to use a rate limiter/hill climbing algorithm to determine a sustatinable throughput for a given testcase

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

[jira] [Updated] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/QPID-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6742: - Attachment: more-data.tar.gz > [Java Broker] Determine heap and direct memory consumption by Java Broker >

[jira] [Commented] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

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

[jira] [Updated] (QPID-6742) [Java Broker] Determine heap and direct memory consumption by Java Broker with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/QPID-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-6742: - Attachment: results.tar.gz > [Java Broker] Determine heap and direct memory consumption by Java Broker > w

[jira] [Commented] (QPID-6732) Change performance test framework to use a rate limiter/hill climbing algorithm to determine a sustatinable throughput for a given testcase

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

[jira] [Commented] (QPID-6741) ThreadPoolExecutors used for virtual host IO / port IO do not scale above minimum pool size

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