You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Marco Bungart (Jira)" <ji...@apache.org> on 2022/11/17 22:03:00 UTC

[jira] [Updated] (ARTEMIS-4094) org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection with destroyed==true not destroyed

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

Marco Bungart updated ARTEMIS-4094:
-----------------------------------
    Issue Type: Bug  (was: New Feature)

> org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection with destroyed==true not destroyed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4094
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4094
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: OpenWire
>    Affects Versions: 2.26.0
>         Environment: Artemis, deployed through the official docker image in version {{2.26.0}} in an OpenShift cluster
>            Reporter: Marco Bungart
>            Priority: Major
>
> We observed through a heap dump that after OpenWire connections were closed, there were still {{org.apache.activemq.artemis.core.server.impl.ServerSessionImpl}}, that reference {{org.apache.activemq.artemis.core.protocol.openwire.OpenWireConnection}} s, which in turn have {{destroyed==true}}.
> In the long this, we suspect that this is the core issue of a memory leak we are currently observing.
> I have a heap dump that we could share, showing the accumulated objects. the dump is about 90 MB in size If this would be helpful to have, please let me know.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)