[
https://issues.apache.org/jira/browse/AMQ-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115007#comment-14115007
]
Marcus Abels commented on AMQ-5331:
-----------------------------------
This bug can be fixed by removing
org.apache.activemq.security.SecurityContext.authorizedReadDests and
org.apache.activemq.security.SecurityContext.authorizedWriteDests and all
references on it, since this data seems not to be used for anything.
Or you simply change the code to not aggregate temp queues in this fields, e.g.:
// PATCH do not add temp queues since it produces a memory leak
if (!destination.isTemporary()) {
securityContext.getAuthorizedReadDests().put(destination,
destination);
}
In our production environment with a network of brokers setup the problem
occurs after 3 to 4 weeks. Actually, it manifests in constantly rising CPU and
HEAP utilization. The Broker dies with weird behavior even before an
OutOfMemoryError even occurs.
> Memory Leak releated to TempQueues and
> JaasAuthenticationBroker.JaasSecurityContext
> -----------------------------------------------------------------------------------
>
> Key: AMQ-5331
> URL: https://issues.apache.org/jira/browse/AMQ-5331
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0, 5.10.0
> Reporter: Marcus Abels
> Priority: Critical
>
> When using temporary reply queues and JAAS Authentication Plugin ActiveMQ
> aggregates fast amounts of references to ActiveMQTempQueue via
> org.apache.activemq.security.JaasAuthenticationBroker$JaasSecurityContext.authorizedReadDests
> and
> org.apache.activemq.security.JaasAuthenticationBroker$JaasSecurityContext.authorizedWriteDests
--
This message was sent by Atlassian JIRA
(v6.2#6252)
