ERROR | wrapper | 2014/01/15 13:15:01 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2014/01/15 13:15:02 | JVM did not exit on request, terminated STATUS | wrapper | 2014/01/15 13:15:11 | Launching a JVM... ERROR | wrapper | 2014/01/15 13:15:47 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2014/01/15 13:15:47 | ADVICE | wrapper | 2014/01/15 13:15:47 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:15:47 | Advice: ADVICE | wrapper | 2014/01/15 13:15:47 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2014/01/15 13:15:47 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2014/01/15 13:15:47 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2014/01/15 13:15:47 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2014/01/15 13:15:47 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2014/01/15 13:15:47 | the Wrapper classes: ADVICE | wrapper | 2014/01/15 13:15:47 | com.visokio.ent.ServiceLaunch ADVICE | wrapper | 2014/01/15 13:15:47 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2014/01/15 13:15:47 | classes to make this initialization processes automatic. ADVICE | wrapper | 2014/01/15 13:15:47 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2014/01/15 13:15:47 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2014/01/15 13:15:47 | within the Wrapper: ADVICE | wrapper | 2014/01/15 13:15:47 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2014/01/15 13:15:47 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:15:47 | ERROR | wrapper | 2014/01/15 13:15:48 | JVM did not exit on request, terminated STATUS | wrapper | 2014/01/15 13:15:53 | Launching a JVM... ERROR | wrapper | 2014/01/15 13:16:39 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2014/01/15 13:16:39 | ADVICE | wrapper | 2014/01/15 13:16:39 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:16:39 | Advice: ADVICE | wrapper | 2014/01/15 13:16:39 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2014/01/15 13:16:39 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2014/01/15 13:16:39 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2014/01/15 13:16:39 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2014/01/15 13:16:39 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2014/01/15 13:16:39 | the Wrapper classes: ADVICE | wrapper | 2014/01/15 13:16:39 | com.visokio.ent.ServiceLaunch ADVICE | wrapper | 2014/01/15 13:16:39 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2014/01/15 13:16:39 | classes to make this initialization processes automatic. ADVICE | wrapper | 2014/01/15 13:16:39 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2014/01/15 13:16:39 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2014/01/15 13:16:39 | within the Wrapper: ADVICE | wrapper | 2014/01/15 13:16:39 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2014/01/15 13:16:39 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:16:39 | ERROR | wrapper | 2014/01/15 13:16:40 | JVM did not exit on request, terminated STATUS | wrapper | 2014/01/15 13:16:45 | Launching a JVM... ERROR | wrapper | 2014/01/15 13:17:24 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2014/01/15 13:17:24 | ADVICE | wrapper | 2014/01/15 13:17:24 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:17:24 | Advice: ADVICE | wrapper | 2014/01/15 13:17:24 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2014/01/15 13:17:24 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2014/01/15 13:17:24 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2014/01/15 13:17:24 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2014/01/15 13:17:24 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2014/01/15 13:17:24 | the Wrapper classes: ADVICE | wrapper | 2014/01/15 13:17:24 | com.visokio.ent.ServiceLaunch ADVICE | wrapper | 2014/01/15 13:17:24 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2014/01/15 13:17:24 | classes to make this initialization processes automatic. ADVICE | wrapper | 2014/01/15 13:17:24 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2014/01/15 13:17:24 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2014/01/15 13:17:24 | within the Wrapper: ADVICE | wrapper | 2014/01/15 13:17:24 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2014/01/15 13:17:24 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:17:24 | ERROR | wrapper | 2014/01/15 13:17:24 | JVM did not exit on request, terminated STATUS | wrapper | 2014/01/15 13:17:30 | Launching a JVM... ERROR | wrapper | 2014/01/15 13:18:06 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2014/01/15 13:18:06 | ADVICE | wrapper | 2014/01/15 13:18:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:18:06 | Advice: ADVICE | wrapper | 2014/01/15 13:18:06 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2014/01/15 13:18:06 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2014/01/15 13:18:06 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2014/01/15 13:18:06 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2014/01/15 13:18:06 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2014/01/15 13:18:06 | the Wrapper classes: ADVICE | wrapper | 2014/01/15 13:18:06 | com.visokio.ent.ServiceLaunch ADVICE | wrapper | 2014/01/15 13:18:06 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2014/01/15 13:18:06 | classes to make this initialization processes automatic. ADVICE | wrapper | 2014/01/15 13:18:06 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2014/01/15 13:18:06 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2014/01/15 13:18:06 | within the Wrapper: ADVICE | wrapper | 2014/01/15 13:18:06 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2014/01/15 13:18:06 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:18:06 | ERROR | wrapper | 2014/01/15 13:18:06 | JVM did not exit on request, terminated STATUS | wrapper | 2014/01/15 13:18:12 | Launching a JVM... ERROR | wrapper | 2014/01/15 13:18:50 | Startup failed: Timed out waiting for a signal from the JVM. ADVICE | wrapper | 2014/01/15 13:18:50 | ADVICE | wrapper | 2014/01/15 13:18:50 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:18:50 | Advice: ADVICE | wrapper | 2014/01/15 13:18:50 | The Wrapper consists of a native component as well as a set of classes ADVICE | wrapper | 2014/01/15 13:18:50 | which run within the JVM that it launches. The Java component of the ADVICE | wrapper | 2014/01/15 13:18:50 | Wrapper must be initialized promptly after the JVM is launched or the ADVICE | wrapper | 2014/01/15 13:18:50 | Wrapper will timeout, as just happened. Most likely the main class ADVICE | wrapper | 2014/01/15 13:18:50 | specified in the Wrapper configuration file is not correctly initializing ADVICE | wrapper | 2014/01/15 13:18:50 | the Wrapper classes: ADVICE | wrapper | 2014/01/15 13:18:50 | com.visokio.ent.ServiceLaunch ADVICE | wrapper | 2014/01/15 13:18:50 | While it is possible to do so manually, the Wrapper ships with helper ADVICE | wrapper | 2014/01/15 13:18:50 | classes to make this initialization processes automatic. ADVICE | wrapper | 2014/01/15 13:18:50 | Please review the integration section of the Wrapper's documentation ADVICE | wrapper | 2014/01/15 13:18:50 | for the various methods which can be employed to launch an application ADVICE | wrapper | 2014/01/15 13:18:50 | within the Wrapper: ADVICE | wrapper | 2014/01/15 13:18:50 | http://wrapper.tanukisoftware.org/doc/english/integrate.html ADVICE | wrapper | 2014/01/15 13:18:50 | ------------------------------------------------------------------------ ADVICE | wrapper | 2014/01/15 13:18:50 | ERROR | wrapper | 2014/01/15 13:18:50 | JVM did not exit on request, terminated FATAL | wrapper | 2014/01/15 13:18:50 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2014/01/15 13:18:50 | There may be a configuration problem: please check the logs. STATUS | wrapper | 2014/01/15 13:18:51 | <-- Wrapper Stopped