-
Bug
-
Resolution: Done
-
Major
-
None
-
9.0.2.Final
-
None
-
-
Compatibility/Configuration, User Experience
After doing some perfomance tests on wildfly 9.0.2.final I recognized that stateless session ejbs are no longer pooled even if the pool settings in standalone.xml are correct. See the following example :
<subsystem xmlns="urn:jboss:domain:ejb3:3.0"> <session-bean> <stateful default-access-timeout="5000" cache-ref="simple" passivation-disabled-cache-ref="simple"/> <singleton default-access-timeout="5000"/> </session-bean> <pools> <bean-instance-pools> <strict-max-pool name="slsb-strict-max-pool" max-pool-size="32" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/> </bean-instance-pools> </pools> .......
This issue is also discussed in wildfly forum:
https://developer.jboss.org/message/954200#954200
In Widfly 8.0 there was the configuration missing. Now the configuration is added. But it had no effect.
- is caused by
-
WFLY-3650 Pooling EJB Session Beans per default
- Closed