[jboss-jira] [JBoss JIRA] (WFLY-6506) Session EJB no pooling in WildFly 9.0.2.final

[Ralph Soika (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190298#comment-13190298 ] 

Ralph Soika commented on WFLY-6506:
-----------------------------------

ok you are right, I have overseen this. 

As the settings for pooling are now part of the default configuration in Wildfly 10.0.0.Final there will also in the future no need to manually change the EJB settings. 

Thanks 

> Session EJB no pooling in WildFly 9.0.2.final
> ---------------------------------------------
>
>                 Key: WFLY-6506
>                 URL: https://issues.jboss.org/browse/WFLY-6506
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 9.0.2.Final
>            Reporter: Ralph Soika
>
> 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 : 
> {code:java}
>   <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>  
> .......  
> {code}
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)