[
https://issues.apache.org/jira/browse/TOMEE-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179641#comment-15179641
]
Romain Manni-Bucau commented on TOMEE-1722:
-------------------------------------------
Depends your server config but the http can take easily 250, if you have some
timers then you got more, some asynchronous even more etc...108 sounds not that
much. Memory also depends the app, There are several caches which can fill
memory depending your app.
Side note about the datasource: the preferred way to configure one in tomee is
to use tomee.xml
> 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)
