[jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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

[jira] [Commented] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

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

[jira] [Resolved] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

[ https://issues.apache.org/jira/browse/ARTEMIS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram resolved ARTEMIS-395. Resolution: Fixed > Auto-delete JMS queues only if auto-delete-jms-queues = true >

[jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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

[jira] [Commented] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

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

[jira] [Commented] (AMQ-6162) DLQ'd message does not get DLQ'd again until broker restart

[ https://issues.apache.org/jira/browse/AMQ-6162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15138736#comment-15138736 ] Jo Vandermeeren commented on AMQ-6162: -- That is correct, a broker restart does not resolve the issue

[jira] [Commented] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

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

[jira] [Created] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

Justin Bertram created ARTEMIS-395: -- Summary: Auto-delete JMS queues only if auto-delete-jms-queues = true Key: ARTEMIS-395 URL: https://issues.apache.org/jira/browse/ARTEMIS-395 Project: ActiveMQ

[jira] [Reopened] (AMQ-6148) When use LDAP auth, Activemq should not always connect to ldap service to do authentication

[ https://issues.apache.org/jira/browse/AMQ-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully reopened AMQ-6148: - looks like we could pull back the fix from artemis for this. I don't see any reason why we cannot cache the

[jira] [Created] (AMQ-6164) queue sendLock prevents concurrent journal updates

Gary Tully created AMQ-6164: --- Summary: queue sendLock prevents concurrent journal updates Key: AMQ-6164 URL: https://issues.apache.org/jira/browse/AMQ-6164 Project: ActiveMQ Issue Type:

[jira] [Resolved] (AMQ-6164) queue sendLock prevents concurrent journal updates

[ https://issues.apache.org/jira/browse/AMQ-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully resolved AMQ-6164. - Resolution: Fixed multiple producers on a single destination can now get the benefit of write batching to

[jira] [Created] (AMQ-6163) ActiveMQ creates a new empty KahaDB

Björn Paulsen created AMQ-6163: -- Summary: ActiveMQ creates a new empty KahaDB Key: AMQ-6163 URL: https://issues.apache.org/jira/browse/AMQ-6163 Project: ActiveMQ Issue Type: Bug

[jira] [Commented] (AMQ-6164) queue sendLock prevents concurrent journal updates

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

[jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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

[jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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

[jira] [Commented] (ARTEMIS-395) Auto-delete JMS queues only if auto-delete-jms-queues = true

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

[jira] [Commented] (ARTEMIS-388) No obvious way to discover whether an embedded server actually started OK or not

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