|
From: Maxime <ma...@ta...> - 2017-07-24 04:26:15
|
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 > > |