|
From: Matthew V. <Mat...@EM...> - 2005-05-09 18:56:07
|
Hi, =20 I have recently upgraded to version 3.1.2 (from 2.2.3 I think) and I've run into a confusing problem. Despite the presence of the following properties in the .conf file, timeouts are occurring. The timeouts take approximately 5 minutes and iterate 5 times; on Unix-flavored machines this is a medium-sized problem, on Windows, this blocks Windows startup, adding 30 minutes to the blank screen before your typical user sees his login dialog. =20 Relevant properties: =20 wrapper.startup.timeout=3D0 wrapper.ping.timeout=3D0 =20 Log section: =20 ERROR | wrapper | 2005/05/03 14:52:22 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2005/05/03 14:52:22 | JVM did not exit on request, terminated STATUS | wrapper | 2005/05/03 14:52:27 | Launching a JVM... INFO | jvm 2 | 2005/05/03 14:52:30 | Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/>=20 INFO | jvm 2 | 2005/05/03 14:52:30 |=20 =20 I should mention that the extra information from setting wrapper.debug=3Dtrue hasn't provided any clues. I've also tried = switching the JVM (Sun/Jrockit) to no gain. I have double and triple-checked the formatting of the configuration file, as well as setting all of the timeout-related properties to 0 (disabled). I haven't seen any similar bugs/issues posted, so I'm a bit concerned. =20 If anyone has any suggestions/solutions, I would be forever in your debt. =20 Thanks, Matt |