[jira] [Commented] (AMQ-6660) Deadlock closing a connection due to an exception

[ https://issues.apache.org/jira/browse/AMQ-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15979427#comment-15979427 ] Dan Groves commented on AMQ-6660: - No, I have not tried that yet. > Deadlock closing a connection due to

[jira] [Commented] (AMQ-6660) Deadlock closing a connection due to an exception

[ https://issues.apache.org/jira/browse/AMQ-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15979422#comment-15979422 ] Timothy Bish commented on AMQ-6660: --- 5.8.0 is rather ancient, have you tried with a current release? >

[jira] [Updated] (AMQ-6660) Deadlock closing a connection due to an exception

[ https://issues.apache.org/jira/browse/AMQ-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Groves updated AMQ-6660: Description: While recovering from a period of network instability, our application deadlocked in ActiveMQ

[jira] [Commented] (ARTEMIS-1116) map ldap roles to local artemis roles

[ https://issues.apache.org/jira/browse/ARTEMIS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15979289#comment-15979289 ] ASF GitHub Bot commented on ARTEMIS-1116: - Github user sjhiggs commented on the issue:

[jira] [Closed] (ARTEMIS-1127) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

[ https://issues.apache.org/jira/browse/ARTEMIS-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed ARTEMIS-1127. - Resolution: Fixed > AMQP: Match client SenderSettleMode instead of always defaulting to MIXED >

[jira] [Commented] (ARTEMIS-1127) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

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

[jira] [Commented] (ARTEMIS-1127) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

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

[jira] [Commented] (ARTEMIS-1127) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

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

[jira] [Created] (ARTEMIS-1127) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

Timothy Bish created ARTEMIS-1127: - Summary: AMQP: Match client SenderSettleMode instead of always defaulting to MIXED Key: ARTEMIS-1127 URL: https://issues.apache.org/jira/browse/ARTEMIS-1127

[jira] [Created] (AMQNET-564) Individual Acknowledgements are slow for large amounts of messages

Juri Robl created AMQNET-564: Summary: Individual Acknowledgements are slow for large amounts of messages Key: AMQNET-564 URL: https://issues.apache.org/jira/browse/AMQNET-564 Project: ActiveMQ .Net

[jira] [Resolved] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version 4.1.9.Final

[ https://issues.apache.org/jira/browse/AMQ-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6630. --- Resolution: Fixed > AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version >

[jira] [Commented] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version 4.1.9.Final

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

[jira] [Updated] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version 4.1.9.Final

[ https://issues.apache.org/jira/browse/AMQ-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6630: -- Summary: AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version 4.1.9.Final (was:

[jira] [Updated] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version

[ https://issues.apache.org/jira/browse/AMQ-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6630: -- Description: Update to latest Qpid JMS release and match the Netty version > AMQP: Update Qpid JMS to

[jira] [Updated] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version

[ https://issues.apache.org/jira/browse/AMQ-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6630: -- Summary: AMQP: Update Qpid JMS to latest 0.22.0 release and match its netty version (was: AMQP: Update

[jira] [Reopened] (AMQ-6630) AMQP: Update Qpid JMS to latest 0.21.0 release and match its netty version

[ https://issues.apache.org/jira/browse/AMQ-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reopened AMQ-6630: --- > AMQP: Update Qpid JMS to latest 0.21.0 release and match its netty version >

[jira] [Commented] (AMQ-6659) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

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

[jira] [Resolved] (AMQ-6659) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

[ https://issues.apache.org/jira/browse/AMQ-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-6659. --- Resolution: Fixed > AMQP: Match client SenderSettleMode instead of always defaulting to MIXED >

[jira] [Commented] (AMQ-6659) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

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

[jira] [Updated] (AMQ-6659) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

[ https://issues.apache.org/jira/browse/AMQ-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQ-6659: -- Fix Version/s: 5.14.6 > AMQP: Match client SenderSettleMode instead of always defaulting to MIXED >

[jira] [Created] (AMQ-6659) AMQP: Match client SenderSettleMode instead of always defaulting to MIXED

Timothy Bish created AMQ-6659: - Summary: AMQP: Match client SenderSettleMode instead of always defaulting to MIXED Key: AMQ-6659 URL: https://issues.apache.org/jira/browse/AMQ-6659 Project: ActiveMQ

[jira] [Commented] (ARTEMIS-1093) Full qualified queue name support

[ https://issues.apache.org/jira/browse/ARTEMIS-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978811#comment-15978811 ] ASF GitHub Bot commented on ARTEMIS-1093: - Github user gaohoward commented on the issue:

[jira] [Commented] (ARTEMIS-1125) Artemis 1.x does not persist JMS bindings in database instead it is using files

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

[jira] [Commented] (ARTEMIS-1093) Full qualified queue name support

[ https://issues.apache.org/jira/browse/ARTEMIS-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15978245#comment-15978245 ] ASF GitHub Bot commented on ARTEMIS-1093: - Github user gaohoward commented on the issue: