[jboss-jira] [JBoss JIRA] Commented: (JBAS-9356) Move the ejb3-async-deployer-jboss-beans.xml out of the jar so that it can be configured by users
[
https://issues.jboss.org/browse/JBAS-9356?page=com.atlassian.jira.plugin....
]
Daniel Bevenius commented on JBAS-9356:
---------------------------------------
Jaikiran wrote:
bq.Daniel, a easier fix to this issue would be to copy the
ejb3-async-deployer-jboss-beans.xml into JBOSS_HOME/server/<servername>/deployers
folder and move the jboss-ejb3-async-deployer.jar completely to JBOSS_HOME/common/lib
folder (You don't have to remove the ejb3-async-deployer-jboss-beans.xml from that
jar). I'm on IRC, if you want to have a quick chat.
Ah, that would make things easier. I'll jump onto IRC. Thanks
Move the ejb3-async-deployer-jboss-beans.xml out of the jar so that
it can be configured by users
--------------------------------------------------------------------------------------------------
Key: JBAS-9356
URL: https://issues.jboss.org/browse/JBAS-9356
Project: Legacy JBoss Application Server 6
Issue Type: Task
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Reporter: jaikiran pai
Assignee: Daniel Bevenius
Labels: open_to_community
Fix For: 6.1.0, Open To Community
Currently the number of threads used by the ExecutorService for Async invocations on EJBs
is configured within a jar
JBOSS_HOME/server/<servername>/deployers/jboss-ejb3-async-deployer.jar/META-INF/ejb3-async-deployer-jboss-beans.xml
making it difficult for users to configure (see the referenced forum thread for details).
It would be better to move it outside the jar so that it can easily be configured by
users.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira