[
https://issues.jboss.org/browse/AS7-6079?page=com.atlassian.jira.plugin.s...
]
Abhi Datt commented on AS7-6079:
--------------------------------
Thanks Fink,
Do you mean to say that in the fixed version the IPT is available?
As when we ported our EJB 2.1 app to JBoss 7.1.1 (from 6.1) we experienced that our
database activity has increased 3 times and in the debug mode it was evident that there is
no caching available for EJBs. For every method call it hits DB which was not the case
earlier. This has resulted in an overall degradation of over 70% of our application in
comparison to JBoss AS 6.1.
Do you think this fix covers this issue
Thanks again.
EJB 2.1 CMP configuration options missing (sync-on-commit-only,
insert-after-ejb-post-create, call-ejb-store-on-clean)
----------------------------------------------------------------------------------------------------------------------
Key: AS7-6079
URL:
https://issues.jboss.org/browse/AS7-6079
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.0.Alpha1, 7.1.3.Final (EAP)
Reporter: Brad Maxwell
Assignee: Brad Maxwell
Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
In JBoss AS 7, EJB 2.1 CMP beans cannot configure some options such as
sync-on-commit-only and insert-after-ejb-post which were configurable in previous versions
of JBoss.
Should also confirm how to configure the rest of the options that were available
previously.
<container-configuration>
<container-name>Clustered CMP 2.x EntityBean</container-name>
<call-logging>false</call-logging>
<invoker-proxy-binding-name>clustered-entity-rmi-invoker</invoker-proxy-binding-name>
<sync-on-commit-only>false</sync-on-commit-only>
<insert-after-ejb-post-create>false</insert-after-ejb-post-create>
<container-interceptors>
...
</container-interceptors>
<instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
<instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
<persistence-manager>org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager</persistence-manager>
<locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
<container-cache-conf>
<cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
<cache-policy-conf>
<min-capacity>50</min-capacity>
<max-capacity>1000000</max-capacity>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period>
<max-cache-miss-period>60</max-cache-miss-period>
<min-cache-miss-period>1</min-cache-miss-period>
<cache-load-factor>0.75</cache-load-factor>
</cache-policy-conf>
</container-cache-conf>
<container-pool-conf>
<MaximumSize>100</MaximumSize>
</container-pool-conf>
<commit-option>B</commit-option>
</container-configuration>
--
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