[jira] [Updated] (DISPATCH-341) router did not respond to request to drain a message-routed consumers link credit

[ https://issues.apache.org/jira/browse/DISPATCH-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-341: -- Fix Version/s: (was: 0.7.0) 0.6.1 > router did not respond to request to drain

[jira] [Updated] (DISPATCH-365) Standalone router crashes if an interior router attempts to connect to it

[ https://issues.apache.org/jira/browse/DISPATCH-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-365: -- Fix Version/s: (was: 0.6.0) 0.6.1 > Standalone router crashes if an interior

[jira] [Updated] (DISPATCH-364) Inter-router listeners should not permit normal endpoint traffic

[ https://issues.apache.org/jira/browse/DISPATCH-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-364: -- Fix Version/s: 0.6.1 > Inter-router listeners should not permit normal endpoint traffic >

[jira] [Commented] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328190#comment-15328190 ] Ganesh Murthy commented on DISPATCH-385: Same case with the VPN. Did not observe any crashes in

[jira] [Updated] (DISPATCH-380) Router stops receiving messages from multiple senders publishing to multiple queues in parallel

[ https://issues.apache.org/jira/browse/DISPATCH-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-380: -- Fix Version/s: (was: 0.6.0) > Router stops receiving messages from multiple senders publishing to

[jira] [Resolved] (DISPATCH-256) Documentation Updates for 0.6

[ https://issues.apache.org/jira/browse/DISPATCH-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-256. --- Resolution: Fixed > Documentation Updates for 0.6 > - > >

[jira] [Updated] (DISPATCH-367) balanced distribution needs to be more... balanced.

[ https://issues.apache.org/jira/browse/DISPATCH-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-367: -- Fix Version/s: (was: 0.6.0) > balanced distribution needs to be more... balanced. >

[jira] [Commented] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328080#comment-15328080 ] Ganesh Murthy commented on DISPATCH-385: I will try this over VPN when on the Redhat guest

[jira] [Commented] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328078#comment-15328078 ] Ganesh Murthy commented on DISPATCH-385: Ernie, were you sending any messages to the broker via

[jira] [Commented] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328076#comment-15328076 ] Ganesh Murthy commented on DISPATCH-385: I am on master proton and dispatch. I added this to my

[jira] [Comment Edited] (PROTON-1224) Proton-J SSL uses deprecated Bouncy Castle functionality

[ https://issues.apache.org/jira/browse/PROTON-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328068#comment-15328068 ] Jem Day edited comment on PROTON-1224 at 6/13/16 7:56 PM: -- Robbie, I closed

[jira] [Commented] (PROTON-1224) Proton-J SSL uses deprecated Bouncy Castle functionality

[ https://issues.apache.org/jira/browse/PROTON-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328068#comment-15328068 ] Jem Day commented on PROTON-1224: - Robbie, I close out the original PR and created a new one, the CI

[jira] [Commented] (DISPATCH-386) Router crashes in qd_link_pn

[ https://issues.apache.org/jira/browse/DISPATCH-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327995#comment-15327995 ] Ganesh Murthy commented on DISPATCH-386: "Each sender has 60 threads. Each receiver has 60

[jira] [Updated] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen updated DISPATCH-385: -- Attachment: Y.conf X.conf D.conf C.conf

[jira] [Commented] (PROTON-1231) python: proton.utils.BlockingConnection hides disconnect error info

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

[jira] [Commented] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327971#comment-15327971 ] Ganesh Murthy commented on DISPATCH-385: Ernie, can you please attach your router config file to

[jira] [Commented] (DISPATCH-383) Intermittent router crashes when restarting one router in the network with different number of threads

[ https://issues.apache.org/jira/browse/DISPATCH-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327955#comment-15327955 ] Vishal Sharda commented on DISPATCH-383: These are intermittent crashes and I do not yet have a

[jira] [Commented] (DISPATCH-383) Intermittent router crashes when restarting one router in the network with different number of threads

[ https://issues.apache.org/jira/browse/DISPATCH-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15327913#comment-15327913 ] Ganesh Murthy commented on DISPATCH-383: On a Debian 8.3 virtual machine, I followed the steps

[jira] [Assigned] (DISPATCH-385) Router crashes when on-demand host is no longer reachable

[ https://issues.apache.org/jira/browse/DISPATCH-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-385: -- Assignee: Ganesh Murthy > Router crashes when on-demand host is no longer reachable

[jira] [Closed] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME

[ https://issues.apache.org/jira/browse/PROTON-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen closed PROTON-1233. Resolution: Fixed > Windows schannel: match OpenSSL and require non-null hostname for >

[jira] [Commented] (PROTON-1233) Windows schannel: match OpenSSL and require non-null hostname for PN_SSL_VERIFY_PEER_NAME

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

[jira] [Created] (DISPATCH-386) Router crashes in qd_link_pn

Eric Leu created DISPATCH-386: - Summary: Router crashes in qd_link_pn Key: DISPATCH-386 URL: https://issues.apache.org/jira/browse/DISPATCH-386 Project: Qpid Dispatch Issue Type: Bug

[jira] [Updated] (QPID-7301) [Java Client] [Java Broker] JMS Selector parsing will not fail if a valid selector is followed by invalid text

[ https://issues.apache.org/jira/browse/QPID-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-7301: -- Status: Reviewable (was: In Progress) > [Java Client] [Java Broker] JMS Selector parsing will not fail

[jira] [Commented] (QPID-7301) [Java Client] [Java Broker] JMS Selector parsing will not fail if a valid selector is followed by invalid text

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

[jira] [Created] (QPID-7301) [Java Client] [Java Broker] JMS Selector parsing will not fail if a valid selector is followed by invalid text

Rob Godfrey created QPID-7301: - Summary: [Java Client] [Java Broker] JMS Selector parsing will not fail if a valid selector is followed by invalid text Key: QPID-7301 URL:

[jira] [Comment Edited] (DISPATCH-184) dispatch do not stop when 'amqp' is not defined

[ https://issues.apache.org/jira/browse/DISPATCH-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324085#comment-15324085 ] Jiri Danek edited comment on DISPATCH-184 at 6/13/16 2:40 PM: -- Issue is

[jira] [Assigned] (DISPATCH-383) Intermittent router crashes when restarting one router in the network with different number of threads

[ https://issues.apache.org/jira/browse/DISPATCH-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-383: -- Assignee: Ganesh Murthy > Intermittent router crashes when restarting one router in

[jira] [Resolved] (DISPATCH-381) qdstat -g causes segfault

[ https://issues.apache.org/jira/browse/DISPATCH-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-381. Resolution: Fixed Fix Version/s: 0.7.0 > qdstat -g causes segfault >

[jira] [Commented] (DISPATCH-381) qdstat -g causes segfault

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

[jira] [Commented] (DISPATCH-211) Expose connection properties in management response

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

[jira] [Updated] (PROTON-1236) Reactor - segfault if connection address cannot be resolved

[ https://issues.apache.org/jira/browse/PROTON-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1236: Priority: Critical (was: Major) > Reactor - segfault if connection address cannot be resolved >

[jira] [Updated] (PROTON-1236) Reactor - segfault if connection address cannot be resolved

[ https://issues.apache.org/jira/browse/PROTON-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1236: Fix Version/s: (was: 0.13.0) 0.13.1 > Reactor - segfault if connection

[jira] [Commented] (QPID-7287) Query parser fails silently with expression such as a + b

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

[jira] [Assigned] (DISPATCH-378) Seg Fault in CORE_link_push

[ https://issues.apache.org/jira/browse/DISPATCH-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-378: - Assignee: Ted Ross > Seg Fault in CORE_link_push > --- > >

[jira] [Resolved] (DISPATCH-384) qdrouter.conf manual : saslMechanisms as "Space separated list ..."

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

[jira] [Assigned] (DISPATCH-384) qdrouter.conf manual : saslMechanisms as "Space separated list ..."

[ https://issues.apache.org/jira/browse/DISPATCH-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-384: -- Assignee: Ganesh Murthy > qdrouter.conf manual : saslMechanisms as "Space separated

[jira] [Commented] (QPID-7108) [Java Broker] Test BDBHAVirtualHostNodeTest.testIntruderProtection is failing sporadically

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

[jira] [Resolved] (QPID-7297) [Java Client] Using socket:// address to supply a preexisting existing socket to the client fails on the 0-10 path

[ https://issues.apache.org/jira/browse/QPID-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-7297. --- Resolution: Fixed > [Java Client] Using socket:// address to supply a preexisting existing socket >

[jira] [Updated] (QPID-7297) [Java Client] Using socket:// address to supply a preexisting existing socket to the client fails on the 0-10 path

[ https://issues.apache.org/jira/browse/QPID-7297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7297: - Fix Version/s: (was: qpid-java-6.0.4) > [Java Client] Using socket:// address to supply a preexisting

[jira] [Commented] (QPID-7297) [Java Client] Using socket:// address to supply a preexisting existing socket to the client fails on the 0-10 path

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

[jira] [Created] (DISPATCH-384) qdrouter.conf manual : saslMechanisms as "Space separated list ..."

Paolo Patierno created DISPATCH-384: --- Summary: qdrouter.conf manual : saslMechanisms as "Space separated list ..." Key: DISPATCH-384 URL: https://issues.apache.org/jira/browse/DISPATCH-384 Project: