|
From: Andy B. <aba...@ca...> - 2003-04-22 04:57:01
|
I followed the instructions regarding the "wrapper.filter" properties at < http://wrapper.tanukisoftware.org/doc/english/prop-filter-x-n.html > and added these to my wrapper.conf: > wrapper.filter.trigger.1=java.lang.NullPointerException > wrapper.filter.action.1=RESTART > wrapper.filter.trigger.2=java.lang.OutOfMemoryError > wrapper.filter.action.2=RESTART Now my application is restarted appropriately when a NPE occurs; however, I don't think this is a robust enough solution for my situation. If my application's main thread dies due to any exception, I need the Wrapper to restart it. I don't think I can express that completely with wrapper.filter properties. Do I have other options? Cheers, ~Andy On Monday, April 21, 2003, at 11:40 PM, Andy Barnett wrote: > In my testing on Linux I set up a Java application to throw a > NullPointerException. I expected the Java Service Wrapper to restart > my Java application, but instead the Wrapper just stops, apparently > exiting normally. > > Here is the end of my debug log: > >> [. . .] > > Here is my setup: I have coded a CmtkWrapper class that implements > WrapperListener using Integration Method #3 as described on the > website. My CmtkWrapper class starts my ChangeManagementToolkit class > which extends ReThread which extends the java.lang.Thread class. So > essentially I'm throwing a NPE from within the run() method of a > java.lang.Thread. > > As I said, I expected the Java Service Wrapper to restart my Java > application. Am I doing something wrong or am I misunderstanding what > the appropriate behavior should be? > > ~Cheers, > Andy |