[jira] [Assigned] (AMQ-4906) advisory producerCount = 0 is not received on temporary queue

[ https://issues.apache.org/jira/browse/AMQ-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-4906: --- Assignee: Rob Davies advisory producerCount = 0 is not received on temporary queue

[jira] [Resolved] (AMQ-4906) advisory producerCount = 0 is not received on temporary queue

[ https://issues.apache.org/jira/browse/AMQ-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-4906. - Resolution: Fixed Fix Version/s: 5.10.0 advisory producerCount = 0 is not received on temporary

[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart

[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834800#comment-13834800 ] Tamilmaran commented on AMQ-4682: - By using this configuration can we change the port of

Jenkins build is back to normal : ActiveMQ-Trunk-Deploy » ActiveMQ :: All JAR bundle #891

See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/org.apache.activemq$activemq-all/891/

Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1424

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-mqtt/1424/

[jira] [Commented] (AMQ-4682) runtime configuration - allow selective application of changes to xml configuration without broker restart

[ https://issues.apache.org/jira/browse/AMQ-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834910#comment-13834910 ] Gary Tully commented on AMQ-4682: - @tamilmaran - not at the moment. Please open an

[jira] [Updated] (AMQ-4882) LevelDB can get to a corrupt state

[ https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remo Gloor updated AMQ-4882: Attachment: (was: TestClient.zip) LevelDB can get to a corrupt state

[jira] [Updated] (AMQ-4882) LevelDB can get to a corrupt state

[ https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remo Gloor updated AMQ-4882: Attachment: TestClient.zip LevelDB can get to a corrupt state --

[jira] [Commented] (AMQ-4837) LevelDB corrupted in AMQ cluster

[ https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834918#comment-13834918 ] Remo Gloor commented on AMQ-4837: - https://issues.apache.org/jira/browse/AMQ-4882 is the

[jira] [Created] (AMQ-4907) kahadb - do some sanity check on the index when checkForCorruptJournalFiles

Gary Tully created AMQ-4907: --- Summary: kahadb - do some sanity check on the index when checkForCorruptJournalFiles Key: AMQ-4907 URL: https://issues.apache.org/jira/browse/AMQ-4907 Project: ActiveMQ

[jira] [Updated] (AMQ-4889) ProxyConnector memory usage skyrockets when several ssl handshakes fails

[ https://issues.apache.org/jira/browse/AMQ-4889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] matteo rulli updated AMQ-4889: -- Attachment: AMQ-4889-patch__5.9.0.txt I attached a possible patch. As long as I can see, the problem was