Tanuki Software Java Service Wrapper

내 응용 프로그램에 Tanuki Java 서비스 래퍼를 사용 중입니다. 내 응용 프로그램이 결국 "5 개의 실패한 실행을 연속적으로 포기"하고 자주 다시 시작합니다. 여기에 이런 일이 될 이유Tanuki Software Java Service Wrapper

ERROR | wrapper | 2012/05/18 13:22:39 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/19 00:24:17 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/19 00:24:17 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/19 01:07:33 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/19 01:08:11 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/19 01:08:11 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/19 05:31:55 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/19 05:32:34 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/19 05:32:34 | There may be a configuration problem: please check the logs. 
FATAL | wrapper | 2012/05/19 13:33:23 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/19 13:33:23 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/19 16:07:30 | JVM did not exit on request, terminated 
ERROR | wrapper | 2012/05/19 17:02:46 | JVM did not exit on request, terminated 
ERROR | wrapper | 2012/05/19 20:17:36 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/19 20:18:13 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/19 20:18:13 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/19 21:27:08 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/20 00:28:00 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/20 00:28:00 | There may be a configuration problem: please check the logs. 
FATAL | wrapper | 2012/05/20 05:22:27 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/20 05:22:27 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/20 13:47:37 | JVM did not exit on request, terminated 
ERROR | wrapper | 2012/05/20 16:27:34 | JVM did not exit on request, terminated 
FATAL | wrapper | 2012/05/20 18:22:28 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. 
FATAL | wrapper | 2012/05/20 18:22:28 | There may be a configuration problem: please check the logs. 
ERROR | wrapper | 2012/05/20 19:22:21 | JVM did not exit on request, terminated 
ERROR | wrapper | 2012/05/20 21:28:06 | JVM did not exit on request, terminated 
STATUS | wrapper | 2012/05/20 21:28:08 | --> Wrapper Started as Daemon 
STATUS | wrapper | 2012/05/20 21:28:08 | Java Service Wrapper Professional Edition 64-bit 3.5.7 
STATUS | wrapper | 2012/05/20 21:28:08 |  http://wrapper.tanukisoftware.com 
STATUS | wrapper | 2012/05/20 21:28:08 | 
STATUS | wrapper | 2012/05/20 21:28:08 | Launching a JVM... 
INFO | jvm 1 | 2012/05/20 21:28:09 | WrapperManager: Initializing...

어떤 생각이 내 래퍼입니다?

출처

2013-09-05 Mok

자바가 설정되어 당신이 자바 – muthukumar

예 클래스 경로의 클래스 경로를 설정해야 – Mok

전체 wrapper.log 파일입니까? 메시지의 시간과 순서에 따라 특정 행만 표시 할 수있는 것처럼 보입니다.

일반적으로 실패한 호출은 구성 문제를 나타냅니다. wrapper.debug = true를 사용하여 전체 wrapper.log 출력뿐만 아니라 wrapper.conf 파일을보아야 만 문제를 알릴 수 있습니다.

전문가 용 사용자 인 경우 [email protected]으로 문의 해 주시면이 문제를 해결할 수 있도록 도와 드리겠습니다. http://wrapper.tanukisoftware.com/doc/english/support.jsp

건배, 레이프

출처

2013-09-09 04:59:02

답변

관련 문제