There will never be a situation where I will span multiple nodes without saving state.
To me, each node is a step in a job. In that light, it is critical to know exactly where the process is so that work is not done twice in case of a power / machine failure. The first node might pick up a file. It might span three asynch processes to process that file differently. After the join, a report may be produced. I need to be able to monitor exactly where everything is and provide the facility to restart a job, step, or pause all jobs if need be. This requires me to save state 2 times in each node: upon entry and after the work is complete. The nice thing is that I can later build an issue tracking system with jBPM as well and have one place that holds all our business processes, both batch, and issue management. This moves us close to a "BAM" (I hate that term) / Dashboard solution where we can see everything that is going on in our business and monitor it realtime. Without accurate node persistance, I do not see how this is possible. you asked... Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3912745#3912745 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3912745 ------------------------------------------------------- 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
