freeing up resources when application gets killed
I have a banking application which continuously logs the details of user transactions. Suppose my application gets killed in between a transaction, what happens to the logging part? Can I stop the logging of this current transaction or will the transaction be logged till the application gets killed (half of the transaction gets logged)
Sheriff
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Ranch Hand
I see that you want the details of the transaction in the log, but it would also apear that you want to discard the details of failed transactions. If that is the case then you might consider buffering the details, and then logging it all after successful completion. It kinda boils down to what you want logged for successful transactions, and what you want logged for failed transactions.
Howard Kushner<br />IBM Certified Enterprise Developer - WebSphere Studio Application Developer V5.0<br />IBM Certified Advanced System Administrator - WebSphere Application Server V5.0<br />IBM Certified Solution Developer - Web Services with WebSphere Studio V5.1<br /><a href="http://www.amazon.com/exec/obidos/tg/detail/-/1931182108/" target="_blank" rel="nofollow">Developing J2EE Applications with WebSphere Studio</a> my Certification Study Guide for IBM Test 287
| It is sorta covered in the JavaRanch Style Guide. |