|
From: Leif M. <le...@ta...> - 2003-11-12 15:57:27
|
Todd, Looking at the wrapper.conf and the log file that you posted. I am actually stumped :-/ The JVM is timing out and being restarted because the WrapperManager class is never being initialized and is thus never contacting the Wrapper process. The thing that has be perplexed is how that could be happening if the WrapperSimpleApp class has been specified as the main class. The first thing that is does is to load the WrapperManager class. Normally you would see something like the following when the JVM is launched: STATUS | wrapper | 2003/11/13 20:48:33 | --> Wrapper Started as Console STATUS | wrapper | 2003/11/13 20:48:34 | Launching a JVM... INFO | jvm 1 | 2003/11/13 20:48:35 | Wrapper (Version 3.0.5) For some reason you are not getting the Wrapper version line. Could you please add the wrapper.debug=true property to your wrapper.conf and rerun your application. Then repost the resulting wrapper.log file for a single JVM invocation. Please send the wrapper.log and wrapper.conf files as unedited attachments So I can see exactly what you are doing. Cheers, Leif Todd Binns wrote: > Hi, > > I have read through the documentation and I think I have implemented > the WrapperSimpleApp correctly, but I it still errors with the: > > "Startup failed: Timed out waiting for signal from JVM." error. > Nothing less is running on the Laptop and the CPU is near 0. I had the > configuration file set for debug, but move the logging back to INFO. I > also went to the NoReturn sample, it is very close to my application > concept. I will have a while loop that is set to true and run like > that, checking the time to do things. I have a thread sleep just like > the sample. Since the sample fails as well I used it for my example > since you already know the code. Here is the conf file and the trap. I > have included as little as possible, let me know if you want more. I > am coding on a XP Pro laptop, the final application will be in Win2K > Server. > |