[jira] [Resolved] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1791. - Resolution: Fixed Tested against the reproducer program provided by [~miha-plesko] as well as

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

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

[jira] [Commented] (QPID-8083) [REST] Refactor REST system test suite

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

[jira] [Commented] (QPID-7197) [Broker-J] Prevent deletion of objects that are in use

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

[jira] [Resolved] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

[ https://issues.apache.org/jira/browse/QPIDJMS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-365. -- Resolution: Fixed > [Failover] failover.reconnectDelay not applied between connection attempts

[jira] [Reopened] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

[ https://issues.apache.org/jira/browse/QPIDJMS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened QPIDJMS-365: -- > [Failover] failover.reconnectDelay not applied between connection attempts if > peer Closes

[jira] [Updated] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

[ https://issues.apache.org/jira/browse/QPIDJMS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-365: - Fix Version/s: 0.31.0 > [Failover] failover.reconnectDelay not applied between connection

[jira] [Resolved] (QPIDJMS-368) Connection URL keystore/truststore/user passwords can be reported unmasked as part of client logs

[ https://issues.apache.org/jira/browse/QPIDJMS-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-368. -- Resolution: Fixed Assignee: Timothy Bish Fix Version/s: 0.31.0 > Connection

[jira] [Commented] (QPIDJMS-368) Connection URL keystore/truststore/user passwords can be reported unmasked as part of client logs

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

[jira] [Closed] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

[ https://issues.apache.org/jira/browse/QPIDJMS-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed QPIDJMS-365. Resolution: Fixed > [Failover] failover.reconnectDelay not applied between connection attempts if

[jira] [Commented] (QPIDJMS-365) [Failover] failover.reconnectDelay not applied between connection attempts if peer Closes gracefully

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

[jira] [Created] (QPIDJMS-368) Connection URL keystore/truststore/user passwords can be reported unmasked as part of client logs

Alex Rudyy created QPIDJMS-368: -- Summary: Connection URL keystore/truststore/user passwords can be reported unmasked as part of client logs Key: QPIDJMS-368 URL: https://issues.apache.org/jira/browse/QPIDJMS-368

[jira] [Commented] (DISPATCH-938) Doc: Remove the "Configuration Reference"

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

[GitHub] qpid-dispatch pull request #269: DISPATCH-938: Remove config ref and add lin...

GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/269 DISPATCH-938: Remove config ref and add links to qdrouterd.conf man page You can merge this pull request into a Git repository by running: $ git pull

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402001#comment-16402001 ] Miha Plesko commented on PROTON-1791: - Indeed, if I remove _raise_ from the script above, the stalled

[jira] [Comment Edited] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401911#comment-16401911 ] Alan Conway edited comment on PROTON-1791 at 3/16/18 2:46 PM: --

[jira] [Created] (PROTON-1795) [cpp] imporved documentation for complex type mapping

Alan Conway created PROTON-1795: --- Summary: [cpp] imporved documentation for complex type mapping Key: PROTON-1795 URL: https://issues.apache.org/jira/browse/PROTON-1795 Project: Qpid Proton

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401914#comment-16401914 ] Miha Plesko commented on PROTON-1791: - [~aconway] in my previous comment I've posted a minimal script

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401911#comment-16401911 ] Alan Conway commented on PROTON-1791: - [~miha-plesko] - got it. I was only opening and closing

[jira] [Updated] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miha Plesko updated PROTON-1791: Attachment: stdout.txt stderr.txt > TCP sockets remain open in CLOSE_WAIT state >

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401862#comment-16401862 ] Miha Plesko commented on PROTON-1791: - {code} require 'qpid_proton' class RecoverableError <

[jira] [Commented] (PROTON-1791) TCP sockets remain open in CLOSE_WAIT state

[ https://issues.apache.org/jira/browse/PROTON-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401852#comment-16401852 ] Alan Conway commented on PROTON-1791: - The following mis-named commit is part of the fix for this

[jira] [Created] (QPID-8135) [JMS AMQP 0-x] Connection URL options for keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn'

Alex Rudyy created QPID-8135: Summary: [JMS AMQP 0-x] Connection URL options for keystore/trustore passwords can be logged when log level for 'org.apache.qpid' loggers is lower than 'warn' Key: QPID-8135 URL:

[jira] [Commented] (PROTON-1790) [ruby] Link name is not generated in open_sender when using hash as parameter

[ https://issues.apache.org/jira/browse/PROTON-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401846#comment-16401846 ] Alan Conway commented on PROTON-1790: - The commit 561dcf5742c3e73078e1df44f07f51caf0bdc5bc mentioned

[jira] [Resolved] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1782. - Resolution: Fixed > [ruby] implement idle_timeout and heartbeats >

[jira] [Commented] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401841#comment-16401841 ] Alan Conway commented on PROTON-1782: - The fix is now on master. The official gem update has to

[jira] [Comment Edited] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401841#comment-16401841 ] Alan Conway edited comment on PROTON-1782 at 3/16/18 12:58 PM: --- The fix is

[jira] [Commented] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

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

[jira] [Commented] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

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

[jira] [Commented] (PROTON-1782) [ruby] implement idle_timeout and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16401803#comment-16401803 ] Miha Plesko commented on PROTON-1782: - [~aconway] I confirm we're not getting "local-idle-timeout

[jira] [Updated] (QPID-8124) [Broker-J][REST] Sucessfully authenticated user is reported as <> in ACL operational logs when checking access to management

[ https://issues.apache.org/jira/browse/QPID-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8124: - Fix Version/s: qpid-java-broker-7.0.3 > [Broker-J][REST] Sucessfully authenticated user is reported as <>

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-7948: - Fix Version/s: qpid-java-broker-7.0.3 > [Java Broker] [AMQP0-9] [Publish Confirms] Client hangs if message

[jira] [Updated] (QPID-8064) [Broker-J] FileKeyStore should validate java keystore content to make sure that private key is present

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

[jira] [Updated] (QPID-7925) [Java Broker] [WMC] Add ability to maintain rule-based access control provider for virtualhost

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

[jira] [Updated] (QPID-8016) [Broker-J] FileKeyStore alias does not select the correct certificate

[ https://issues.apache.org/jira/browse/QPID-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8016: - Fix Version/s: qpid-java-broker-7.0.3 > [Broker-J] FileKeyStore alias does not select the correct

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-7948: - Status: Reviewable (was: In Progress) > [Java Broker] [AMQP0-9] [Publish Confirms] Client hangs if

[jira] [Assigned] (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:all-tabpanel ] Keith Wall reassigned QPID-7948: Assignee: Keith Wall > [Java Broker] [AMQP0-9] [Publish Confirms] Client hangs if message sent to

[jira] [Updated] (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:all-tabpanel ] Keith Wall updated QPID-7948: - Fix Version/s: (was: Future) qpid-java-broker-7.1.0 > [Java Broker] [AMQP0-9]