Your question is really more an issue of understanding EJB and not JBoss specifically.
When using commit option A, the container assumes exclusive "ownership" of the database so it can cache the data very aggresively. However, at no time does the cache contain incomplete writes to the database outside the scope of a transaction. The data in the cache is synchronized with the database and as such, the container can serve data to requesting clients without re-reading from the database. The flush() command simply invalidates the cache so when a request for that data comes in, the container will re-request the data from the database. The documentation makes this fairly clear. See this chapter of the on-line docs: http://docs.jboss.org/admin-devel/Chap11.html Specifically reference Commit Options here: http://docs.jboss.org/admin-devel/Chap11.html#0_pgfId-926545 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852985#3852985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852985 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
