[
https://issues.apache.org/jira/browse/TOMEE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177937#comment-15177937
]
Romain Manni-Bucau commented on TOMEE-1722:
-------------------------------------------
Yep seems the pool is blocked, you can monitor it through JMX and likely on
your database too to identify the issue. Can be a misconfiguration of the pool.
Side note if it helps for tests: switching the DataSourceCreator you will use
commons-dbcp which has a logic a bit different from tomcat-jdbc so can help
validating it.
> 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)
