I expected a "spanking" for doing that, but I need updated state info and it did the trick.
I did isolate it so that the referenced tokens are in their own hibernate session and closed the session afterwords. Nothing is broken in this case. I need the state refreshed in the join and since I am in an object inside the session (join), I can't simply reload the objects (tried that, failed miserably). This is equivalent to taking a peak in the database to get an accurate snapshot of what is going on (my states all commit state on a node by node basis so that I can peak around and see what is going on). This business of not saving state until the entire process is complete will not work for nodes that are long running. I also needed the ability to monitor the process externally, so the state had to be saved... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911870#3911870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911870 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
