[jboss-jira] [JBoss JIRA] (AS7-6395) EJB2 CMP - no entity-bean instance pool configured in *full* profiles with cmp

[Stuart Douglas (JIRA)]

     [ https://issues.jboss.org/browse/AS7-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart Douglas resolved AS7-6395.
---------------------------------

    Resolution: Rejected


We don't really want to encourage people to use this, until we have a pool that better suits the CMP use case. 

Any pool that has a strict upper limit has a chance of deadlocking if to many beans are loaded, so we would first need a pool that does not have hard limits. 

In general GC overhead will be significantly smaller than concurrency overhead introduced by the pool the only time that a pool should provide significant gains is when setEntityContext() does something expensive, which does not seem to be very common. 



                
> EJB2 CMP - no entity-bean instance pool configured in *full* profiles with cmp
> ------------------------------------------------------------------------------
>
>                 Key: AS7-6395
>                 URL: https://issues.jboss.org/browse/AS7-6395
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Wolf-Dieter Fink
>            Assignee: Wolf-Dieter Fink
>            Priority: Minor
>              Labels: cmp, ejb2, pool, pooling
>
> The ejb3 subsystem does not configure entity-bean.bean-instance-pool.
> In that case the CMP subsystem must create a instance for each entity if it is used.
> This might be a performance issue (instantiation and GC), also the setContext/unsetContext methods must be called.

--
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