[
https://issues.apache.org/jira/browse/TOMEE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175513#comment-15175513
]
Matthew Broadhead commented on TOMEE-1722:
------------------------------------------
jstack shows this sort of stuff
{noformat}
"JMX server connection timeout" 2627 #2627 daemon prio=9 os_prio=0
tid=0x00007f939e29e800 nid=0x364e in Object.wait() [0x00007f9372914000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at
com.sun.jmx.remote.internal.ServerCommunicatorAdmin$Timeout.run(ServerCommunicatorAdmin.java:168)
- locked <0x00000007336ed9e0> (a [I)
at java.lang.Thread.run(Thread.java:745)
Abandoned connection cleanup thread #11 daemon prio=5 os_prio=0
tid=0x00007f9418947000 nid=0x76d8 in Object.wait() [0x00007f9402f5b000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
- locked <0x000000070819bb28> (a java.lang.ref.ReferenceQueue$Lock)
at
com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)
{noformat}
i call JAX-WS and JAX-RS services. would they use JMX connector inside?
> 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)
