[jira] [Reopened] (AMQ-5250) temp queue not working after long run of activemq

[ https://issues.apache.org/jira/browse/AMQ-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rural Hunter reopened AMQ-5250: --- No it's definitely not normal behavior. This happened again after my activemq 5.10.0 running for about 2 m

[jira] [Commented] (AMQ-5338) Run into Memory Leak problem after upgrade from 5.5.1 to 5.10

[ https://issues.apache.org/jira/browse/AMQ-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114759#comment-14114759 ] Edwin Wang commented on AMQ-5338: - I have use JConsole to monitor the OOM problem and found

[jira] [Commented] (AMQ-5331) Memory Leak releated to TempQueues and JaasAuthenticationBroker.JaasSecurityContext

[ https://issues.apache.org/jira/browse/AMQ-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114756#comment-14114756 ] Edwin Wang commented on AMQ-5331: - Looks like similar problem for issue 5338 I just opened.

[jira] [Created] (AMQ-5338) Run into Memory Leak problem after upgrade from 5.5.1 to 5.10

Edwin Wang created AMQ-5338: --- Summary: Run into Memory Leak problem after upgrade from 5.5.1 to 5.10 Key: AMQ-5338 URL: https://issues.apache.org/jira/browse/AMQ-5338 Project: ActiveMQ Issue Type:

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Performance Test Plugin #1043

See -- [INFO] [INFO]

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1043

See Changes: [dejan] https://issues.apache.org/jira/browse/AMQ-5305 - modify element with runtime configuration plugin -- [...truncated 14739 lines...] [JENKINS] Archiving

[jira] [Closed] (AMQNET-461) FailoverTransport PoisonAcks Rollbacked messages

[ https://issues.apache.org/jira/browse/AMQNET-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQNET-461. --- Resolution: Cannot Reproduce Assignee: Timothy Bish (was: Jim Gomes) Attempted to reproduce wi

[jira] [Resolved] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQNET-471. - Resolution: Fixed Fixed on trunk and 1.6.x branch. The separate rollback call in the exception

[jira] [Updated] (AMQNET-471) Synchronous message consumer will lose a message that failed to commit whilst the broker was unavailable

[ https://issues.apache.org/jira/browse/AMQNET-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQNET-471: Fix Version/s: 1.7.0 1.6.4 > Synchronous message consumer will lose a message th

[jira] [Resolved] (AMQ-5305) runtime configuration - allow changes to configuration elements

[ https://issues.apache.org/jira/browse/AMQ-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-5305. Resolution: Fixed Fix Version/s: 5.11.0 This is now fixed on trunk with http://git-wip-us.apa

[jira] [Assigned] (AMQ-5305) runtime configuration - allow changes to configuration elements

[ https://issues.apache.org/jira/browse/AMQ-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-5305: -- Assignee: Dejan Bosanac > runtime configuration - allow changes to configuration elements >

[jira] [Created] (AMQ-5337) Bug in ConcurrentLinkedQueue leads to excessive CPU-consumption by ActiveMQ process

Wawan created AMQ-5337: -- Summary: Bug in ConcurrentLinkedQueue leads to excessive CPU-consumption by ActiveMQ process Key: AMQ-5337 URL: https://issues.apache.org/jira/browse/AMQ-5337 Project: ActiveMQ