I have specified all get* methods of my Entity Bean to be "read-only" through the following tag in the jboss.xml.
<method-attributes> | <method> | <method-name>get*</method-name> | <read-only>true</read-only> | </method> | </method-attributes> Now, I access the getCustomerId of such an entity bean instance from an MDB that is enrolled in a "Required" type CMT. The transaction rolls back due to a timeout. However, that entity bean instance seems to be locked, when the MDB tries to re-process the message. I am of the opinion that read-only methods will release transactional locks at the end of the invocation. I am not sure why it holds up when the transaction rolls back. Can anyone throw some light? Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871957#3871957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871957 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
