为什么包装器会自动重新启动?

时间:2018-08-10 08:23:01

标签: windows windows-services java-service-wrapper tanuki

当包装器正常运行时,包装器突然通过将信号/代码 SERVICE_CONTROL_STOP 发送到JVM来重新启动。

我是否可以知道包装器将此信号/代码发送到JVM的原因?这是否表明包装程序的任何配置都是错误的?

DEBUG  | wrapperp | 2018/08/08 16:57:38 | Send a packet PING : ping 000003ef
INFO   | jvm 1    | 2018/08/08 16:57:39 | WrapperManager Debug: Received a packet PING : ping 000003ef
INFO   | jvm 1    | 2018/08/08 16:57:39 | WrapperManager Debug: Send a packet PING : ping 000003ef
DEBUG  | wrapperp | 2018/08/08 16:57:39 | read a packet PING : ping 000003ef
DEBUG  | wrapperp | 2018/08/08 16:57:43 | Send a packet PING : ping 00000418
INFO   | jvm 1    | 2018/08/08 16:57:43 | WrapperManager Debug: Received a packet PING : ping 00000418
INFO   | jvm 1    | 2018/08/08 16:57:43 | WrapperManager Debug: Send a packet PING : ping 00000418
DEBUG  | wrapperp | 2018/08/08 16:57:43 | read a packet PING : ping 00000418
DEBUG  | wrapperp | 2018/08/08 16:57:47 | Send a packet PING : ping 00000441
INFO   | jvm 1    | 2018/08/08 16:57:47 | WrapperManager Debug: Received a packet PING : ping 00000441
INFO   | jvm 1    | 2018/08/08 16:57:47 | WrapperManager Debug: Send a packet PING : ping 00000441
DEBUG  | wrapperp | 2018/08/08 16:57:47 | read a packet PING : ping 00000441
DEBUG  | wrapperp | 2018/08/08 16:57:51 | Send a packet PING : ping 0000046a
INFO   | jvm 1    | 2018/08/08 16:57:51 | WrapperManager Debug: Received a packet PING : ping 0000046a
INFO   | jvm 1    | 2018/08/08 16:57:51 | WrapperManager Debug: Send a packet PING : ping 0000046a
DEBUG  | wrapperp | 2018/08/08 16:57:51 | read a packet PING : ping 0000046a
DEBUG  | wrapperp | 2018/08/08 16:57:55 | Send a packet PING : ping 00000493
INFO   | jvm 1    | 2018/08/08 16:57:55 | WrapperManager Debug: Received a packet PING : ping 00000493
INFO   | jvm 1    | 2018/08/08 16:57:55 | WrapperManager Debug: Send a packet PING : ping 00000493
DEBUG  | wrapperp | 2018/08/08 16:57:55 | read a packet PING : ping 00000493
DEBUG  | wrapperp | 2018/08/08 16:57:59 | Send a packet PING : ping 000004bc
INFO   | jvm 1    | 2018/08/08 16:57:59 | WrapperManager Debug: Received a packet PING : ping 000004bc
INFO   | jvm 1    | 2018/08/08 16:57:59 | WrapperManager Debug: Send a packet PING : ping 000004bc
DEBUG  | wrapperp | 2018/08/08 16:57:59 | read a packet PING : ping 000004bc
DEBUG  | wrapperp | 2018/08/08 16:58:03 | Send a packet PING : ping 000004e5
INFO   | jvm 1    | 2018/08/08 16:58:03 | WrapperManager Debug: Received a packet PING : ping 000004e5
INFO   | jvm 1    | 2018/08/08 16:58:03 | WrapperManager Debug: Send a packet PING : ping 000004e5
DEBUG  | wrapperp | 2018/08/08 16:58:03 | read a packet PING : ping 000004e5
DEBUG  | wrapper  | 2018/08/08 16:58:04 |   SERVICE_CONTROL_STOP
DEBUG  | wrapperp | 2018/08/08 16:58:04 | Send a packet SERVICE_CONTROL_CODE : 1
DEBUG  | wrapper  | 2018/08/08 16:58:04 | wrapperStopProcess(0, TRUE) called.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Received a packet SERVICE_CONTROL_CODE : 1
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: ServiceControlCode from Wrapper with code 1
DEBUG  | wrapper  | 2018/08/08 16:58:04 | Sending stop signal to JVM
DEBUG  | wrapperp | 2018/08/08 16:58:04 | Send a packet STOP : NULL
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Received a packet STOP : 
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Thread, Wrapper-Connection, handling the shutdown process.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: calling listener.stop()
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Waiting for WrapperListener.stop runner thread to complete.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: WrapperListener.stop runner thread started.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Application stop main thread: WrapperListener_stop_runner Priority: 5
INFO   | jvm 1    | 2018/08/08 16:58:04 | Going to shutdown the all threads...
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: WrapperListener.stop runner thread stopped.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: returned from listener.stop() -> 0
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: shutdownJVM(0) Thread: Wrapper-Connection
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: wait for 0 shutdown locks to be released.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Send a packet STOPPED : 0
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Stopped checking for control events.
DEBUG  | wrapperp | 2018/08/08 16:58:04 | read a packet STOPPED : 0
DEBUG  | wrapper  | 2018/08/08 16:58:04 | JVM signaled that it was stopped.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: Closing backend connection.
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: calling System.exit(0)
INFO   | jvm 1    | 2018/08/08 16:58:04 | WrapperManager Debug: WrapperManger stopped due to System Exit
DEBUG  | wrapperp | 2018/08/08 16:58:04 | socket read no code (closed?).
DEBUG  | wrapperp | 2018/08/08 16:58:04 | Closing backend socket.
DEBUG  | wrapper  | 2018/08/08 16:58:05 | JVM process exited with a code of 0, leaving the wrapper exit code set to 0.
DEBUG  | wrapper  | 2018/08/08 16:58:05 | JVM exited normally.
STATUS | wrapper  | 2018/08/08 16:58:05 | <-- Wrapper Stopped
STATUS | wrapper  | 2018/08/08 16:58:07 | --> Wrapper Started as Service
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Allocating a console for the service.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Found console window.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Wrapper console window hidden successfully.
STATUS | wrapper  | 2018/08/08 16:58:07 | Java Service Wrapper Community Edition 32-bit 3.5.27
STATUS | wrapper  | 2018/08/08 16:58:07 |   Copyright (C) 1999-2015 Tanuki Software, Ltd. All Rights Reserved.
STATUS | wrapper  | 2018/08/08 16:58:07 |     http://wrapper.tanukisoftware.com
STATUS | wrapper  | 2018/08/08 16:58:07 | 
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Launching Startup thread.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Startup thread started.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Attempting to verify the binary signature.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | The file "C:\InfoMindz\eFileMonitor\wrapper.exe" is signed and the signature was verified.
DEBUG  | wrapper  | 2018/08/08 16:58:07 |   Signer Certificate:
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Serial Number: 
DEBUG  | wrapper  | 2018/08/08 16:58:07 |       00 97 06 fe b5 6e 56 cc cb 66 3a bb 55 a7 a0 e4 76 
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Issuer Name: UTN-USERFirst-Object
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Subject Name: Tanuki Software Ltd.
DEBUG  | wrapper  | 2018/08/08 16:58:07 |   TimeStamp Certificate:
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Serial Number: 
DEBUG  | wrapper  | 2018/08/08 16:58:07 |       00 9f ea c8 11 b0 f1 62 47 a5 fc 20 d8 05 23 ac e6 
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Issuer Name: UTN-USERFirst-Object
DEBUG  | wrapper  | 2018/08/08 16:58:07 |     Subject Name: COMODO Time Stamping Signer
DEBUG  | wrapper  | 2018/08/08 16:58:07 | 
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Startup thread stopped.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Release time: 2015/09/04 00:00:00
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Build time:   2015/09/04 14:13:00
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Timezone:     India Standard Time (India Standard Time) Offset: -19800, hasDaylight: 0
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Using tick timer.
DEBUG  | wrapper  | 2018/08/08 16:58:07 | PID:          15904
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Current User: SYSTEM  Domain: NT AUTHORITY
DEBUG  | wrapper  | 2018/08/08 16:58:07 | Operating System ID: Microsoft Windows XP Professional Service Pack 3 (build 2600)

请帮助我调试此问题。

谢谢。

0 个答案:

没有答案