Access intent for CMP Entity EJB is only a hint for bean behavior when using wsOptimisticRead
 Technote (troubleshooting)
 
Problem(Abstract)
When wsOptimisticRead has an access intent set to Read, the Enterprise Java™ Bean (EJB) follows this hint, unless the bean must perform a non-read action in the transaction.

Access intent is only a hint. If the business application code does not adhere to this hint, the container changes the access intent internally and automatically to be able to carry out the required tasks.
 
Cause
Access intent wsOptimisticRead is set to Read and the bean is asked to do updates in the same transaction as the reads by having the beans update method called. This made the ejbStore() method appear in SystemOut.log. Performance is degraded.
 
Resolving the problem
When coding the business application, place only the Read components in transactions, and if update is required of the bean, place that in a separate transaction. When coding, be aware that updates utilize more resources than reads, and lay out the business application accordingly.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > EJB Container
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1165865
IBM Group: Software Group
Modified date: Dec 7, 2006