Thanks Ben. I was just counting on persistence between invocations of Java but that if the object itself timed out, it would disappear. If I call treecache.remove(), I assume it will be removed from the persistent store, so perhaps I should catch an event when the node is being timed out (and also run through all the nodes at startup).
Or, better yet: I still get the same timeouts if I add a je.properies to my WEB-INF/classes dir that contains je.lock.timeout=[LARGE NUMBER]. It seems to be ignored. Is there any way to crank up the timeouts for BDBJE? Thanks, Dan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916266#3916266 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916266 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
