tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Romain Manni-Bucau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TOMEE-1722) Potential JMX memory leak
Date Wed, 02 Mar 2016 12:34:18 GMT

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

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

TomEE doesnt open remote (RMI here I think) JMX connector so it should be a setup on your
JVM.

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

Mime
View raw message