|
From: Greg&Frederique <gre...@tp...> - 2005-02-10 06:28:02
|
Quartz and "Timed out waiting for JVM Signal" Hi, BACKGROUND - I have a java applicaiton which uses Quartz for scheduling (refer http://sourceforge.net/projects/quartz/). Basically the application starts and registeres jobs/triggers. I'm not sure what the JVM/Quartz is doing whilst waiting for the next trigger, however I noted that when I run my application in a windows console that once the schedule is setup, and waiting for the first event, that I can't control-c to kill the JVM session/CMD window. I do also use a "thisThread.sleep(lengthSecs * 1000);" at one point within my applicaiton too. ISSUE When I lauch my application (headless) using the Method 1 integration I get a "Startup failed: Timed out waiting for a signal from the JVM" from the wrapper application. It then starts another JVM session. I also note if I set my first quartz trigger to occur quite quickly, that the wrapper application does correctly start my application, however half way through the 2nd quartz trigger (20 seconds or so in) I still get the "Startup failed: Timed out waiting for a signal from the JVM". It is as if, whilst my application is working, that the wrapper application at no time is getting the impression the JVM is responding. QUESTIONS Does the Wrapper application has constraints on the type of java application it runs? (e.g. no use of "thisThread.sleep(z);", or Quartz) How do I ensure the wrapper application obtains the view that the JVM is working correctly in my situation? Cheers Greg |