[jboss-jira] [JBoss JIRA] (AS7-6395) EJB2 CMP - no entity-bean instance pool configured in *full* profiles with cmp
[
https://issues.jboss.org/browse/AS7-6395?page=com.atlassian.jira.plugin.s...
]
Wolf-Dieter Fink commented on AS7-6395:
---------------------------------------
As the only available pool implementation is a 'strict-max' pool the max-pool-size
must big enough to handle the number of entities (same type) that can be used at the same
time.
- the number of entities as result of a findBy or CMR
multiplied by
- the number of concurrent running threads with the same entity
Otherwise a thread might be blocked for a while (until instance-acquisition-timeout) and
that end in a worse performance, or if the number of entities in the same thread is above
max-pool-size the use-case will never run successful.
You might see "parking to wait for <0x00??????> (a
java.util.concurrent.Semaphore$FairSync)" in a thread dump.
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