|
From: Maxime A. <max...@ta...> - 2017-08-31 02:03:53
|
Hana Thank you for your email. These restarts are initiated by the OS. As you can see in the log, the Wrapper catches a SERVICE_CONTROL_STOP signal (for example at 10:17:18) and stops in response. This may happen for instance when you stop the service from the "Services" window accessible from the control panel. The Wrapper is behaving normally here, so if those restarts are unexpected the cause should be searched at the OS level. Around both 10:17:59 and 19:29:00, the Wrapper is forwarding the logs of the JVM normally, so any log message coming from your application will also be printed by the Wrapper. Unfortunately it seems that for some reason your application doesn't always catch the file as expected, although it is still running. You should probably add some debug messages in your code to better understand what your application is doing. Best Regards, Maxime On Tue, Aug 29, 2017 at 10:43 AM, Hana Wu <Ha...@se...> wrote: > Hi Team, > > > > Thanks for your feedback, I set the ‘wrapper.debug’ to true and running > one month. It works well, but today it crashed again, the details log in > attachment. The service be restarted at 18:00 everyday. You can see the > log, > > > > Service be restarted 10:17:18, and the new file coming in at 10:17:59, it > caught. Then > > Service be restarted 18:00:00, and the new file coming in at 19:29:00, It > did not catch it. > > > > Could you help check? > > > > Thanks so much, > > Hana > > > > *From:* Maxime [mailto:ma...@ta...] > *Sent:* Monday, 24 July 2017 12:26 p.m. > *To:* wra...@li... > *Subject:* Re: [Wrapper-user] Java service crashed after 5 hours > > > > Hana > > Thank you for your email. > > Could you please run the Wrapper in debug mode and send us the log file so > that we can see more outputs just before the Wrapper stops? To execute in > debug mode, just set wrapper.debug=TRUE and make sure the property is not > commented, then relaunch the Wrapper. > > Note that in your configuration you have set the > wrapper.ntservice.recovery.* properties of the standard edition but they > will be ignored because you are using the community edition. This should > not cause the Wrapper to stop though. > > Best Regards, > > Maxime > > > > 2017-07-24 11:41 GMT+09:00 Hana Wu <Ha...@se...>: > > Hi Team, > > > > Thanks for your help. > > > > I used java service wrapper to running a jar file. My java application is > for monitoring a folder if it has a new file coming in, the service can > started and working well for several hours, after that, it doesn’t work, > need restart service. > > > > Below is the detailed information: > > > > > > - The version of the Wrapper you are using. - *Java Service Wrapper > Community Edition 32-bit 3.5.32* > The OS and version that you are running on. – *Windows Server 2008 R2 > Datacenter, 64 bit OS* > - Your wrapper.conf file. – see attachment > - Your wrapper.log file. – see attachment > > > > Thanks, > > Hana > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > -- Maxime Andrighetto Tanuki Software Ltd. 6-18-10-4F Nishi-Kasai, Edogawa-ku Tokyo 134-0088 Japan Tel: +81-3-3878-3211 Fax: +81-3-3878-0313 http://www.tanukisoftware.com |