[
https://issues.jboss.org/browse/WFLY-238?page=com.atlassian.jira.plugin.s...
]
Eduardo Martins edited comment on WFLY-238 at 6/12/13 10:56 AM:
----------------------------------------------------------------
Well, I'm gonna revert my opinion, not going to use threads subsystem at all, made a
PoC with one of the executors and doesn't look good at all, so I'm now going in
the same direction as David.
I'm considering something like this:
{code:xml}
<subsystem xmlns="urn:jboss:domain:ee:2.0" >
<global-modules>
<module name="org.jboss.logging" slot="main"/>
<module name="org.apache.log4j" annotations="true"
meta-inf="true" services="false"/>
</global-modules>
<ear-subdeployments-isolated>${test-exp:true}</ear-subdeployments-isolated>
<spec-descriptor-property-replacement>${test-exp1:false}</spec-descriptor-property-replacement>
<jboss-descriptor-property-replacement>${test-exp2:false}</jboss-descriptor-property-replacement>
<concurrent>
<default-managed-thread-factory
group-name="wildfly-ee-concurrent-threads" thread-name-pattern="%G %i"
priority="5"/>
<default-managed-executor-service>
<max-threads count="25"/>
<keepalive-time time="5" unit="seconds"/>
</default-managed-executor-service>
<default-managed-scheduled-executor-service>
<max-threads count="10"/>
<keepalive-time time="3" unit="seconds"/>
</default-managed-scheduled-executor-service>
</concurrent>
</subsystem>
{code}
Thoughts?
PS: Almost done with WFLY-237, which means soon we have jsr 236 fully working.
was (Author: emmartins):
Well, I'm gonna revert my opinion, not going to use threads subsystem at all, made
a PoC with one of the executors and doesn't look good at all, so I'm now going in
the same direction as David.
I'm considering something like this:
{code:xml}
<subsystem xmlns="urn:jboss:domain:ee:2.0" >
<global-modules>
<module name="org.jboss.logging" slot="main"/>
<module name="org.apache.log4j" annotations="true"
meta-inf="true" services="false"/>
</global-modules>
<ear-subdeployments-isolated>${test-exp:true}</ear-subdeployments-isolated>
<spec-descriptor-property-replacement>${test-exp1:false}</spec-descriptor-property-replacement>
<jboss-descriptor-property-replacement>${test-exp2:false}</jboss-descriptor-property-replacement>
<concurrent>
<default-managed-thread-factory
group-name="wildfly-ee-concurrent-threads" thread-name-pattern="%G %i"
priority="5"/>
<default-managed-executor-service>
<max-threads count="25"/>
<keepalive-time time="5" unit="seconds"/>
<shared>true</shared>
</default-managed-executor-service>
<default-managed-scheduled-executor-service>
<max-threads count="10"/>
<keepalive-time time="3" unit="seconds"/>
<shared>true</shared>
</default-managed-scheduled-executor-service>
</concurrent>
</subsystem>
{code}
Thoughts?
PS: Almost done with WFLY-237, which means soon we have jsr 236 fully working.
Thread pool configuration in EE subsystem
-----------------------------------------
Key: WFLY-238
URL:
https://issues.jboss.org/browse/WFLY-238
Project: WildFly
Issue Type: Sub-task
Components: EE
Reporter: David Lloyd
Assignee: Eduardo Martins
Fix For: 8.0.0.Alpha2
The EE subsystem should allow for thread pool configurations which are named and bound
into JNDI.
By default the binding name should probably not impinge upon standard namespaces. A good
default name would be {{java:jboss/threadpool/xxx}}.
--
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