Noel Did you mean %JAMES_BASE%/logs/wrapper.log There was nothing in the %JAMES_BASE%/temp/ directory.
I found this which provides a bit more information. ERROR | wrapper | 2004/08/15 18:07:29 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:07:29 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:07:34 | Launching a JVM... INFO | wrapper | 2004/08/15 18:08:18 | Wrapper Process has not received any CPU time for 49 seconds. Extending timeouts. INFO | jvm 3 | 2004/08/15 18:08:38 | Wrapper (Version 2.2.8) INFO | jvm 3 | 2004/08/15 18:08:38 | INFO | jvm 3 | 2004/08/15 18:08:38 | INFO | jvm 3 | 2004/08/15 18:08:38 | Phoenix 4.0.1 INFO | jvm 3 | 2004/08/15 18:08:38 | INFO | jvm 3 | 2004/08/15 18:08:42 | James 2.2.0 INFO | jvm 3 | 2004/08/15 18:08:42 | Remote Manager Service started plain:4555 INFO | jvm 3 | 2004/08/15 18:08:42 | POP3 Service started plain:110 INFO | jvm 3 | 2004/08/15 18:08:43 | SMTP Service started plain:25 INFO | jvm 3 | 2004/08/15 18:08:43 | NNTP Service Disabled INFO | jvm 3 | 2004/08/15 18:08:43 | Fetch POP Disabled INFO | jvm 3 | 2004/08/15 18:08:43 | FetchMail Disabled ERROR | wrapper | 2004/08/15 18:15:15 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:15:15 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:15:20 | Launching a JVM... INFO | jvm 4 | 2004/08/15 18:15:36 | Wrapper (Version 2.2.8) INFO | jvm 4 | 2004/08/15 18:15:36 | ERROR | wrapper | 2004/08/15 18:15:46 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:15:46 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:15:51 | Launching a JVM... INFO | jvm 5 | 2004/08/15 18:15:53 | Wrapper (Version 2.2.8) INFO | jvm 5 | 2004/08/15 18:15:53 | ERROR | wrapper | 2004/08/15 18:16:17 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:16:17 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:16:22 | Launching a JVM... INFO | jvm 6 | 2004/08/15 18:16:23 | Wrapper (Version 2.2.8) INFO | jvm 6 | 2004/08/15 18:16:23 | ERROR | wrapper | 2004/08/15 18:16:48 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:16:48 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:16:53 | Launching a JVM... INFO | jvm 7 | 2004/08/15 18:16:54 | Wrapper (Version 2.2.8) INFO | jvm 7 | 2004/08/15 18:16:54 | ERROR | wrapper | 2004/08/15 18:17:19 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:17:19 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/15 18:17:24 | Launching a JVM... INFO | jvm 8 | 2004/08/15 18:17:25 | Wrapper (Version 2.2.8) INFO | jvm 8 | 2004/08/15 18:17:25 | ERROR | wrapper | 2004/08/15 18:17:50 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/15 18:17:50 | Java Virtual Machine did not exit on request, terminated FATAL | wrapper | 2004/08/15 18:17:50 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2004/08/15 18:17:50 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2004/08/15 18:17:51 | <-- Wrapper Stopped This would have all been going on when the Windows Server backup job was taking place. Something similar happened the day before, it just wasn't quite so serious. ERROR | wrapper | 2004/08/14 18:15:21 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2004/08/14 18:15:21 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2004/08/14 18:15:26 | Launching a JVM... INFO | jvm 2 | 2004/08/14 18:15:44 | Wrapper (Version 2.2.8) INFO | jvm 2 | 2004/08/14 18:15:44 | INFO | jvm 2 | 2004/08/14 18:15:44 | INFO | jvm 2 | 2004/08/14 18:15:44 | Phoenix 4.0.1 INFO | jvm 2 | 2004/08/14 18:15:44 | INFO | jvm 2 | 2004/08/14 18:16:08 | James 2.2.0 INFO | jvm 2 | 2004/08/14 18:16:08 | Remote Manager Service started plain:4555 INFO | jvm 2 | 2004/08/14 18:16:08 | POP3 Service started plain:110 INFO | jvm 2 | 2004/08/14 18:16:08 | SMTP Service started plain:25 INFO | jvm 2 | 2004/08/14 18:16:08 | NNTP Service Disabled INFO | jvm 2 | 2004/08/14 18:16:08 | Fetch POP Disabled INFO | jvm 2 | 2004/08/14 18:16:08 | FetchMail Disabled It beats me.... Regards Stephen -----Original Message----- From: Noel J. Bergman [mailto:[EMAIL PROTECTED] Sent: 18 August 2004 16:32 To: James Users List Subject: RE: James 2.2.0 Server crash The one "non-obvious" place to check is %JAMES_BASE%/temp/phoenix.console, which may have some additional error messages. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
