Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2014/09/23 14:02:00 | --> Wrapper Started as Daemon
- 2014/09/23 14:02:00 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:02:00 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:02:00 | http://wrapper.tanukisoftware.com
- 2014/09/23 14:02:00 |
- 2014/09/23 14:02:00 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:00 | Launching a JVM...
- 2014/09/23 14:02:00 | JVM exited while loading the application.
- 2014/09/23 14:02:00 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:02:00 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:02:00 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:02:00 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:02:00 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:02:00 | wrapper |
- 2014/09/23 14:02:00 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:00 | wrapper | Launching a JVM...
- 2014/09/23 14:02:00 |
- 2014/09/23 14:02:00 | ------------------------------------------------------------------------
- 2014/09/23 14:02:00 | Advice:
- 2014/09/23 14:02:00 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:00 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:00 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:00 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:00 | variables are correctly defined for the current environment.
- 2014/09/23 14:02:00 | ------------------------------------------------------------------------
- 2014/09/23 14:02:00 |
- 2014/09/23 14:02:09 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | Launching a JVM...
- 2014/09/23 14:02:10 | JVM exited while loading the application.
- 2014/09/23 14:02:10 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:02:10 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:02:10 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:02:10 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:02:10 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:02:10 | wrapper |
- 2014/09/23 14:02:10 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | wrapper | Launching a JVM...
- 2014/09/23 14:02:10 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:02:10 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:02:10 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:02:10 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:02:10 | jvm 1 | wrapper |
- 2014/09/23 14:02:10 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 14:02:10 | wrapper |
- 2014/09/23 14:02:10 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:10 | wrapper | Advice:
- 2014/09/23 14:02:10 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:10 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:10 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:10 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:02:10 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:10 | wrapper |
- 2014/09/23 14:02:10 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | wrapper | Launching a JVM...
- 2014/09/23 14:02:10 |
- 2014/09/23 14:02:10 | ------------------------------------------------------------------------
- 2014/09/23 14:02:10 | Advice:
- 2014/09/23 14:02:10 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:10 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:10 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:10 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:10 | variables are correctly defined for the current environment.
- 2014/09/23 14:02:10 | ------------------------------------------------------------------------
- 2014/09/23 14:02:10 |
- 2014/09/23 14:02:19 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:19 | Launching a JVM...
- 2014/09/23 14:02:19 | JVM exited while loading the application.
- 2014/09/23 14:02:19 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:02:19 | e correctly defined for the current environment.
- 2014/09/23 14:02:19 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:19 | wrapper |
- 2014/09/23 14:02:19 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:19 | wrapper | Launching a JVM...
- 2014/09/23 14:02:19 |
- 2014/09/23 14:02:19 | ------------------------------------------------------------------------
- 2014/09/23 14:02:19 | Advice:
- 2014/09/23 14:02:19 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:19 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:19 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:19 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:19 | variables are correctly defined for the current environment.
- 2014/09/23 14:02:19 | ------------------------------------------------------------------------
- 2014/09/23 14:02:19 |
- 2014/09/23 14:02:28 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | Launching a JVM...
- 2014/09/23 14:02:29 | JVM exited while loading the application.
- 2014/09/23 14:02:29 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:02:29 | e correctly defined for the current environment.
- 2014/09/23 14:02:29 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 | wrapper |
- 2014/09/23 14:02:29 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | wrapper | Launching a JVM...
- 2014/09/23 14:02:29 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:02:29 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 | jvm 3 | wrapper |
- 2014/09/23 14:02:29 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:02:29 | wrapper |
- 2014/09/23 14:02:29 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 | wrapper | Advice:
- 2014/09/23 14:02:29 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:29 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:29 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:29 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:02:29 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 | wrapper |
- 2014/09/23 14:02:29 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | wrapper | Launching a JVM...
- 2014/09/23 14:02:29 |
- 2014/09/23 14:02:29 | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 | Advice:
- 2014/09/23 14:02:29 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:29 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:29 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:29 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:29 | variables are correctly defined for the current environment.
- 2014/09/23 14:02:29 | ------------------------------------------------------------------------
- 2014/09/23 14:02:29 |
- 2014/09/23 14:02:38 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | Launching a JVM...
- 2014/09/23 14:02:38 | JVM exited while loading the application.
- 2014/09/23 14:02:38 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:02:38 | e correctly defined for the current environment.
- 2014/09/23 14:02:38 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | wrapper |
- 2014/09/23 14:02:38 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:02:38 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | jvm 3 | wrapper |
- 2014/09/23 14:02:38 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | wrapper |
- 2014/09/23 14:02:38 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | wrapper | Advice:
- 2014/09/23 14:02:38 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:38 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:38 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:38 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:02:38 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | wrapper |
- 2014/09/23 14:02:38 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 14:02:38 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | jvm 4 | wrapper |
- 2014/09/23 14:02:38 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:02:38 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 14:02:38 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | jvm 4 | wrapper |
- 2014/09/23 14:02:38 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | jvm 4 | wrapper | Advice:
- 2014/09/23 14:02:38 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:38 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:38 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:38 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:02:38 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | jvm 4 | wrapper |
- 2014/09/23 14:02:38 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 | wrapper |
- 2014/09/23 14:02:38 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | wrapper | Advice:
- 2014/09/23 14:02:38 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:38 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:38 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:38 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:02:38 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | wrapper |
- 2014/09/23 14:02:38 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | wrapper | Launching a JVM...
- 2014/09/23 14:02:38 |
- 2014/09/23 14:02:38 | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 | Advice:
- 2014/09/23 14:02:38 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:02:38 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:02:38 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:02:38 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:02:38 | variables are correctly defined for the current environment.
- 2014/09/23 14:02:38 | ------------------------------------------------------------------------
- 2014/09/23 14:02:38 |
- 2014/09/23 14:02:38 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 14:02:38 | There may be a configuration problem: please check the logs.
- 2014/09/23 14:02:38 | <-- Wrapper Stopped
- 2014/09/23 14:05:23 | --> Wrapper Started as Daemon
- 2014/09/23 14:05:23 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:05:23 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:05:23 | http://wrapper.tanukisoftware.com
- 2014/09/23 14:05:23 |
- 2014/09/23 14:05:23 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:23 | Launching a JVM...
- 2014/09/23 14:05:23 | JVM exited while loading the application.
- 2014/09/23 14:05:23 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:05:23 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:05:23 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:05:23 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:05:23 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:05:23 | wrapper |
- 2014/09/23 14:05:23 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:23 | wrapper | Launching a JVM...
- 2014/09/23 14:05:23 |
- 2014/09/23 14:05:23 | ------------------------------------------------------------------------
- 2014/09/23 14:05:23 | Advice:
- 2014/09/23 14:05:23 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:23 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:23 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:23 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:23 | variables are correctly defined for the current environment.
- 2014/09/23 14:05:23 | ------------------------------------------------------------------------
- 2014/09/23 14:05:23 |
- 2014/09/23 14:05:33 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | Launching a JVM...
- 2014/09/23 14:05:33 | JVM exited while loading the application.
- 2014/09/23 14:05:33 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:05:33 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:05:33 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:05:33 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:05:33 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:05:33 | wrapper |
- 2014/09/23 14:05:33 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | wrapper | Launching a JVM...
- 2014/09/23 14:05:33 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 14:05:33 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 14:05:33 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 14:05:33 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 14:05:33 | jvm 1 | wrapper |
- 2014/09/23 14:05:33 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 14:05:33 | wrapper |
- 2014/09/23 14:05:33 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:33 | wrapper | Advice:
- 2014/09/23 14:05:33 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:33 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:33 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:33 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:05:33 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:33 | wrapper |
- 2014/09/23 14:05:33 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | wrapper | Launching a JVM...
- 2014/09/23 14:05:33 |
- 2014/09/23 14:05:33 | ------------------------------------------------------------------------
- 2014/09/23 14:05:33 | Advice:
- 2014/09/23 14:05:33 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:33 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:33 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:33 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:33 | variables are correctly defined for the current environment.
- 2014/09/23 14:05:33 | ------------------------------------------------------------------------
- 2014/09/23 14:05:33 |
- 2014/09/23 14:05:42 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:42 | Launching a JVM...
- 2014/09/23 14:05:42 | JVM exited while loading the application.
- 2014/09/23 14:05:42 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:05:42 | e correctly defined for the current environment.
- 2014/09/23 14:05:42 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:42 | wrapper |
- 2014/09/23 14:05:42 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:42 | wrapper | Launching a JVM...
- 2014/09/23 14:05:42 |
- 2014/09/23 14:05:42 | ------------------------------------------------------------------------
- 2014/09/23 14:05:42 | Advice:
- 2014/09/23 14:05:42 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:42 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:42 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:42 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:42 | variables are correctly defined for the current environment.
- 2014/09/23 14:05:42 | ------------------------------------------------------------------------
- 2014/09/23 14:05:42 |
- 2014/09/23 14:05:52 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | Launching a JVM...
- 2014/09/23 14:05:52 | JVM exited while loading the application.
- 2014/09/23 14:05:52 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:05:52 | e correctly defined for the current environment.
- 2014/09/23 14:05:52 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 | wrapper |
- 2014/09/23 14:05:52 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | wrapper | Launching a JVM...
- 2014/09/23 14:05:52 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:05:52 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 | jvm 3 | wrapper |
- 2014/09/23 14:05:52 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:05:52 | wrapper |
- 2014/09/23 14:05:52 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 | wrapper | Advice:
- 2014/09/23 14:05:52 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:52 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:52 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:52 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:05:52 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 | wrapper |
- 2014/09/23 14:05:52 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | wrapper | Launching a JVM...
- 2014/09/23 14:05:52 |
- 2014/09/23 14:05:52 | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 | Advice:
- 2014/09/23 14:05:52 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:05:52 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:05:52 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:05:52 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:05:52 | variables are correctly defined for the current environment.
- 2014/09/23 14:05:52 | ------------------------------------------------------------------------
- 2014/09/23 14:05:52 |
- 2014/09/23 14:06:01 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | Launching a JVM...
- 2014/09/23 14:06:01 | JVM exited while loading the application.
- 2014/09/23 14:06:01 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 14:06:01 | e correctly defined for the current environment.
- 2014/09/23 14:06:01 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | wrapper |
- 2014/09/23 14:06:01 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:06:01 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | jvm 3 | wrapper |
- 2014/09/23 14:06:01 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | wrapper |
- 2014/09/23 14:06:01 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | wrapper | Advice:
- 2014/09/23 14:06:01 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:06:01 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:06:01 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:06:01 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:06:01 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | wrapper |
- 2014/09/23 14:06:01 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 14:06:01 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | jvm 4 | wrapper |
- 2014/09/23 14:06:01 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 14:06:01 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 14:06:01 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | jvm 4 | wrapper |
- 2014/09/23 14:06:01 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | jvm 4 | wrapper | Advice:
- 2014/09/23 14:06:01 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:06:01 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:06:01 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:06:01 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:06:01 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | jvm 4 | wrapper |
- 2014/09/23 14:06:01 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 | wrapper |
- 2014/09/23 14:06:01 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | wrapper | Advice:
- 2014/09/23 14:06:01 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:06:01 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:06:01 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:06:01 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 14:06:01 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | wrapper |
- 2014/09/23 14:06:01 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | wrapper | Launching a JVM...
- 2014/09/23 14:06:01 |
- 2014/09/23 14:06:01 | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 | Advice:
- 2014/09/23 14:06:01 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 14:06:01 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 14:06:01 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 14:06:01 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 14:06:01 | variables are correctly defined for the current environment.
- 2014/09/23 14:06:01 | ------------------------------------------------------------------------
- 2014/09/23 14:06:01 |
- 2014/09/23 14:06:02 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 14:06:02 | There may be a configuration problem: please check the logs.
- 2014/09/23 14:06:02 | <-- Wrapper Stopped
- 2014/09/23 16:56:25 | --> Wrapper Started as Daemon
- 2014/09/23 16:56:25 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 16:56:25 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 16:56:25 | http://wrapper.tanukisoftware.com
- 2014/09/23 16:56:25 |
- 2014/09/23 16:56:25 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:26 | Launching a JVM...
- 2014/09/23 16:56:26 | JVM exited while loading the application.
- 2014/09/23 16:56:26 | Unable to start JVM: No such file or directory (2)
- 2014/09/23 16:56:26 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 16:56:26 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 16:56:26 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 16:56:26 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 16:56:26 | wrapper |
- 2014/09/23 16:56:26 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:26 | wrapper | Launching a JVM...
- 2014/09/23 16:56:26 |
- 2014/09/23 16:56:26 | ------------------------------------------------------------------------
- 2014/09/23 16:56:26 | Advice:
- 2014/09/23 16:56:26 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:26 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:26 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:26 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:26 | variables are correctly defined for the current environment.
- 2014/09/23 16:56:26 | ------------------------------------------------------------------------
- 2014/09/23 16:56:26 |
- 2014/09/23 16:56:35 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | Launching a JVM...
- 2014/09/23 16:56:35 | JVM exited while loading the application.
- 2014/09/23 16:56:35 | Unable to start JVM: No such file or directory (2)
- 2014/09/23 16:56:35 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 16:56:35 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 16:56:35 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 16:56:35 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 16:56:35 | wrapper |
- 2014/09/23 16:56:35 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | wrapper | Launching a JVM...
- 2014/09/23 16:56:35 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 16:56:35 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 16:56:35 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 16:56:35 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 16:56:35 | jvm 1 | wrapper |
- 2014/09/23 16:56:35 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 16:56:35 | wrapper |
- 2014/09/23 16:56:35 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:35 | wrapper | Advice:
- 2014/09/23 16:56:35 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:35 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:35 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:35 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 16:56:35 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:35 | wrapper |
- 2014/09/23 16:56:35 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | wrapper | Launching a JVM...
- 2014/09/23 16:56:35 |
- 2014/09/23 16:56:35 | ------------------------------------------------------------------------
- 2014/09/23 16:56:35 | Advice:
- 2014/09/23 16:56:35 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:35 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:35 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:35 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:35 | variables are correctly defined for the current environment.
- 2014/09/23 16:56:35 | ------------------------------------------------------------------------
- 2014/09/23 16:56:35 |
- 2014/09/23 16:56:44 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:45 | Launching a JVM...
- 2014/09/23 16:56:45 | JVM exited while loading the application.
- 2014/09/23 16:56:45 | Unable to start JVM: No such file or directory (2)
- 2014/09/23 16:56:45 | e correctly defined for the current environment.
- 2014/09/23 16:56:45 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:45 | wrapper |
- 2014/09/23 16:56:45 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:45 | wrapper | Launching a JVM...
- 2014/09/23 16:56:45 |
- 2014/09/23 16:56:45 | ------------------------------------------------------------------------
- 2014/09/23 16:56:45 | Advice:
- 2014/09/23 16:56:45 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:45 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:45 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:45 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:45 | variables are correctly defined for the current environment.
- 2014/09/23 16:56:45 | ------------------------------------------------------------------------
- 2014/09/23 16:56:45 |
- 2014/09/23 16:56:54 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | Launching a JVM...
- 2014/09/23 16:56:54 | JVM exited while loading the application.
- 2014/09/23 16:56:54 | Unable to start JVM: No such file or directory (2)
- 2014/09/23 16:56:54 | e correctly defined for the current environment.
- 2014/09/23 16:56:54 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 | wrapper |
- 2014/09/23 16:56:54 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | wrapper | Launching a JVM...
- 2014/09/23 16:56:54 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 16:56:54 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 | jvm 3 | wrapper |
- 2014/09/23 16:56:54 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 16:56:54 | wrapper |
- 2014/09/23 16:56:54 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 | wrapper | Advice:
- 2014/09/23 16:56:54 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:54 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:54 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:54 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 16:56:54 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 | wrapper |
- 2014/09/23 16:56:54 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | wrapper | Launching a JVM...
- 2014/09/23 16:56:54 |
- 2014/09/23 16:56:54 | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 | Advice:
- 2014/09/23 16:56:54 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:56:54 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:56:54 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:56:54 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:56:54 | variables are correctly defined for the current environment.
- 2014/09/23 16:56:54 | ------------------------------------------------------------------------
- 2014/09/23 16:56:54 |
- 2014/09/23 16:57:03 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | Launching a JVM...
- 2014/09/23 16:57:04 | JVM exited while loading the application.
- 2014/09/23 16:57:04 | Unable to start JVM: No such file or directory (2)
- 2014/09/23 16:57:04 | e correctly defined for the current environment.
- 2014/09/23 16:57:04 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | wrapper |
- 2014/09/23 16:57:04 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 16:57:04 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | jvm 3 | wrapper |
- 2014/09/23 16:57:04 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | wrapper |
- 2014/09/23 16:57:04 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | wrapper | Advice:
- 2014/09/23 16:57:04 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:57:04 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:57:04 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:57:04 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 16:57:04 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | wrapper |
- 2014/09/23 16:57:04 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 16:57:04 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | jvm 4 | wrapper |
- 2014/09/23 16:57:04 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 16:57:04 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 16:57:04 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | jvm 4 | wrapper |
- 2014/09/23 16:57:04 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | jvm 4 | wrapper | Advice:
- 2014/09/23 16:57:04 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:57:04 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:57:04 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:57:04 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 16:57:04 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | jvm 4 | wrapper |
- 2014/09/23 16:57:04 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 | wrapper |
- 2014/09/23 16:57:04 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | wrapper | Advice:
- 2014/09/23 16:57:04 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:57:04 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:57:04 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:57:04 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 16:57:04 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | wrapper |
- 2014/09/23 16:57:04 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | wrapper | Launching a JVM...
- 2014/09/23 16:57:04 |
- 2014/09/23 16:57:04 | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 | Advice:
- 2014/09/23 16:57:04 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 16:57:04 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 16:57:04 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 16:57:04 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 16:57:04 | variables are correctly defined for the current environment.
- 2014/09/23 16:57:04 | ------------------------------------------------------------------------
- 2014/09/23 16:57:04 |
- 2014/09/23 16:57:04 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 16:57:04 | There may be a configuration problem: please check the logs.
- 2014/09/23 16:57:04 | <-- Wrapper Stopped
- 2014/09/23 17:31:01 | --> Wrapper Started as Daemon
- 2014/09/23 17:31:01 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:31:01 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:31:01 | http://wrapper.tanukisoftware.com
- 2014/09/23 17:31:01 |
- 2014/09/23 17:31:01 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:01 | Launching a JVM...
- 2014/09/23 17:31:01 | JVM exited while loading the application.
- 2014/09/23 17:31:01 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:31:01 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:31:01 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:31:01 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:31:01 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:31:01 | wrapper |
- 2014/09/23 17:31:01 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:01 | wrapper | Launching a JVM...
- 2014/09/23 17:31:01 |
- 2014/09/23 17:31:01 | ------------------------------------------------------------------------
- 2014/09/23 17:31:01 | Advice:
- 2014/09/23 17:31:01 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:01 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:01 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:01 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:01 | variables are correctly defined for the current environment.
- 2014/09/23 17:31:01 | ------------------------------------------------------------------------
- 2014/09/23 17:31:01 |
- 2014/09/23 17:31:11 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | Launching a JVM...
- 2014/09/23 17:31:11 | JVM exited while loading the application.
- 2014/09/23 17:31:11 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:31:11 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:31:11 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:31:11 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:31:11 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:31:11 | wrapper |
- 2014/09/23 17:31:11 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | wrapper | Launching a JVM...
- 2014/09/23 17:31:11 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:31:11 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:31:11 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:31:11 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:31:11 | jvm 1 | wrapper |
- 2014/09/23 17:31:11 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 17:31:11 | wrapper |
- 2014/09/23 17:31:11 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:11 | wrapper | Advice:
- 2014/09/23 17:31:11 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:11 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:11 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:11 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:31:11 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:11 | wrapper |
- 2014/09/23 17:31:11 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | wrapper | Launching a JVM...
- 2014/09/23 17:31:11 |
- 2014/09/23 17:31:11 | ------------------------------------------------------------------------
- 2014/09/23 17:31:11 | Advice:
- 2014/09/23 17:31:11 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:11 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:11 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:11 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:11 | variables are correctly defined for the current environment.
- 2014/09/23 17:31:11 | ------------------------------------------------------------------------
- 2014/09/23 17:31:11 |
- 2014/09/23 17:31:20 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:20 | Launching a JVM...
- 2014/09/23 17:31:20 | JVM exited while loading the application.
- 2014/09/23 17:31:20 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:31:20 | e correctly defined for the current environment.
- 2014/09/23 17:31:20 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:20 | wrapper |
- 2014/09/23 17:31:20 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:20 | wrapper | Launching a JVM...
- 2014/09/23 17:31:20 |
- 2014/09/23 17:31:20 | ------------------------------------------------------------------------
- 2014/09/23 17:31:20 | Advice:
- 2014/09/23 17:31:20 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:20 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:20 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:20 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:20 | variables are correctly defined for the current environment.
- 2014/09/23 17:31:20 | ------------------------------------------------------------------------
- 2014/09/23 17:31:20 |
- 2014/09/23 17:31:30 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | Launching a JVM...
- 2014/09/23 17:31:30 | JVM exited while loading the application.
- 2014/09/23 17:31:30 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:31:30 | e correctly defined for the current environment.
- 2014/09/23 17:31:30 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 | wrapper |
- 2014/09/23 17:31:30 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | wrapper | Launching a JVM...
- 2014/09/23 17:31:30 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:31:30 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 | jvm 3 | wrapper |
- 2014/09/23 17:31:30 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:31:30 | wrapper |
- 2014/09/23 17:31:30 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 | wrapper | Advice:
- 2014/09/23 17:31:30 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:30 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:30 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:30 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:31:30 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 | wrapper |
- 2014/09/23 17:31:30 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | wrapper | Launching a JVM...
- 2014/09/23 17:31:30 |
- 2014/09/23 17:31:30 | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 | Advice:
- 2014/09/23 17:31:30 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:30 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:30 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:30 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:30 | variables are correctly defined for the current environment.
- 2014/09/23 17:31:30 | ------------------------------------------------------------------------
- 2014/09/23 17:31:30 |
- 2014/09/23 17:31:39 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | Launching a JVM...
- 2014/09/23 17:31:39 | JVM exited while loading the application.
- 2014/09/23 17:31:39 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:31:39 | e correctly defined for the current environment.
- 2014/09/23 17:31:39 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | wrapper |
- 2014/09/23 17:31:39 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:31:39 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | jvm 3 | wrapper |
- 2014/09/23 17:31:39 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | wrapper |
- 2014/09/23 17:31:39 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | wrapper | Advice:
- 2014/09/23 17:31:39 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:39 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:39 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:39 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:31:39 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | wrapper |
- 2014/09/23 17:31:39 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 17:31:39 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | jvm 4 | wrapper |
- 2014/09/23 17:31:39 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:31:39 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 17:31:39 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | jvm 4 | wrapper |
- 2014/09/23 17:31:39 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | jvm 4 | wrapper | Advice:
- 2014/09/23 17:31:39 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:39 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:39 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:39 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:31:39 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | jvm 4 | wrapper |
- 2014/09/23 17:31:39 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 | wrapper |
- 2014/09/23 17:31:39 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | wrapper | Advice:
- 2014/09/23 17:31:39 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:39 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:39 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:39 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:31:39 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | wrapper |
- 2014/09/23 17:31:39 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | wrapper | Launching a JVM...
- 2014/09/23 17:31:39 |
- 2014/09/23 17:31:39 | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 | Advice:
- 2014/09/23 17:31:39 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:31:39 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:31:39 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:31:39 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:31:39 | variables are correctly defined for the current environment.
- 2014/09/23 17:31:39 | ------------------------------------------------------------------------
- 2014/09/23 17:31:39 |
- 2014/09/23 17:31:40 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 17:31:40 | There may be a configuration problem: please check the logs.
- 2014/09/23 17:31:40 | <-- Wrapper Stopped
- 2014/09/23 17:41:33 | --> Wrapper Started as Daemon
- 2014/09/23 17:41:33 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:41:33 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:41:33 | http://wrapper.tanukisoftware.com
- 2014/09/23 17:41:33 |
- 2014/09/23 17:41:34 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:34 | Launching a JVM...
- 2014/09/23 17:41:34 | JVM exited while loading the application.
- 2014/09/23 17:41:34 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:41:34 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:41:34 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:41:34 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:41:34 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:41:34 | wrapper |
- 2014/09/23 17:41:34 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:34 | wrapper | Launching a JVM...
- 2014/09/23 17:41:34 |
- 2014/09/23 17:41:34 | ------------------------------------------------------------------------
- 2014/09/23 17:41:34 | Advice:
- 2014/09/23 17:41:34 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:41:34 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:41:34 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:34 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:41:34 | variables are correctly defined for the current environment.
- 2014/09/23 17:41:34 | ------------------------------------------------------------------------
- 2014/09/23 17:41:34 |
- 2014/09/23 17:41:43 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | Launching a JVM...
- 2014/09/23 17:41:43 | JVM exited while loading the application.
- 2014/09/23 17:41:43 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:41:43 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:41:43 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:41:43 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:41:43 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:41:43 | wrapper |
- 2014/09/23 17:41:43 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | wrapper | Launching a JVM...
- 2014/09/23 17:41:43 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:41:43 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:41:43 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:41:43 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:41:43 | jvm 1 | wrapper |
- 2014/09/23 17:41:43 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 17:41:43 | wrapper |
- 2014/09/23 17:41:43 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:41:43 | wrapper | Advice:
- 2014/09/23 17:41:43 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:41:43 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:41:43 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:41:43 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:41:43 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:41:43 | wrapper |
- 2014/09/23 17:41:43 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | wrapper | Launching a JVM...
- 2014/09/23 17:41:43 |
- 2014/09/23 17:41:43 | ------------------------------------------------------------------------
- 2014/09/23 17:41:43 | Advice:
- 2014/09/23 17:41:43 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:41:43 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:41:43 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:43 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:41:43 | variables are correctly defined for the current environment.
- 2014/09/23 17:41:43 | ------------------------------------------------------------------------
- 2014/09/23 17:41:43 |
- 2014/09/23 17:41:53 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:53 | Launching a JVM...
- 2014/09/23 17:41:53 | JVM exited while loading the application.
- 2014/09/23 17:41:53 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:41:53 | e correctly defined for the current environment.
- 2014/09/23 17:41:53 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:41:53 | wrapper |
- 2014/09/23 17:41:53 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:53 | wrapper | Launching a JVM...
- 2014/09/23 17:41:53 |
- 2014/09/23 17:41:53 | ------------------------------------------------------------------------
- 2014/09/23 17:41:53 | Advice:
- 2014/09/23 17:41:53 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:41:53 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:41:53 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:41:53 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:41:53 | variables are correctly defined for the current environment.
- 2014/09/23 17:41:53 | ------------------------------------------------------------------------
- 2014/09/23 17:41:53 |
- 2014/09/23 17:42:02 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | Launching a JVM...
- 2014/09/23 17:42:02 | JVM exited while loading the application.
- 2014/09/23 17:42:02 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:42:02 | e correctly defined for the current environment.
- 2014/09/23 17:42:02 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 | wrapper |
- 2014/09/23 17:42:02 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | wrapper | Launching a JVM...
- 2014/09/23 17:42:02 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:42:02 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 | jvm 3 | wrapper |
- 2014/09/23 17:42:02 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:42:02 | wrapper |
- 2014/09/23 17:42:02 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 | wrapper | Advice:
- 2014/09/23 17:42:02 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:02 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:02 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:02 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:42:02 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 | wrapper |
- 2014/09/23 17:42:02 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | wrapper | Launching a JVM...
- 2014/09/23 17:42:02 |
- 2014/09/23 17:42:02 | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 | Advice:
- 2014/09/23 17:42:02 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:02 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:02 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:02 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:02 | variables are correctly defined for the current environment.
- 2014/09/23 17:42:02 | ------------------------------------------------------------------------
- 2014/09/23 17:42:02 |
- 2014/09/23 17:42:12 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | Launching a JVM...
- 2014/09/23 17:42:12 | JVM exited while loading the application.
- 2014/09/23 17:42:12 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:42:12 | e correctly defined for the current environment.
- 2014/09/23 17:42:12 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | wrapper |
- 2014/09/23 17:42:12 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:42:12 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | jvm 3 | wrapper |
- 2014/09/23 17:42:12 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | wrapper |
- 2014/09/23 17:42:12 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | wrapper | Advice:
- 2014/09/23 17:42:12 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:12 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:12 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:12 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:42:12 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | wrapper |
- 2014/09/23 17:42:12 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 17:42:12 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | jvm 4 | wrapper |
- 2014/09/23 17:42:12 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:42:12 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 17:42:12 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | jvm 4 | wrapper |
- 2014/09/23 17:42:12 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | jvm 4 | wrapper | Advice:
- 2014/09/23 17:42:12 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:12 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:12 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:12 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:42:12 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | jvm 4 | wrapper |
- 2014/09/23 17:42:12 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 | wrapper |
- 2014/09/23 17:42:12 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | wrapper | Advice:
- 2014/09/23 17:42:12 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:12 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:12 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:12 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:42:12 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | wrapper |
- 2014/09/23 17:42:12 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | wrapper | Launching a JVM...
- 2014/09/23 17:42:12 |
- 2014/09/23 17:42:12 | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 | Advice:
- 2014/09/23 17:42:12 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:42:12 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:42:12 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:42:12 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:42:12 | variables are correctly defined for the current environment.
- 2014/09/23 17:42:12 | ------------------------------------------------------------------------
- 2014/09/23 17:42:12 |
- 2014/09/23 17:42:12 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 17:42:12 | There may be a configuration problem: please check the logs.
- 2014/09/23 17:42:12 | <-- Wrapper Stopped
- 2014/09/23 17:52:04 | --> Wrapper Started as Daemon
- 2014/09/23 17:52:04 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:04 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:04 | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:04 |
- 2014/09/23 17:52:04 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:05 | Launching a JVM...
- 2014/09/23 17:52:05 | JVM exited while loading the application.
- 2014/09/23 17:52:05 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:52:05 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:05 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:05 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:05 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:05 | wrapper |
- 2014/09/23 17:52:05 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:05 | wrapper | Launching a JVM...
- 2014/09/23 17:52:05 |
- 2014/09/23 17:52:05 | ------------------------------------------------------------------------
- 2014/09/23 17:52:05 | Advice:
- 2014/09/23 17:52:05 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:05 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:05 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:05 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:05 | variables are correctly defined for the current environment.
- 2014/09/23 17:52:05 | ------------------------------------------------------------------------
- 2014/09/23 17:52:05 |
- 2014/09/23 17:52:14 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | Launching a JVM...
- 2014/09/23 17:52:14 | JVM exited while loading the application.
- 2014/09/23 17:52:14 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:52:14 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:14 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:14 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:14 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:14 | wrapper |
- 2014/09/23 17:52:14 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | wrapper | Launching a JVM...
- 2014/09/23 17:52:14 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:14 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:14 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:14 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:14 | jvm 1 | wrapper |
- 2014/09/23 17:52:14 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 17:52:14 | wrapper |
- 2014/09/23 17:52:14 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:52:14 | wrapper | Advice:
- 2014/09/23 17:52:14 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:14 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:14 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:14 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:52:14 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:52:14 | wrapper |
- 2014/09/23 17:52:14 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | wrapper | Launching a JVM...
- 2014/09/23 17:52:14 |
- 2014/09/23 17:52:14 | ------------------------------------------------------------------------
- 2014/09/23 17:52:14 | Advice:
- 2014/09/23 17:52:14 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:14 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:14 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:14 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:14 | variables are correctly defined for the current environment.
- 2014/09/23 17:52:14 | ------------------------------------------------------------------------
- 2014/09/23 17:52:14 |
- 2014/09/23 17:52:23 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:24 | Launching a JVM...
- 2014/09/23 17:52:39 | --> Wrapper Started as Daemon
- 2014/09/23 17:52:39 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:39 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:39 | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:39 |
- 2014/09/23 17:52:39 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:39 | Launching a JVM...
- 2014/09/23 17:52:39 | JVM exited while loading the application.
- 2014/09/23 17:52:39 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:52:39 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:39 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:39 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:39 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:39 | wrapper |
- 2014/09/23 17:52:39 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:39 | wrapper | Launching a JVM...
- 2014/09/23 17:52:39 |
- 2014/09/23 17:52:39 | ------------------------------------------------------------------------
- 2014/09/23 17:52:39 | Advice:
- 2014/09/23 17:52:39 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:39 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:39 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:39 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:39 | variables are correctly defined for the current environment.
- 2014/09/23 17:52:39 | ------------------------------------------------------------------------
- 2014/09/23 17:52:39 |
- 2014/09/23 17:52:48 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | Launching a JVM...
- 2014/09/23 17:52:49 | JVM exited while loading the application.
- 2014/09/23 17:52:49 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:52:49 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:49 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:49 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:49 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:49 | wrapper |
- 2014/09/23 17:52:49 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | wrapper | Launching a JVM...
- 2014/09/23 17:52:49 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:52:49 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:52:49 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:52:49 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:52:49 | jvm 1 | wrapper |
- 2014/09/23 17:52:49 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 17:52:49 | wrapper |
- 2014/09/23 17:52:49 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:52:49 | wrapper | Advice:
- 2014/09/23 17:52:49 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:49 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:49 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:49 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:52:49 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:52:49 | wrapper |
- 2014/09/23 17:52:49 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | wrapper | Launching a JVM...
- 2014/09/23 17:52:49 |
- 2014/09/23 17:52:49 | ------------------------------------------------------------------------
- 2014/09/23 17:52:49 | Advice:
- 2014/09/23 17:52:49 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:49 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:49 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:49 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:49 | variables are correctly defined for the current environment.
- 2014/09/23 17:52:49 | ------------------------------------------------------------------------
- 2014/09/23 17:52:49 |
- 2014/09/23 17:52:58 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:58 | Launching a JVM...
- 2014/09/23 17:52:58 | JVM exited while loading the application.
- 2014/09/23 17:52:58 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:52:58 | e correctly defined for the current environment.
- 2014/09/23 17:52:58 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:52:58 | wrapper |
- 2014/09/23 17:52:58 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:58 | wrapper | Launching a JVM...
- 2014/09/23 17:52:58 |
- 2014/09/23 17:52:58 | ------------------------------------------------------------------------
- 2014/09/23 17:52:58 | Advice:
- 2014/09/23 17:52:58 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:52:58 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:52:58 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:52:58 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:52:58 | variables are correctly defined for the current environment.
- 2014/09/23 17:52:58 | ------------------------------------------------------------------------
- 2014/09/23 17:52:58 |
- 2014/09/23 17:53:07 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | Launching a JVM...
- 2014/09/23 17:53:08 | JVM exited while loading the application.
- 2014/09/23 17:53:08 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:53:08 | e correctly defined for the current environment.
- 2014/09/23 17:53:08 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 | wrapper |
- 2014/09/23 17:53:08 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | wrapper | Launching a JVM...
- 2014/09/23 17:53:08 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:53:08 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 | jvm 3 | wrapper |
- 2014/09/23 17:53:08 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:53:08 | wrapper |
- 2014/09/23 17:53:08 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 | wrapper | Advice:
- 2014/09/23 17:53:08 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:08 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:08 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:08 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:53:08 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 | wrapper |
- 2014/09/23 17:53:08 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | wrapper | Launching a JVM...
- 2014/09/23 17:53:08 |
- 2014/09/23 17:53:08 | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 | Advice:
- 2014/09/23 17:53:08 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:08 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:08 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:08 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:08 | variables are correctly defined for the current environment.
- 2014/09/23 17:53:08 | ------------------------------------------------------------------------
- 2014/09/23 17:53:08 |
- 2014/09/23 17:53:17 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | Launching a JVM...
- 2014/09/23 17:53:17 | JVM exited while loading the application.
- 2014/09/23 17:53:17 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:53:17 | e correctly defined for the current environment.
- 2014/09/23 17:53:17 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | wrapper |
- 2014/09/23 17:53:17 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:53:17 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | jvm 3 | wrapper |
- 2014/09/23 17:53:17 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | wrapper |
- 2014/09/23 17:53:17 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | wrapper | Advice:
- 2014/09/23 17:53:17 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:17 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:17 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:17 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:53:17 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | wrapper |
- 2014/09/23 17:53:17 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 17:53:17 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | jvm 4 | wrapper |
- 2014/09/23 17:53:17 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:53:17 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 17:53:17 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | jvm 4 | wrapper |
- 2014/09/23 17:53:17 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | jvm 4 | wrapper | Advice:
- 2014/09/23 17:53:17 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:17 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:17 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:17 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:53:17 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | jvm 4 | wrapper |
- 2014/09/23 17:53:17 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 | wrapper |
- 2014/09/23 17:53:17 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | wrapper | Advice:
- 2014/09/23 17:53:17 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:17 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:17 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:17 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:53:17 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | wrapper |
- 2014/09/23 17:53:17 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | wrapper | Launching a JVM...
- 2014/09/23 17:53:17 |
- 2014/09/23 17:53:17 | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 | Advice:
- 2014/09/23 17:53:17 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:53:17 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:53:17 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:53:17 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:53:17 | variables are correctly defined for the current environment.
- 2014/09/23 17:53:17 | ------------------------------------------------------------------------
- 2014/09/23 17:53:17 |
- 2014/09/23 17:53:17 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 17:53:17 | There may be a configuration problem: please check the logs.
- 2014/09/23 17:53:17 | <-- Wrapper Stopped
- 2014/09/23 17:55:05 | --> Wrapper Started as Daemon
- 2014/09/23 17:55:05 | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:55:05 | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:55:05 | http://wrapper.tanukisoftware.com
- 2014/09/23 17:55:05 |
- 2014/09/23 17:55:06 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:06 | Launching a JVM...
- 2014/09/23 17:55:06 | JVM exited while loading the application.
- 2014/09/23 17:55:06 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:55:06 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:55:06 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:55:06 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:55:06 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:55:06 | wrapper |
- 2014/09/23 17:55:06 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:06 | wrapper | Launching a JVM...
- 2014/09/23 17:55:06 |
- 2014/09/23 17:55:06 | ------------------------------------------------------------------------
- 2014/09/23 17:55:06 | Advice:
- 2014/09/23 17:55:06 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:06 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:06 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:06 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:06 | variables are correctly defined for the current environment.
- 2014/09/23 17:55:06 | ------------------------------------------------------------------------
- 2014/09/23 17:55:06 |
- 2014/09/23 17:55:15 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | Launching a JVM...
- 2014/09/23 17:55:15 | JVM exited while loading the application.
- 2014/09/23 17:55:15 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:55:15 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:55:15 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:55:15 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:55:15 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:55:15 | wrapper |
- 2014/09/23 17:55:15 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | wrapper | Launching a JVM...
- 2014/09/23 17:55:15 | jvm 1 | wrapper | --> Wrapper Started as Daemon
- 2014/09/23 17:55:15 | jvm 1 | wrapper | Java Service Wrapper Community Edition 64-bit 3.5.25
- 2014/09/23 17:55:15 | jvm 1 | wrapper | Copyright (C) 1999-2014 Tanuki Software, Ltd. All Rights Reserved.
- 2014/09/23 17:55:15 | jvm 1 | wrapper | http://wrapper.tanukisoftware.com
- 2014/09/23 17:55:15 | jvm 1 | wrapper |
- 2014/09/23 17:55:15 | jvm 1 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | jvm 1 | wrapper | Launching a JVM...
- 2014/09/23 17:55:15 | wrapper |
- 2014/09/23 17:55:15 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:15 | wrapper | Advice:
- 2014/09/23 17:55:15 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:15 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:15 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:15 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:55:15 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:15 | wrapper |
- 2014/09/23 17:55:15 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | wrapper | Launching a JVM...
- 2014/09/23 17:55:15 |
- 2014/09/23 17:55:15 | ------------------------------------------------------------------------
- 2014/09/23 17:55:15 | Advice:
- 2014/09/23 17:55:15 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:15 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:15 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:15 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:15 | variables are correctly defined for the current environment.
- 2014/09/23 17:55:15 | ------------------------------------------------------------------------
- 2014/09/23 17:55:15 |
- 2014/09/23 17:55:24 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:25 | Launching a JVM...
- 2014/09/23 17:55:25 | JVM exited while loading the application.
- 2014/09/23 17:55:25 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:55:25 | e correctly defined for the current environment.
- 2014/09/23 17:55:25 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:25 | wrapper |
- 2014/09/23 17:55:25 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:25 | wrapper | Launching a JVM...
- 2014/09/23 17:55:25 |
- 2014/09/23 17:55:25 | ------------------------------------------------------------------------
- 2014/09/23 17:55:25 | Advice:
- 2014/09/23 17:55:25 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:25 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:25 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:25 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:25 | variables are correctly defined for the current environment.
- 2014/09/23 17:55:25 | ------------------------------------------------------------------------
- 2014/09/23 17:55:25 |
- 2014/09/23 17:55:34 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | Launching a JVM...
- 2014/09/23 17:55:34 | JVM exited while loading the application.
- 2014/09/23 17:55:34 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:55:34 | e correctly defined for the current environment.
- 2014/09/23 17:55:34 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 | wrapper |
- 2014/09/23 17:55:34 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | wrapper | Launching a JVM...
- 2014/09/23 17:55:34 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:55:34 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 | jvm 3 | wrapper |
- 2014/09/23 17:55:34 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:55:34 | wrapper |
- 2014/09/23 17:55:34 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 | wrapper | Advice:
- 2014/09/23 17:55:34 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:34 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:34 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:34 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:55:34 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 | wrapper |
- 2014/09/23 17:55:34 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | wrapper | Launching a JVM...
- 2014/09/23 17:55:34 |
- 2014/09/23 17:55:34 | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 | Advice:
- 2014/09/23 17:55:34 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:34 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:34 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:34 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:34 | variables are correctly defined for the current environment.
- 2014/09/23 17:55:34 | ------------------------------------------------------------------------
- 2014/09/23 17:55:34 |
- 2014/09/23 17:55:43 | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | Launching a JVM...
- 2014/09/23 17:55:44 | JVM exited while loading the application.
- 2014/09/23 17:55:44 | Unable to start JVM: Нет такого файла или каталога (2)
- 2014/09/23 17:55:44 | e correctly defined for the current environment.
- 2014/09/23 17:55:44 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | wrapper |
- 2014/09/23 17:55:44 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:55:44 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | jvm 3 | wrapper |
- 2014/09/23 17:55:44 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | wrapper |
- 2014/09/23 17:55:44 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | wrapper | Advice:
- 2014/09/23 17:55:44 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:44 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:44 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:44 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:55:44 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | wrapper |
- 2014/09/23 17:55:44 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | jvm 4 | e correctly defined for the current environment.
- 2014/09/23 17:55:44 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | jvm 4 | wrapper |
- 2014/09/23 17:55:44 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | jvm 4 | jvm 3 | e correctly defined for the current environment.
- 2014/09/23 17:55:44 | jvm 4 | jvm 3 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | jvm 4 | jvm 3 | wrapper |
- 2014/09/23 17:55:44 | jvm 4 | jvm 3 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | jvm 4 | jvm 3 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | jvm 4 | wrapper |
- 2014/09/23 17:55:44 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | jvm 4 | wrapper | Advice:
- 2014/09/23 17:55:44 | jvm 4 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:44 | jvm 4 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:44 | jvm 4 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | jvm 4 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:44 | jvm 4 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:55:44 | jvm 4 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | jvm 4 | wrapper |
- 2014/09/23 17:55:44 | jvm 4 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | jvm 4 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 | wrapper |
- 2014/09/23 17:55:44 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | wrapper | Advice:
- 2014/09/23 17:55:44 | wrapper | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:44 | wrapper | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:44 | wrapper | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | wrapper | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:44 | wrapper | variables are correctly defined for the current environment.
- 2014/09/23 17:55:44 | wrapper | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | wrapper |
- 2014/09/23 17:55:44 | wrapper | The configured wrapper.java.command could not be found, attempting to launch anyway: /usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | wrapper | Launching a JVM...
- 2014/09/23 17:55:44 |
- 2014/09/23 17:55:44 | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 | Advice:
- 2014/09/23 17:55:44 | Usually when the Wrapper fails to start the JVM process, it is because
- 2014/09/23 17:55:44 | of a problem with the value of the configured Java command. Currently:
- 2014/09/23 17:55:44 | wrapper.java.command=/usr/lib/jvm/java-default-runtime/bin/java
- 2014/09/23 17:55:44 | Please make sure that the PATH or any other referenced environment
- 2014/09/23 17:55:44 | variables are correctly defined for the current environment.
- 2014/09/23 17:55:44 | ------------------------------------------------------------------------
- 2014/09/23 17:55:44 |
- 2014/09/23 17:55:44 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.
- 2014/09/23 17:55:44 | There may be a configuration problem: please check the logs.
- 2014/09/23 17:55:44 | <-- Wrapper Stopped
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement