[
https://issues.jboss.org/browse/AS7-6778?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-6778:
----------------------------------
The reason you see 90% of CPU cycles being spent in JBossThread.run() is that nearly all
of our threads are JBossThreads, thus all work that the server does will ultimately show
up as being in this method one way or another. It is not indicative of a problem - indeed
if you saw 0% usage in JBossThread.run(), it would mean that the server isn't doing
anything at all.
Configure EJB3/MDB with an individual thread pool for each EJB.
---------------------------------------------------------------
Key: AS7-6778
URL:
https://issues.jboss.org/browse/AS7-6778
Project: Application Server 7
Issue Type: Feature Request
Components: EJB
Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
Reporter: Jeremy Whiting
Assignee: jaikiran pai
For performance of an application to be scalable I need to configure sometimes a thread
pool to an EJB. The pool is not shared with other EJB in the deployed application.
For example
PoolA - EJB Dog
PoolB - EJB Cat
To configure this the ability no define the thread pool name for an EJB. Rather than an
EJB to the shared thread pool as it currently works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira