[jira] [Commented] (PROTON-1408) long-lived connections suffer large performance hit after many messages

[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951930#comment-15951930 ] ASF GitHub Bot commented on PROTON-1408: Github user mgoulish commented on the is

[GitHub] qpid-proton issue #100: PROTON-1408 -- fixes for message ID wraparound bugs

Github user mgoulish commented on the issue: https://github.com/apache/qpid-proton/pull/100 OK! No problem. Same qdrouterd behavior using unaltered proton code. All is well. Hale and Hearty. A-OK. No problemo. Hasta la Vista. --- If your project is set up for it, you can rep

[jira] [Commented] (PROTON-1408) long-lived connections suffer large performance hit after many messages

[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951868#comment-15951868 ] ASF GitHub Bot commented on PROTON-1408: Github user mgoulish commented on the is

[GitHub] qpid-proton issue #100: PROTON-1408 -- fixes for message ID wraparound bugs

Github user mgoulish commented on the issue: https://github.com/apache/qpid-proton/pull/100 Wait! Don't pull this yet! I am seeing something weird with memory usage that I want to check out. I will report back. --- If your project is set up for it, you can reply to this email and

[jira] [Resolved] (DISPATCH-734) Weird class / adress name while using url like queue name

[ https://issues.apache.org/jira/browse/DISPATCH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-734. Resolution: Fixed Fix Version/s: (was: 1.0.0) 0.8.0 This pro

[jira] [Updated] (DISPATCH-734) Weird class / adress name while using url like queue name

[ https://issues.apache.org/jira/browse/DISPATCH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-734: --- Fix Version/s: 1.0.0 > Weird class / adress name while using url like queue name > -

[jira] [Assigned] (DISPATCH-734) Weird class / adress name while using url like queue name

[ https://issues.apache.org/jira/browse/DISPATCH-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-734: -- Assignee: Ganesh Murthy > Weird class / adress name while using url like queue name >

[jira] [Resolved] (QPIDJMS-282) creating a Connection can time out if a pipelined Open frame arrives before the client sends its own

[ https://issues.apache.org/jira/browse/QPIDJMS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-282. Resolution: Fixed > creating a Connection can time out if a pipelined Open frame arrives be

[jira] [Commented] (DISPATCH-737) qdstat and qdmanage always force sasl exchange

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

[GitHub] qpid-dispatch pull request #156: DISPATCH-737 - Set the sasl_enabled flag ba...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/156 DISPATCH-737 - Set the sasl_enabled flag based on some of the paramet… …ers provided to qdstat and qdmanage You can merge this pull request into a Git repository by running: $ g

[jira] [Commented] (QPIDJMS-282) creating a Connection can time out if a pipelined Open frame arrives before the client sends its own

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

[jira] [Created] (QPIDJMS-282) creating a Connection can time out if a pipelined Open frame arrives before the client sends its own

Robbie Gemmell created QPIDJMS-282: -- Summary: creating a Connection can time out if a pipelined Open frame arrives before the client sends its own Key: QPIDJMS-282 URL: https://issues.apache.org/jira/browse/QPIDJ

[jira] [Commented] (QPIDJMS-281) Add option to the transport to allow for tracing bytes in / out in the logs

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

[jira] [Resolved] (QPIDJMS-281) Add option to the transport to allow for tracing bytes in / out in the logs

[ https://issues.apache.org/jira/browse/QPIDJMS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-281. -- Resolution: Fixed > Add option to the transport to allow for tracing bytes in / out in the logs

[jira] [Commented] (QPIDJMS-281) Add option to the transport to allow for tracing bytes in / out in the logs

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

[jira] [Created] (QPIDJMS-281) Add option to the transport to allow for tracing bytes in / out in the logs

Timothy Bish created QPIDJMS-281: Summary: Add option to the transport to allow for tracing bytes in / out in the logs Key: QPIDJMS-281 URL: https://issues.apache.org/jira/browse/QPIDJMS-281 Project:

[jira] [Created] (DISPATCH-737) qdstat and qdmanage always force sasl exchange

Ganesh Murthy created DISPATCH-737: -- Summary: qdstat and qdmanage always force sasl exchange Key: DISPATCH-737 URL: https://issues.apache.org/jira/browse/DISPATCH-737 Project: Qpid Dispatch

[jira] [Commented] (PROTON-1408) long-lived connections suffer large performance hit after many messages

[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951171#comment-15951171 ] ASF GitHub Bot commented on PROTON-1408: Github user kgiusti commented on the iss

[GitHub] qpid-proton issue #100: PROTON-1408 -- fixes for message ID wraparound bugs

Github user kgiusti commented on the issue: https://github.com/apache/qpid-proton/pull/100 Fyi - I've checked in a fix to the travis issue. Rebase to master and re-run the travis tests - they should pass. --- If your project is set up for it, you can reply to this email and have you

[jira] [Created] (DISPATCH-736) 3 system tests in the test suite are failing on RHEL 6.4

Ganesh Murthy created DISPATCH-736: -- Summary: 3 system tests in the test suite are failing on RHEL 6.4 Key: DISPATCH-736 URL: https://issues.apache.org/jira/browse/DISPATCH-736 Project: Qpid Dispatch

[jira] [Created] (QPID-7731) Upgrade to Jetty 9.4

Keith Wall created QPID-7731: Summary: Upgrade to Jetty 9.4 Key: QPID-7731 URL: https://issues.apache.org/jira/browse/QPID-7731 Project: Qpid Issue Type: Improvement Components: Java Br

[jira] [Updated] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

[ https://issues.apache.org/jira/browse/QPID-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7729: - Priority: Minor (was: Major) > [Java Broker, WMC] Fix evaluation of context path in the Web Management >

[jira] [Resolved] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

[ https://issues.apache.org/jira/browse/QPID-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7729. -- Resolution: Fixed > [Java Broker, WMC] Fix evaluation of context path in the Web Management > Console >

[jira] [Resolved] (QPID-7658) [Java Broker] Improve LinkRegistry

[ https://issues.apache.org/jira/browse/QPID-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7658. -- Resolution: Fixed The changes look good to me. I am resolving this JIRA > [Java Broker] Improve LinkRegi

[jira] [Commented] (QPIDJMS-280) Update the TestPeer used in the client to enable TCP_NODELAY

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

[jira] [Resolved] (QPIDJMS-280) Update the TestPeer used in the client to enable TCP_NODELAY

[ https://issues.apache.org/jira/browse/QPIDJMS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-280. -- Resolution: Fixed > Update the TestPeer used in the client to enable TCP_NODELAY >

[jira] [Updated] (QPIDJMS-280) Update the TestPeer used in the client to enable TCP_NODELAY

[ https://issues.apache.org/jira/browse/QPIDJMS-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-280: - Description: The TestPeer used in the tests in the qpid-jms-client module doesn't currently enab

[jira] [Created] (QPIDJMS-280) Update the TestPeer used in the client to enable TCP_NODELAY

Timothy Bish created QPIDJMS-280: Summary: Update the TestPeer used in the client to enable TCP_NODELAY Key: QPIDJMS-280 URL: https://issues.apache.org/jira/browse/QPIDJMS-280 Project: Qpid JMS

[jira] [Commented] (PROTON-1453) pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings

[ https://issues.apache.org/jira/browse/PROTON-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951005#comment-15951005 ] ASF GitHub Bot commented on PROTON-1453: GitHub user kgiusti opened a pull reques

[GitHub] qpid-proton pull request #102: NO-JIRA: revert temporary workaround for PROT...

GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-proton/pull/102 NO-JIRA: revert temporary workaround for PROTON-1453 Looks like the fix for PROTON-1453 resolves the problems travis hit for the tox tests. This change reverts just the change where the travis

[jira] [Assigned] (DISPATCH-735) Crash on startup parsing JSON conf file with "address" entity

[ https://issues.apache.org/jira/browse/DISPATCH-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-735: -- Assignee: Ganesh Murthy > Crash on startup parsing JSON conf file with "address" enti

[jira] [Resolved] (DISPATCH-735) Crash on startup parsing JSON conf file with "address" entity

[ https://issues.apache.org/jira/browse/DISPATCH-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-735. Resolution: Fixed Fix Version/s: 0.8.0 > Crash on startup parsing JSON conf file wi

[jira] [Commented] (DISPATCH-735) Crash on startup parsing JSON conf file with "address" entity

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

[jira] [Issue Comment Deleted] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated DISPATCH-506: Comment: was deleted (was: I'm re-opening it because after the fix the router sends the de

[jira] [Closed] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno closed DISPATCH-506. --- Resolution: Fixed Sorry for re-opening it. The close=false is deliberate after the discussio

[jira] [Resolved] (PROTON-1453) pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings

[ https://issues.apache.org/jira/browse/PROTON-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved PROTON-1453. Resolution: Fixed > pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings >

[jira] [Commented] (PROTON-1453) pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings

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

[jira] [Reopened] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno reopened DISPATCH-506: - I'm re-opening it because after the fix the router sends the detach with closed=false, this

[jira] [Commented] (PROTON-1453) pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings

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

[GitHub] qpid-proton pull request #101: PROTON-1453: properly terminate output string...

Github user asfgit closed the pull request at: https://github.com/apache/qpid-proton/pull/101 --- 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] [Updated] (DISPATCH-735) Crash on startup parsing JSON conf file with "address" entity

[ https://issues.apache.org/jira/browse/DISPATCH-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated DISPATCH-735: Description: Hi, using a router configuration file in the JSON format with something like

[jira] [Created] (DISPATCH-735) Crash on startup parsing JSON conf file with "address" entity

Paolo Patierno created DISPATCH-735: --- Summary: Crash on startup parsing JSON conf file with "address" entity Key: DISPATCH-735 URL: https://issues.apache.org/jira/browse/DISPATCH-735 Project: Qpid D

[jira] [Commented] (PROTON-1453) pn_ssl_get_{protocol|cypher}_name() may segfault when called by bindings

[ https://issues.apache.org/jira/browse/PROTON-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950918#comment-15950918 ] ASF GitHub Bot commented on PROTON-1453: Github user kgiusti commented on the iss

[GitHub] qpid-proton issue #101: PROTON-1453: properly terminate output string buffer

Github user kgiusti commented on the issue: https://github.com/apache/qpid-proton/pull/101 I agree with Alan on this - but in this specific case proton is actually *inconsistent* in the handling of this buffer. In the schannel impl the buffer is null terminated regardless of outcome

[jira] [Commented] (QPID-7658) [Java Broker] Improve LinkRegistry

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

[jira] [Commented] (QPID-7658) [Java Broker] Improve LinkRegistry

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

[jira] [Created] (QPID-7730) [Java Broker] Upgrade logback to latest version (1.2.2)

Alex Rudyy created QPID-7730: Summary: [Java Broker] Upgrade logback to latest version (1.2.2) Key: QPID-7730 URL: https://issues.apache.org/jira/browse/QPID-7730 Project: Qpid Issue Type: Bug

[jira] [Comment Edited] (QPID-7658) [Java Broker] Improve LinkRegistry

[ https://issues.apache.org/jira/browse/QPID-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950830#comment-15950830 ] Lorenz Quack edited comment on QPID-7658 at 3/31/17 1:08 PM: - T

[jira] [Commented] (QPID-7658) [Java Broker] Improve LinkRegistry

[ https://issues.apache.org/jira/browse/QPID-7658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950830#comment-15950830 ] Lorenz Quack commented on QPID-7658: * {{NamedAddressSpace#getSendingLink(String, Strin

[jira] [Commented] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

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

[jira] [Commented] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

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

[jira] [Commented] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

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

[GitHub] qpid-java pull request #3: Fixe bug: the 'contextPath' does not end with '/'

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

[jira] [Commented] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

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

[jira] [Commented] (PROTON-1408) long-lived connections suffer large performance hit after many messages

[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950779#comment-15950779 ] ASF GitHub Bot commented on PROTON-1408: Github user mgoulish commented on the is

[GitHub] qpid-proton issue #100: PROTON-1408 -- fixes for message ID wraparound bugs

Github user mgoulish commented on the issue: https://github.com/apache/qpid-proton/pull/100 Ah, I see now. This is a general problem in the python-tox py33 test that started recently -- not related to my little change. Nihil Obstat. Imprimatur. --- If your project is set up fo

[jira] [Resolved] (QPID-7468) Upgrade logback to 1.1.11 and SLF4J to 1.7.24

[ https://issues.apache.org/jira/browse/QPID-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7468. -- Resolution: Fixed The changes look good to me > Upgrade logback to 1.1.11 and SLF4J to 1.7.24 >

[jira] [Commented] (QPID-7468) Upgrade logback to 1.1.11 and SLF4J to 1.7.24

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

[jira] [Updated] (QPIDJMS-279) Add support for Netty Epoll transport

[ https://issues.apache.org/jira/browse/QPIDJMS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-279: --- Description: Add support for using the Netty Epoll transport when the platform supports it (

[jira] [Updated] (QPIDJMS-279) Add support for Netty Epoll transport

[ https://issues.apache.org/jira/browse/QPIDJMS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPIDJMS-279: --- Description: Add support for using the Netty Epoll transport when the platform supports it (

[jira] [Commented] (PROTON-1408) long-lived connections suffer large performance hit after many messages

[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950687#comment-15950687 ] ASF GitHub Bot commented on PROTON-1408: Github user mgoulish commented on the is

[GitHub] qpid-proton issue #100: PROTON-1408 -- fixes for message ID wraparound bugs

Github user mgoulish commented on the issue: https://github.com/apache/qpid-proton/pull/100 Final (hopefully) code with make_hash fn has passed full test (64-bit) starting at ID 0, now at 5e9 with no ill effects. I am looking into Travis build failure. --- If your project is set up

[jira] [Commented] (QPIDJMS-279) Add support for Netty Epoll transport

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

[jira] [Resolved] (QPID-3987) Tests broker_0_9.queue.QueueTests.test_unbind_fanout and broker_0_9.queue.QueueTests.test_unbind_headers fail with 404, 'No such binding'

[ https://issues.apache.org/jira/browse/QPID-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-3987. -- Resolution: Fixed The changes look good to me. Although I think that fanout exchange implementation itse

[jira] [Commented] (QPID-7729) [Java Broker, WMC] Fix evaluation of context path in the Web Management Console

[ https://issues.apache.org/jira/browse/QPID-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950574#comment-15950574 ] Keith Wall commented on QPID-7729: -- Change looks reasonable. We need to remember to add t