[
https://issues.jboss.org/browse/AS7-6778?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-6778:
-----------------------------------
I'm sorry, I'm still not sure what's being asked for here.
> Furthermore, the thread pools could be assigned to specific
components, otherwise they will use the default one.
I don't understand this. Local invocations will keep using the originating thread.
Assigning a thread pool to a component wouldn't have any affect on that.
> We are having some bottleneck when increasing the threads for
each components.
I think we should start looking at what those problems are and then figure out if adding
some new feature is relevant.
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