Hi there, I have set my entity beans up to use Commit option D with a refresh period of 180 seconds. Application runs on a single server version 3.2.3.
Could someone please explain the following behaviour for me? I access a bean via a finder. If I look at jmx-console it shows that 1 bean is in the pool and not the cache. I access the same bean via the finder. Jmx-console now shows that 1 bean in the cache and not in pool anymore. Once the 180 seconds pass, the bean moves from the cache to the pool. Do this mean that the one in the pool will be reused as-is once the same data is looked up again? Another thing is the following: I lookup the bean via the finder. I change one of the string fields to null in the database directly. Somehow this bean now updates immediately and not after the 180 seconds. I change the string field back to having a value. Now the bean takes the 180 seconds to update. Regards, -- Alwyn Schoeman SMART Money Inc. If you're a SMARTY and you're using the better DNS connections, you can access my homepage at http://nevyn.smarties.com.ph/Members/alwyn. The other unlucky ones: http://10.126.68.24/myplone ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
