Re: [Wrapper-user] Re: Windows 2003 support and restart issue

[Leif M. <le...@ta...>]

Sam,
Your config file looks pretty normal except for one thing.  Your log 
file is defined as:
wrapper.logfile=log/ase.log

This means that you have a log directory in the bin directory where 
wrapper.exe is
located?  Is that correct?  Should this be:
wrapper.logfile=../log/ase.log

Anyway, in your case, wrapper.log does not exist.   It is called 
ase.log.  Does that
file exist after your files have vanished?   If so, I am wondering if 
you can reproduce
this with the wrapper.debug=true property set?  I still can't think of 
how the wrapper
could be causing this...  But that might give us some clues as to 
exactly when the files
are getting deleted.

Also, try adding the following properties.  I am wondering if these 
files exist after a
reboot when the files are being deleted.  If the pid files still exist 
then it means that
the wrapper was not shut down cleanly.
wrapper.pidfile=./wrapper.pid
wrapper.java.pidfile=./java.pid

I assume you are running as a service.   Are you able to reproduce this 
when running
as a console app?  Probably not...

You say that you are running as a user with admin privileges.  How are 
you setting
that account?  It does not appear that you are using the 
wrapper.ntservice.account
property to configure that.

Do the directories or files where you have the wrapper and you 
application installed
have any special permissions or access restrictions assigned to them?

The 3.2.0 will be out very shortly.  Getting it all tied up.  If you 
want, you can
give the latest prerelease snapshot a try.  But can't imagine that it 
would change
anything.
http://wrapper.tanukisoftware.org/tmp/3.2.0-d/wrapper-windows-x86-32-3.2.0-d.zip

Cheers,
Leif


Sam Russell wrote:
> Leif, here's the wrapper.conf file (the {tag} items are altered by our 
> installer and some non-important classname info has been changed).  
> I'd like to clear up that i don't know that the service wrapper is 
> responsible for the issues we're seeing, it's just clear that any file 
> associated with the service is affected by what's happening - so it 
> seems like a good place to start.
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> #wrapper.java.command=..\java\bin\java
> wrapper.java.command={jre}/bin/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=MainClass
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../wrapper/wrapper.jar
> wrapper.java.classpath.2=../bin/{jar}
> wrapper.java.classpath.3=../lib/j2ee/mail.jar
> wrapper.java.classpath.4=../lib/xml/jdom.jar
> wrapper.java.classpath.5=../lib/j2ee/activation.jar
> wrapper.java.classpath.6=../lib/j2ee/servlet.jar
> wrapper.java.classpath.7=../lib/apache/commons/commons-lang-1.0.1.jar
> wrapper.java.classpath.8=../lib/db/mysql.jar
> wrapper.java.classpath.9=../lib/util/concurrent.jar
> wrapper.java.classpath.10=../lib/util/jetty.jar
> wrapper.java.classpath.11=../lib/apache/commons/commons-logging-api.jar
> wrapper.java.classpath.12=../lib/util/tools.jar
> wrapper.java.classpath.13=../lib/apache/commons/commons-io-1.1.jar
> wrapper.java.classpath.14=../lib/apache/ant/ant.jar
> wrapper.java.classpath.15=../lib/apache/axis/axis.jar
> wrapper.java.classpath.16=../lib/apache/axis/axis-ant.jar
> wrapper.java.classpath.17=../lib/apache/axis/axis-schema.jar
> wrapper.java.classpath.18=../lib/apache/commons/commons-discovery-0.2.jar
> wrapper.java.classpath.19=../lib/apache/commons/commons-el.jar
> wrapper.java.classpath.20=../lib/apache/jasper/jasper-compiler.jar
> wrapper.java.classpath.21=../lib/apache/jasper/jasper-runtime.jar
> wrapper.java.classpath.22=../lib/apache/axis/jaxrpc.jar
> wrapper.java.classpath.23=../lib/util/jmx.jar
> wrapper.java.classpath.24=../lib/apache/log4j/log4j-1.2.8.jar
> wrapper.java.classpath.25=../lib/apache/mx4j/mx4j.jar
> wrapper.java.classpath.26=../lib/apache/mx4j/mx4j-remote.jar
> wrapper.java.classpath.27=../lib/apache/mx4j/mx4j-tools.jar
> wrapper.java.classpath.28=../lib/apache/axis/opensaml-1.0.1.jar
> wrapper.java.classpath.29=../lib/apache/axis/saaj.jar
> wrapper.java.classpath.30=../lib/apache/axis/wsdl4j-1.5.1.jar
> wrapper.java.classpath.31=../lib/apache/axis/wss4j.jar
> wrapper.java.classpath.32=../lib/apache/xml/xercesImpl.jar
> wrapper.java.classpath.33=../lib/apache/xml/xml-apis.jar
> wrapper.java.classpath.34=../lib/xml/xmlsec-1.3.0.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../wrapper/
> wrapper.java.library.path.2=./
>
> # Java Additional Parameters
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Dase.tag={tag}
> wrapper.java.additional.3=-Dwrapper.actionserver.port={actionport}
> wrapper.java.additional.4=-Djava.io.tmpdir=.
> wrapper.java.additional.5=-Dsun.rmi.server.exceptionTrace=true
>
> # Sets the working directory for the application.
> wrapper.working.dir=../{tag}
>
> # Initial Java Heap Size (in MB)
> wrapper.java.initmemory=64
>
> # Maximum Java Heap Size (in MB)
> wrapper.java.maxmemory=512
>
> #Dump threads when a failure to exit occurs
> wrapper.request_thread_dump_on_failed_jvm_exit=TRUE
>
> #Time before bailing the JVM
> wrapper.jvm_exit.timeout=180
>
> #Delay between an internal shutdown and start
> wrapper.restart.delay=30
>  
> #How long to wait for the jvm to stop before killing it
> wrapper.shutdown.timeout=250
>
> #Maximum number of times to restart JVM
> wrapper.max_failed_invocations=100
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
>
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=NONE
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=log/ase.log
>
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=M
>
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=INFO
>
> # 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=10m
>
> # 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=50
>
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=ERROR
>
> # Ping Interval - How often the JVM will be pinged for life
> wrapper.ping.interval=3595
>
> #Ping Timeout - How long to wait for a response from the JVM
> wrapper.ping.timeout=3600
>
> #Filters and Triggers - Actions: RESTART, SHUTDOWN, NONE
> #wrapper.filter.trigger.1= java.lang.OutOfMemoryError
> #wrapper.filter.action.1=RESTART
>
> #********************************************************************
> # Wrapper NT 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={tag}
>
> # Display name of the service
> wrapper.ntservice.displayname={tag}
>
> # Description of the service
> wrapper.ntservice.description=Description
>
> # Service dependencies.  Add dependencies as needed starting from 1
> #wrapper.ntservice.dependency.1=mysql
>
> # 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
>
> We run the service as an administrative user (admin or user with admin 
> privaledges).
> Are there any new versions of the wrapper released (or being released 
> in the near future)?
>
> >Can you post your wrapper.conf file.   I still can't think of anything
> >that the Wrapper could
> >possibly be doing to cause this.  But I am curious about how the service
> >is being configured
> >to run.   System user, or are you specifying a specific user to run as.
> >Also wondering about your wrapper.log file.  It is specified using the
> >following property:
> >wrapper.logfile=../logs/wrapper.log
>
> >If the Wrapper is unable to write to that file for any reason, it will
> >try writing to
> >./wrapper.log  Failing that, it will create a file in the
> >Windows\system32 directory.
>
>
> Thanks,
>
> Sam