[jira] [Commented] (DISPATCH-1020) Detach expiring links with closed=true when peer connectivity lost

[ https://issues.apache.org/jira/browse/DISPATCH-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517595#comment-16517595 ] Gordon Sim commented on DISPATCH-1020: -- One possibility proposed here:

Review Request 67661: propagate link-detach as expiry policy for link route if none was explicitly selected by client

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67661/ --- Review request for qpid, Alan Conway and Ted Ross. Bugs: DISPATCH-1020

[jira] [Commented] (PROTON-1866) cannot tell whether peer specified expiry-policy on terminus

[ https://issues.apache.org/jira/browse/PROTON-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517591#comment-16517591 ] Gordon Sim commented on PROTON-1866: suggested fix: https://reviews.apache.org/r/67659/ > cannot

Review Request 67659: provide new function to test whether an explicit expiry policy was set on a terminus

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67659/ --- Review request for qpid, Alan Conway and Andrew Stitcher. Bugs: PROTON-1866

[jira] [Created] (PROTON-1866) cannot tell whether peer specified expiry-policy on terminus

Gordon Sim created PROTON-1866: -- Summary: cannot tell whether peer specified expiry-policy on terminus Key: PROTON-1866 URL: https://issues.apache.org/jira/browse/PROTON-1866 Project: Qpid Proton

[jira] [Commented] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517456#comment-16517456 ] Alex Rudyy commented on QPID-8210: -- Keith, I made a change in commit

[jira] [Updated] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8210: - Summary: [Broker-J] Consumer attach when message is being released and requeued can end-up in broker

[jira] [Updated] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8210: - Description: The consumer node is currently set after consumer is added into queue consumer manager.

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 6:00 PM: --- Change looks

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 5:57 PM: --- Change looks

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 5:56 PM: --- Change looks

[jira] [Commented] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall commented on QPID-8210: -- Change looks reasonable to me, but I notice that

[jira] [Commented] (DISPATCH-476) qualified link routing

[ https://issues.apache.org/jira/browse/DISPATCH-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517339#comment-16517339 ] ASF GitHub Bot commented on DISPATCH-476: - Github user lulf closed the pull request at:

[GitHub] qpid-dispatch pull request #111: DISPATCH-476: Add support for groupId prope...

Github user lulf closed the pull request at: https://github.com/apache/qpid-dispatch/pull/111 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPIDJMS-395) connection:forced leads to JMSException even though reconnect is enabled

[ https://issues.apache.org/jira/browse/QPIDJMS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517277#comment-16517277 ] Timothy Bish commented on QPIDJMS-395: -- Would you not be testing for

[jira] [Comment Edited] (QPIDJMS-395) connection:forced leads to JMSException even though reconnect is enabled

[ https://issues.apache.org/jira/browse/QPIDJMS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517274#comment-16517274 ] Jiri Daněk edited comment on QPIDJMS-395 at 6/19/18 4:19 PM: - I do need to

[jira] [Commented] (QPIDJMS-395) connection:forced leads to JMSException even though reconnect is enabled

[ https://issues.apache.org/jira/browse/QPIDJMS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517274#comment-16517274 ] Jiri Daněk commented on QPIDJMS-395: I do need to inspect the exception I got from send, because I

[jira] [Commented] (QPIDJMS-395) connection:forced leads to JMSException even though reconnect is enabled

[ https://issues.apache.org/jira/browse/QPIDJMS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517273#comment-16517273 ] Timothy Bish commented on QPIDJMS-395: -- Having a JMS client specific exception would mean that

[jira] [Commented] (DISPATCH-1043) In a two router network, qdstat -g is showing non-zero values for "Ingress Count" even when no messages are sent

[ https://issues.apache.org/jira/browse/DISPATCH-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517267#comment-16517267 ] Ganesh Murthy commented on DISPATCH-1043: - Looks for tests relating to this issue when the fix

[jira] [Resolved] (DISPATCH-1043) In a two router network, qdstat -g is showing non-zero values for "Ingress Count" even when no messages are sent

[ https://issues.apache.org/jira/browse/DISPATCH-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1043. - Resolution: Fixed > In a two router network, qdstat -g is showing non-zero values for

[jira] [Commented] (QPIDJMS-395) connection:forced leads to JMSException even though reconnect is enabled

[ https://issues.apache.org/jira/browse/QPIDJMS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517248#comment-16517248 ] Jiri Daněk commented on QPIDJMS-395: I will just resend if I get such exception. Artemis Core JMS

[jira] [Created] (DISPATCH-1043) In a two router network, qdstat -g is showing non-zero values for "Ingress Count" even when no messages are sent

Ganesh Murthy created DISPATCH-1043: --- Summary: In a two router network, qdstat -g is showing non-zero values for "Ingress Count" even when no messages are sent Key: DISPATCH-1043 URL:

[jira] [Commented] (PROTON-1354) Disable problematic SASL mechanisms if they are not explicitly enabled

[ https://issues.apache.org/jira/browse/PROTON-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517189#comment-16517189 ] ASF GitHub Bot commented on PROTON-1354: Github user codecov-io commented on the issue:

[GitHub] qpid-proton issue #148: PROTON-1354: Don't allow SASL mechanisms GSSAPI or G...

Github user codecov-io commented on the issue: https://github.com/apache/qpid-proton/pull/148 # [Codecov](https://codecov.io/gh/apache/qpid-proton/pull/148?src=pr=h1) Report > Merging [#148](https://codecov.io/gh/apache/qpid-proton/pull/148?src=pr=desc) into

[jira] [Created] (PROTON-1865) Improve split between general SASL code and the specific implementations

Andrew Stitcher created PROTON-1865: --- Summary: Improve split between general SASL code and the specific implementations Key: PROTON-1865 URL: https://issues.apache.org/jira/browse/PROTON-1865

[jira] [Updated] (QPID-8208) [Broker-J] Improve handling of unexpected exceptions on establishing LDAP connections in SimpleLDAPAuthenticationProvider

[ https://issues.apache.org/jira/browse/QPID-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8208: - Attachment: (was: 0001-QPID-8208-Broker-J-Improve-exception-handling.patch) > [Broker-J] Improve

[jira] [Resolved] (QPID-8208) [Broker-J] Improve handling of unexpected exceptions on establishing LDAP connections in SimpleLDAPAuthenticationProvider

[ https://issues.apache.org/jira/browse/QPID-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8208. -- Resolution: Invalid Fix Version/s: (was: qpid-java-broker-7.0.6) Closing JIRA as invalid as

[jira] [Commented] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516795#comment-16516795 ] Alex Rudyy commented on QPID-8210: -- The fix for the issue is committed

[jira] [Commented] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516790#comment-16516790 ] Alex Rudyy commented on QPID-8210: -- Exception stack trace for another occurrence of the issue when

[jira] [Updated] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8210: - Description: The consumer node is currently set after consumer is added into queue consumer manager.