[
https://issues.apache.org/jira/browse/TOMEE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew Broadhead updated TOMEE-1722:
-------------------------------------
Attachment: jstack-20160303-1604.txt
the processor got stuck at 100% again and TomEE had to be restarted. the issue
may not be TomEE but I wondered if you can see anything in this jstack that
might indicate the problem? it looks like some threads are blocked by not
being able to create a mysql object but when i restart everything is ok and
mysql doesn't need to be restarted
> 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: 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)
