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

Posted to commits@tomee.apache.org by "Matthew Broadhead (JIRA)" <ji...@apache.org> on 2016/03/09 14:16:40 UTC

[jira] [Resolved] (TOMEE-1722) Potential JMX memory leak

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

Matthew Broadhead resolved TOMEE-1722.
--------------------------------------
    Resolution: Not A Problem

i had included xalan-2.6.0 which has a known leak

> Potential JMX memory leak
> -------------------------
>
>                 Key: TOMEE-1722
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1722
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 1.7.2, 1.7.3
>            Reporter: Matthew Broadhead
>         Attachments: 2016-03-07 01.27.58 pm.png, 2016-03-08 10.39.09 am.png, jstack-20160303-1604.txt
>
>
> I have been trying to track down a memory leak on a production server.  Was 1.7.2 and is now 1.7.3.  I have run jvmtop and I get lots of threads with JMX Server Connection Timeout.  I have searched my projects and I never use JMX so is this something that is internal to TomEE?  I searched the error and it said that whenever a JMXConnector is used the close() function must be called at the end.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)