I am using JAVA service Wrapper + Spring in my application.
This application is a batch job which basically calls other applcations at regular intervals.
i start this batch using the install.bat file and stop it using uninstall.bat file.
it is deployed as windows service.
The other applications are AXIS2 1.3 webservices.
The batch application is set in the JAVA 6 environament.
when this batch job calls a webservice A the service returns a XML (very large in size) which is then massaged by the batch application and then sent back to another service say B(XML very large in size) .
the service B then finishes its process and ther returns back to the batch which eventually updates the status of process in DB
If the above process continues for 2 or 3 hours then the batch job suddenly gets reset/reload.
this behaviour is very unpredictable some times it happens after 2/3 hrs some times 4 hrs... once the XML is received it generally restarts before massaging and sending the XML to service B and as this reloads the stuff the current running process is suspended in between and is never completed.
and Spring reloads application context which is very strange behavious i guess the JVM restarts.
i could see same log messags which appeared @ the application start.
In my conf file i havnt set any restart parameters.
also it seems ther is no eror message in the log file which must have caused the restart.
my configuration file looks as below.
i am new to this any help in this is appreciated
I am using JAVA service Wrapper + Spring in my application.
This application is a batch job which basically calls other applcations at regular intervals.
i start this batch using the install.bat file and stop it using uninstall.bat file.
it is deployed as windows service.
The other applications are AXIS2 1.3 webservices.
The batch application is set in the JAVA 6 environament.
when this batch job calls a webservice A the service returns a XML (very large in size) which is then massaged by the batch application and then sent back to another service say B(XML very large in size) .
the service B then finishes its process and ther returns back to the batch which eventually updates the status of process in DB
If the above process continues for 2 or 3 hours then the batch job suddenly gets reset/reload.
this behaviour is very unpredictable some times it happens after 2/3 hrs some times 4 hrs... once the XML is received it generally restarts before massaging and sending the XML to service B and as this reloads the stuff the current running process is suspended in between and is never completed.
and Spring reloads application context which is very strange behavious i guess the JVM restarts.
i could see same log messags which appeared @ the application start.
In my conf file i havnt set any restart parameters.
also it seems ther is no eror message in the log file which must have caused the restart.
my configuration file looks as below.
i am new to this any help in this is appreciated
#********************************************************************
# TestWrapper Properties
#
# NOTE - Please use src/conf/wrapper.conf.in as a template for your
# own application rather than the values used for the
# TestWrapper sample.
#********************************************************************
# Java Application
wrapper.java.command=java
# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.
wrapper.java.mainclass=com.toro.rebateautomation.RebateAutomation
# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/*.*
wrapper.java.classpath.3=../conf/*.*
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
# Java Additional Parameters
#wrapper.java.additional.1=
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=512
# Application parameters. Add parameters as needed starting from 1
#wrapper.app.parameter.1=
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console. (See docs for formats)
wrapper.console.format=PM
# Log Level for console output. (See docs for log levels)
wrapper.console.loglevel=INFO
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
# Format of output for the log file. (See docs for formats)
wrapper.logfile.format=LPTM
# Log Level for log file output. (See docs for log levels)
wrapper.logfile.loglevel=NONE
# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0
# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0
# Log Level for sys/event log output. (See docs for log levels)
wrapper.syslog.loglevel=NONE
#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=Rebate Automation
#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.
# Name of the service
wrapper.ntservice.name=Rebate Automation
# Display name of the service
wrapper.ntservice.displayname=Rebate Automation
# Description of the service
wrapper.ntservice.description=Rebate Automation
# Service dependencies. Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
# Mode in which the service is installed. AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
This is being discussed on the wrapper-user mailing list.