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

Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/03/02 13:12:18 UTC

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

    [ https://issues.apache.org/jira/browse/TOMEE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175498#comment-15175498 ] 

Romain Manni-Bucau commented on TOMEE-1722:
-------------------------------------------

Hi Matthew,

depends in which context. Normally by default TomEE doesn't activate remote JMX connectors.

> 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
>
> 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)