You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2019/03/18 11:05:00 UTC

[jira] [Closed] (AMQ-7169) Java heap space And deadLock

     [ https://issues.apache.org/jira/browse/AMQ-7169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher L. Shannon closed AMQ-7169.
---------------------------------------
    Resolution: Not A Problem

The threads seems to be stuck on stopAsync and there was some work done in newer versions to fix some of those deadlock issues so you should upgrade.

For OOM take a look at [http://activemq.apache.org/javalangoutofmemory.html]

The out of memory issue is probably related to configuration and how you are using the broker and not a bug so you should use the users mailing list if you need help trying to figure out the OOM issue: [http://activemq.apache.org/mailing-lists.html]

I'm closing this for now as you most likely just need to upgrade and do some work to prevent OOM but if a real bug is found then this can be reopened.

 

> Java heap space And deadLock
> ----------------------------
>
>                 Key: AMQ-7169
>                 URL: https://issues.apache.org/jira/browse/AMQ-7169
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.14.3
>            Reporter: frank0417
>            Priority: Critical
>         Attachments: activemq.log, ems_mq_thead.log
>
>
> TransportConnection  have many Thread BLOCKED and LOCK  
>  Java heap space



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)