|
An archive search revealed several messages regarding use of the JBoss application server on the iSeries. I have been trying to use JBoss under V5R1 with some success, but I have a problem: shutdown. I can get JBoss to run, but when I attempt to shut it down by using SysReq-2, it immediately terminates the JVM as well as JBoss. Because the JVM is terminated immediately, the JBoss shutdown hooks are not executed. Therefore the shutdown is not controlled, cleanup tasks are not performed, shutdown messages are not written to the log files, etc. I fear that repeated "hard shutdowns" would destroy the integrity of the JBoss system, precluding its use for mission critical work. Has anyone else encountered this shutdown problem and solved it? Is there a way to shut down JBoss properly under OS/400, perhaps using an API or some other operator interface? IBM investigated this issue and after several months, they replied that JBoss should be using a different shutdown technique and that no fix would be produced because the real problem is the way JBoss is coded. I am relatively new to java and the programming details are beyond me, but IBM quotes a Sun document that seems to support their assertion. The explanation is contained in the following APAR: http://www-912.ibm.com/n_dir/nas4apar.NSF/c79815e083182fec862564c00079d117/b 89ec0daa9e1d43486256c6400426f0a Any help would be greatly appreciated. THANK YOU, -Marty
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.