wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: [Wrapper-user] Win Server 2003 and GUI

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

Ajmal,
    Thanks for trying that out.  I'll add a comment on the 
wrapper.ntservice.interactive
property's documentation page.

Cheers,
Leif

Ajmal Abdool wrote:
> Hi Leif,
>
> I tried the following and still couldnt get the GUI to
> be displayed via Remote Desktop.
>
> 1. Logged everyone out from the server and then
> connect to the server via RDC. No GUI
>
> 2. Logged out of the server. Connect locally to the
> Server. The GUI is displayed. I then left the session
> open and connect via RDC from my PC. Still no GUI.
>
> I think that the issue with Win Server OS is that
> there is no 'default' or 'first' session. Each time a
> user logs in, a different session is open. We can have
> the same user logged in multiple times concurrently
> with the same user name...
>
> I hope that helped. Let me know if you need any more
> tests carried out...
>
> Cheers,
>
> Ajmal
>
> --- Leif Mortenson <le...@ta...> wrote:
>
>   
>> Ajmal,
>>     The machine that I had seen this issue on before
>> was at a customer 
>> and I couldn't play
>> around with it.   I would like to document this a
>> little bit however.
>>     When you log in with the remote desktop, was a
>> user logged in 
>> locally?   It appears
>> that on XP, locally at least, the first user to log
>> in becomes the 
>> interactive desktop that
>> services will connect to.  There doesn't appear to
>> be a way that I could 
>> find to provide
>> access to the secondary desktops.   I am wondering
>> if it never works for 
>> remote desktops
>> or if it only works if the service is started when
>> nobody is logged in 
>> locally.
>>
>> Cheers,
>> Leif
>>
>>     
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>   

Re: [Wrapper-user] Win Server 2003 and GUI

[Ajmal A. <ajm...@ya...>]

Hi Leif,

I tried the following and still couldnt get the GUI to
be displayed via Remote Desktop.

1. Logged everyone out from the server and then
connect to the server via RDC. No GUI

2. Logged out of the server. Connect locally to the
Server. The GUI is displayed. I then left the session
open and connect via RDC from my PC. Still no GUI.

I think that the issue with Win Server OS is that
there is no 'default' or 'first' session. Each time a
user logs in, a different session is open. We can have
the same user logged in multiple times concurrently
with the same user name...

I hope that helped. Let me know if you need any more
tests carried out...

Cheers,

Ajmal

--- Leif Mortenson <le...@ta...> wrote:

> Ajmal,
>     The machine that I had seen this issue on before
> was at a customer 
> and I couldn't play
> around with it.   I would like to document this a
> little bit however.
>     When you log in with the remote desktop, was a
> user logged in 
> locally?   It appears
> that on XP, locally at least, the first user to log
> in becomes the 
> interactive desktop that
> services will connect to.  There doesn't appear to
> be a way that I could 
> find to provide
> access to the secondary desktops.   I am wondering
> if it never works for 
> remote desktops
> or if it only works if the service is started when
> nobody is logged in 
> locally.
> 
> Cheers,
> Leif
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Wrapper-user] Using wrapper on Solaris 10 x86

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

Thiago,
Version 3.2.0 will clear all this up.  Binaries are native to particular 
hardware as well as the
OS.  The 3.1.2 Solaris version only runs on sparc.   For now, give the 
3.2.0-d prerelease
test vesion.  But DO NOT use this in a distributed project.  The actual 
release will be
coming shortly.
http://wrapper.tanukisoftware.org/tmp/3.2.0-d/wrapper-solaris-x86-32-3.2.0-d.tar.gz

Cheers,
Leif

Thiago Araujo wrote:
> Hi all,
>        I've been using the Java Service Wrapper successfuly to make an application run as a Service in Windows platform (windows 2000 and Windows Server 2003). Now I need to be able to run the same application on a Solaris 10 machine.
>        I've made all the configurations following the instructions on the site. However, when I try to run my shell script (run_service), it returns the following message:
>
> # ./run_service console
> Running Service...
> ./run_service console: ./wrapper: cannot execute
>
>        I am Running Solaris 10 x86 version. The software will actually run on a Solaris 9/SPARC, but I'm trying to run it for now. Is that a problem with my version os Solaris? I've seen messages on the mailing list saying that it is possible to run the Java Service Wrapper on the Solaris 10 Platform, only it doesn't specify whether it is a x86 or SPARC distribution.
>        Any help would be greatly appeciated.
>
> Thanks a lot,
> Thiago
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>   

[Wrapper-user] Using wrapper on Solaris 10 x86

[Thiago A. <ta...@uo...>]

Hi all,
       I've been using the Java Service Wrapper successfuly to make an ap=
plication run as a Service in Windows platform (windows 2000 and Windows =
Server 2003). Now I need to be able to run the same application on a Sola=
ris 10 machine.
       I've made all the configurations following the instructions on the=
 site. However, when I try to run my shell script (run_service), it retur=
ns the following message:

# ./run_service console
Running Service...
./run_service console: ./wrapper: cannot execute

       I am Running Solaris 10 x86 version. The software will actually ru=
n on a Solaris 9/SPARC, but I'm trying to run it for now. Is that a probl=
em with my version os Solaris? I've seen messages on the mailing list say=
ing that it is possible to run the Java Service Wrapper on the Solaris 10=
 Platform, only it doesn't specify whether it is a x86 or SPARC distribut=
ion.
       Any help would be greatly appeciated.

Thanks a lot,
Thiago

Re: [Wrapper-user] Linux daemon question

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

Anat,
> The process terminates when I logout, or at least that's how it seems. 
> I know the wrapper is not shutting it down, however I thought the 
> wrapper is supposed to intercept those signals so that the JVM doesn't 
> get them.
The Wrapper is capable of catching and handling many signals, but the JVM
is a separate child process of the Wrapper.  If it receives a kill -9, 
there is not
anything that can be done about it.  At that point, the os is killing 
the process
at a very low level.  This is true on Windows as well if the user kills 
the java
process from the task manager.  Processes in both platforms are protected
by user privileges.  But if the user has the privilege to kill the 
process, it goes
bye bye.
> I think the wrapper wouldn't be able to restart the application for 
> other reasons as well, but in any case restarting is not the solution 
> for this problem.
I agree, the reason for the restart not working makes sense in your case.
The question is, who is killing the initial java process?
> The original invocation also had a window, but hidden. I am checking 
> whether running in service mode, and if so I have the window hidden. 
> This is currently easier for me to do than to disentangle the GUI code 
> from the application. I plan to separate them, but I hope it will not 
> be necessary to do it now. Please let me know if it is...
I wonder if the JVM is creating some hooks into the window manager simply
by allocating the resources for a window, even if that window is not being
displayed?

Could you create a simple headless application and try this out on your
machine?  I would like to find out if this is being caused by hidden GUI.

I'll try this out on my home linux machine over the weekend.  I only have
access to remote systems today.

Cheers,
Leif
> Leif Mortenson wrote:
>> Anat,
>>    Sorry for the delay.  wrapper.log.service_normal and 
>> wrapper.log.console
>> are the runs that work correctly right?  They both appear to be 
>> running and
>> shutting down correctly.
>>
>>    Both wrapper.log.service_local_logout and 
>> wrapper.log.service_vnc_logout
>> Contain output like the following:
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 
>> (SIGCHLD), source="unknown"
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling 
>> wait().
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child 
>> process should be gone.
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 
>> (SIGCHLD), source="unknown"
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling 
>> wait().
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child 
>> process should be gone.
>> DEBUG  | wrapperp | 2006/02/14 16:20:45 | socket read no code (closed?).
>> DEBUG  | wrapper  | 2006/02/14 16:20:45 | JVM process is gone.
>> ERROR  | wrapper  | 2006/02/14 16:20:45 | JVM exited unexpectedly.
>>
>>    The JVM appears to be running along perfectly normally then its 
>> process
>> suddenly terminates.  The Wrapper is not shutting it down.  It just 
>> dies as if
>> it crashed or its process was killed with 'kill -9'.  The Wrapper is 
>> viewing this
>> as a crash and attempts to restart the application.
>>    It restarts the Java process successfully, but the application is 
>> throwing
>> an exception because it is not able to display a window because a 
>> display
>> no longer exists:
>> INFO   | jvm 2    | 2006/02/14 16:20:57 | Caused by: 
>> java.lang.InternalError: Can't connect to X11 window server using 
>> 'jupiter.eng.tau.ac.il:8.0' as the value of the DISPLAY variable.
>> INFO   | jvm 2    | 2006/02/14 16:20:57 |     at 
>> sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
>>
>>    Since this is happening on a restart, I assume that this means 
>> that the
>> original invocation also had a window up?   It may be that the window is
>> system is sending a kill -9 to all processes with windows that do not
>> shutdown on their own when the Window manager shuts down the display.
>>    I will have to play around with trying to reproduce this.  But it 
>> may depend
>> on the window manager you are using.
>>
>>    I mentioned this before, but add code like the following in your 
>> code to
>> make sure that your application never shows a gui when it is being 
>> run as
>> a daemon / service process:
>>
>> if ( WrapperManager.isLaunchedAsService() )
>> {
>>    // Windowless mode
>> }
>> else
>> {
>>    // Show GUI.
>> }
>>
>> Cheers,
>> Leif
<snip history>

Re: [Wrapper-user] Linux daemon question

[Anat H. <an...@en...>]

Thanks for your help, Leif.

The process terminates when I logout, or at least that's how it seems. I 
know the wrapper is not shutting it down, however I thought the wrapper 
is supposed to intercept those signals so that the JVM doesn't get them.

I think the wrapper wouldn't be able to restart the application for 
other reasons as well, but in any case restarting is not the solution 
for this problem.

The original invocation also had a window, but hidden. I am checking 
whether running in service mode, and if so I have the window hidden. 
This is currently easier for me to do than to disentangle the GUI code 
from the application. I plan to separate them, but I hope it will not be 
necessary to do it now. Please let me know if it is...

Cheers,
Anat

Leif Mortenson wrote:
> Anat,
>    Sorry for the delay.  wrapper.log.service_normal and 
> wrapper.log.console
> are the runs that work correctly right?  They both appear to be 
> running and
> shutting down correctly.
>
>    Both wrapper.log.service_local_logout and 
> wrapper.log.service_vnc_logout
> Contain output like the following:
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
> DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 
> (SIGCHLD), source="unknown"
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling 
> wait().
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child 
> process should be gone.
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
> DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 
> (SIGCHLD), source="unknown"
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling 
> wait().
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child 
> process should be gone.
> DEBUG  | wrapperp | 2006/02/14 16:20:45 | socket read no code (closed?).
> DEBUG  | wrapper  | 2006/02/14 16:20:45 | JVM process is gone.
> ERROR  | wrapper  | 2006/02/14 16:20:45 | JVM exited unexpectedly.
>
>    The JVM appears to be running along perfectly normally then its 
> process
> suddenly terminates.  The Wrapper is not shutting it down.  It just 
> dies as if
> it crashed or its process was killed with 'kill -9'.  The Wrapper is 
> viewing this
> as a crash and attempts to restart the application.
>    It restarts the Java process successfully, but the application is 
> throwing
> an exception because it is not able to display a window because a display
> no longer exists:
> INFO   | jvm 2    | 2006/02/14 16:20:57 | Caused by: 
> java.lang.InternalError: Can't connect to X11 window server using 
> 'jupiter.eng.tau.ac.il:8.0' as the value of the DISPLAY variable.
> INFO   | jvm 2    | 2006/02/14 16:20:57 |     at 
> sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
>
>    Since this is happening on a restart, I assume that this means that 
> the
> original invocation also had a window up?   It may be that the window is
> system is sending a kill -9 to all processes with windows that do not
> shutdown on their own when the Window manager shuts down the display.
>    I will have to play around with trying to reproduce this.  But it 
> may depend
> on the window manager you are using.
>
>    I mentioned this before, but add code like the following in your 
> code to
> make sure that your application never shows a gui when it is being run as
> a daemon / service process:
>
> if ( WrapperManager.isLaunchedAsService() )
> {
>    // Windowless mode
> }
> else
> {
>    // Show GUI.
> }
>
> Cheers,
> Leif
>
>
>
> Anat Halpern wrote:
>> Apparently, sourceforge is blocking zip file attachments, ans also 
>> attachment size is
>> limited to 40K. So I'll try the zip again (just change the extension).
>> -- 
>> Open WebMail Project (http://openwebmail.org)
>>
>>
>> ---------- Original Message -----------
>> From: Leif Mortenson <le...@ta...>
>> To: wra...@li...
>> Sent: Wed, 15 Feb 2006 15:41:45 +0900
>> Subject: Re: [Wrapper-user] Linux daemon question
>>
>>  
>>> Anat,
>>>     You forgot to attach the 4 log files.   I'll need to see them to 
>>> give you more help.
>>> I was expecting this to be working with 3.2.0.
>>>
>>>     Also see my comments below.
>>>
>>> Anat Halpern wrote:
>>>    
>>>> Hi Leif,
>>>>
>>>> Thanks for your response. However, it doesn't seem to be working 
>>>> for me :'(
>>>>
>>>> Leif Mortenson wrote:
>>>>      
>>>>> Anat,
>>>>>    Looking at your log file, this is the cause of the application 
>>>>> being shut down:
>>>>> INFO   | jvm 1    | 2006/02/07 16:42:51 | Processing control 
>>>>> event(WRAPPER_CTRL_SHUTDOWN_EVENT)
>>>>>
>>>>>    There is a bug in 3.1.2 where the JVM is not correctly ignoring 
>>>>> TERM signals
>>>>> even if the IGNORE_SIGNALS flag is set in the sh script.  This has 
>>>>> been fixed
>>>>> for the unreleased 3.2.0.  Could you please download and try out 
>>>>> the latest
>>>>> snapshot build and verify that this fixes the problem for you?
>>>>>
>>>>>    
>>>>> http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-linux-x86-32-3.2.0-d.tar.gz 
>>>>>
>>>>>
>>>>>    You will want to use the new sh script and set the IGNORE_SIGNALS
>>>>> variable to true in the script.
>>>>>         
>>>> I've tried the new files, with the property set to true, but it 
>>>> still shutting down when I logout. Attached are 4 logs - for a 
>>>> console run, and service run which I stopped using <app> stop - 
>>>> those have normal behavior. The other 2 logs are of service runs 
>>>> during which I logout - one running remote through VNC, and the 
>>>> other is run locally.
>>>>      
>>>>>    Also, from your logs, it looks like there is a GUI being 
>>>>> displayed?   That may
>>>>> why your JVM is getting the TERM signals in the first place.
>>>>>         
>>>> Could you explain about that?
>>>>       
>>> I saw references to the "AgentFrame" class in your wrapper.log.  I 
>>> assumed
>>> that this was referring to a GUI Frame.
>>>    
>>>>> In general, daemon
>>>>> processes don't have GUIs.  You should add a call to
>>>>> WrapperManager.isLaunchedAsService()  This method will return true 
>>>>> if the
>>>>> Wrapper is running as a daemon process.  Only show your GUI if it 
>>>>> is false.
>>>>> If you don't want to add a dependency to the wrapper API, look for 
>>>>> the
>>>>> "wrapper.service" system property.
>>>>>         
>>>> I'm not actually showing the GUI, it's hidden when in service mode 
>>>> - it's just a temporary (messy) solution before I remove the GUI. 
>>>> Is there a problem with that?
>>>>       
>>> If it is not being shown, that should be fine.  I was thinking that 
>>> that might be
>>> the reason why you were getting the TERM signal.
>>>     
>> It's hidden. I just don't understand should be the reason for the 
>> signal - sorry for the
>> ignorance...
>>  
>>> Cheers,
>>> Leif
>>>
>>>     
>> ------- End of Original Message -------
>>
>> Thanks,
>> Anat
>>
>>   
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting 
> language
> that extends applications into web and mobile media. Attend the live 
> webcast
> and join the prime developer group breaking into this new coding 
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> +++++++++++++++++++++++++++++++++++++++++++
> This Mail Was Scanned By Mail-seCure System
> at the Tel-Aviv University CC.

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

Re: [Wrapper-user] Win Server 2003 and GUI

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

Ajmal,
    The machine that I had seen this issue on before was at a customer 
and I couldn't play
around with it.   I would like to document this a little bit however.
    When you log in with the remote desktop, was a user logged in 
locally?   It appears
that on XP, locally at least, the first user to log in becomes the 
interactive desktop that
services will connect to.  There doesn't appear to be a way that I could 
find to provide
access to the secondary desktops.   I am wondering if it never works for 
remote desktops
or if it only works if the service is started when nobody is logged in 
locally.

Cheers,
Leif

Ajmal Abdool wrote:
> Hi Leif,
>
> Thanks for your support. I was working via remote
> desktop. I've just connected locally and the GUI is
> displayed. The issue must be with the remote desktop.
>
> Cheers,
>
> Ajmal
>
>
> --- Leif Mortenson <le...@ta...> wrote:
>
>   
>> Ajmal,
>>     Your configuration looks correct.   Are you
>> connecting to this 2003 
>> machine
>> locally?  I have seen that on some systems, the
>> service is unable to 
>> access the
>> desktop if you connect from a remote terminal.
>>     On Windows XP, it is possible to have multiple
>> users logs in at the 
>> same time.
>> Windows services only appear to "interact" with the
>> desktop of the first 
>> user
>> that logs on after (or during) the service being
>> started.
>>     I don't have access to a 2003 system to play
>> around with myself..  
>> Does that
>> apply to you?
>>
>> Cheers,
>> Leif
>>
>> Ajmal Abdool wrote:
>>     
>>> Hi,
>>>
>>> I have an encountered an issue displaying a GUI on
>>>       
>> Win
>>     
>>> Server 2003. The service seems to start normally
>>>       
>> but
>>     
>>> no GUI is visible. 
>>>
>>> This issue does not occur on Win XP Pro though. Is
>>>       
>> it
>>     
>>> an OS specific error? Or is there some rights that
>>> needs to be granted on the Server OS...?
>>>
>>> In my example, I'm using the Tray Example from
>>>       
>> JDIC
>>     
>>> but I've tested other GUIs and it still doesnt
>>>       
>> work...
>>     
>>> Below is a snap shot of the logs file and wrapper
>>> conf:
>>>
>>> /* Log File */
>>> STATUS | wrapper  | 2006/02/22 17:56:03 | Starting
>>>       
>> the
>>     
>>> Test Wrapper Sample Application service...
>>> STATUS | wrapper  | 2006/02/22 17:56:03 | -->
>>>       
>> Wrapper
>>     
>>> Started as Service
>>> STATUS | wrapper  | 2006/02/22 17:56:03 |
>>>       
>> Launching a
>>     
>>> JVM...
>>> INFO   | jvm 1    | 2006/02/22 17:56:03 | Wrapper
>>> (Version 3.1.2) http://wrapper.tanukisoftware.org
>>> INFO   | jvm 1    | 2006/02/22 17:56:03 | 
>>> STATUS | wrapper  | 2006/02/22 17:56:05 | Test
>>>       
>> Wrapper
>>     
>>> Sample Application started.
>>> /* End of Log File */
>>>
>>> /* Wrapper Conf */
>>>
>>>       
> #********************************************************************
>   
>>> # 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=org.tanukisoftware.wrapper.WrapperSimpleApp
>   
>>> # 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=C:\Program
>>> Files\Java\jdic-bin\demo\Tray
>>> wrapper.java.classpath.3=C:\Program
>>> Files\Java\jdic-bin\jdic.jar
>>>
>>>
>>>
>>> # 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=3
>>>
>>> # Maximum Java Heap Size (in MB)
>>> #wrapper.java.maxmemory=64
>>>
>>> # Application parameters.  Add parameters as
>>>       
>> needed
>>     
>>> starting from 1
>>> wrapper.app.parameter.1=Tray
>>>
>>>
>>>
>>>       
> #********************************************************************
>   
>>> # 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=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=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=Test Wrapper Sample
>>>       
>> Application
>>     
>>>       
> #********************************************************************
>   
>>> # 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=testwrapper
>>>
>>> # Display name of the service
>>> wrapper.ntservice.displayname=Test Wrapper Sample
>>> Application
>>>
>>> # Description of the service
>>> wrapper.ntservice.description=Test Wrapper Sample
>>> Application Description
>>>
>>> # 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=true
>>>
>>> wrapper.ntservice.hide-console=false
>>> /* End of Conf File */
>>>
>>> Any help would be much appreciated.
>>>
>>> Thanks,
>>>
>>> Ajmal
>>>   
>>>       
>>
>>
>>     
> -------------------------------------------------------
>   
>> This SF.Net email is sponsored by xPML, a
>> groundbreaking scripting language
>> that extends applications into web and mobile media.
>> Attend the live webcast
>> and join the prime developer group breaking into
>> this new coding territory!
>>
>>     
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>   
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>>
>>     
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>   

Re: [Wrapper-user] Linux daemon question

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

Anat,
    Sorry for the delay.  wrapper.log.service_normal and wrapper.log.console
are the runs that work correctly right?  They both appear to be running and
shutting down correctly.

    Both wrapper.log.service_local_logout and wrapper.log.service_vnc_logout
Contain output like the following:
DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 (SIGCHLD), 
source="unknown"
DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling wait().
DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child process 
should be gone.
DEBUG  | wrapper  | 2006/02/14 16:20:45 | Signal trapped.  Details:
DEBUG  | wrapper  | 2006/02/14 16:20:45 |   signal number=17 (SIGCHLD), 
source="unknown"
DEBUG  | wrapper  | 2006/02/14 16:20:45 | Received SIGCHLD, calling wait().
DEBUG  | wrapper  | 2006/02/14 16:20:45 | wait() returned, child process 
should be gone.
DEBUG  | wrapperp | 2006/02/14 16:20:45 | socket read no code (closed?).
DEBUG  | wrapper  | 2006/02/14 16:20:45 | JVM process is gone.
ERROR  | wrapper  | 2006/02/14 16:20:45 | JVM exited unexpectedly.

    The JVM appears to be running along perfectly normally then its process
suddenly terminates.  The Wrapper is not shutting it down.  It just dies 
as if
it crashed or its process was killed with 'kill -9'.  The Wrapper is 
viewing this
as a crash and attempts to restart the application.
    It restarts the Java process successfully, but the application is 
throwing
an exception because it is not able to display a window because a display
no longer exists:
INFO   | jvm 2    | 2006/02/14 16:20:57 | Caused by: 
java.lang.InternalError: Can't connect to X11 window server using 
'jupiter.eng.tau.ac.il:8.0' as the value of the DISPLAY variable.
INFO   | jvm 2    | 2006/02/14 16:20:57 |     at 
sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)

    Since this is happening on a restart, I assume that this means that the
original invocation also had a window up?   It may be that the window is
system is sending a kill -9 to all processes with windows that do not
shutdown on their own when the Window manager shuts down the display.
    I will have to play around with trying to reproduce this.  But it 
may depend
on the window manager you are using.

    I mentioned this before, but add code like the following in your code to
make sure that your application never shows a gui when it is being run as
a daemon / service process:

if ( WrapperManager.isLaunchedAsService() )
{
    // Windowless mode
}
else
{
    // Show GUI.
}

Cheers,
Leif



Anat Halpern wrote:
> Apparently, sourceforge is blocking zip file attachments, ans also attachment size is
> limited to 40K. So I'll try the zip again (just change the extension).
> --
> Open WebMail Project (http://openwebmail.org)
>
>
> ---------- Original Message -----------
> From: Leif Mortenson <le...@ta...>
> To: wra...@li...
> Sent: Wed, 15 Feb 2006 15:41:45 +0900
> Subject: Re: [Wrapper-user] Linux daemon question
>
>   
>> Anat,
>>     You forgot to attach the 4 log files.   I'll need to see them to 
>> give you more help.
>> I was expecting this to be working with 3.2.0.
>>
>>     Also see my comments below.
>>
>> Anat Halpern wrote:
>>     
>>> Hi Leif,
>>>
>>> Thanks for your response. However, it doesn't seem to be working for 
>>> me :'(
>>>
>>> Leif Mortenson wrote:
>>>       
>>>> Anat,
>>>>    Looking at your log file, this is the cause of the application 
>>>> being shut down:
>>>> INFO   | jvm 1    | 2006/02/07 16:42:51 | Processing control 
>>>> event(WRAPPER_CTRL_SHUTDOWN_EVENT)
>>>>
>>>>    There is a bug in 3.1.2 where the JVM is not correctly ignoring 
>>>> TERM signals
>>>> even if the IGNORE_SIGNALS flag is set in the sh script.  This has 
>>>> been fixed
>>>> for the unreleased 3.2.0.  Could you please download and try out the 
>>>> latest
>>>> snapshot build and verify that this fixes the problem for you?
>>>>
>>>>    
>>>> http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-linux-x86-32-3.2.0-d.tar.gz 
>>>>
>>>>
>>>>    You will want to use the new sh script and set the IGNORE_SIGNALS
>>>> variable to true in the script.
>>>>         
>>> I've tried the new files, with the property set to true, but it still 
>>> shutting down when I logout. Attached are 4 logs - for a console run, 
>>> and service run which I stopped using <app> stop - those have normal 
>>> behavior. The other 2 logs are of service runs during which I logout - 
>>> one running remote through VNC, and the other is run locally.
>>>       
>>>>    Also, from your logs, it looks like there is a GUI being 
>>>> displayed?   That may
>>>> why your JVM is getting the TERM signals in the first place.
>>>>         
>>> Could you explain about that?
>>>       
>> I saw references to the "AgentFrame" class in your wrapper.log.  I assumed
>> that this was referring to a GUI Frame.
>>     
>>>> In general, daemon
>>>> processes don't have GUIs.  You should add a call to
>>>> WrapperManager.isLaunchedAsService()  This method will return true if 
>>>> the
>>>> Wrapper is running as a daemon process.  Only show your GUI if it is 
>>>> false.
>>>> If you don't want to add a dependency to the wrapper API, look for the
>>>> "wrapper.service" system property.
>>>>         
>>> I'm not actually showing the GUI, it's hidden when in service mode - 
>>> it's just a temporary (messy) solution before I remove the GUI. Is 
>>> there a problem with that?
>>>       
>> If it is not being shown, that should be fine.  I was thinking that that 
>> might be
>> the reason why you were getting the TERM signal.
>>     
> It's hidden. I just don't understand should be the reason for the signal - sorry for the
> ignorance...
>   
>> Cheers,
>> Leif
>>
>>     
> ------- End of Original Message -------
>
> Thanks,
> Anat
>
>   

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

[Sam R. <sam...@gm...>]

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 lik=
e
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=3D..\java\bin\java
wrapper.java.command=3D{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=3DMainClass

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3D../wrapper/wrapper.jar
wrapper.java.classpath.2=3D../bin/{jar}
wrapper.java.classpath.3=3D../lib/j2ee/mail.jar
wrapper.java.classpath.4=3D../lib/xml/jdom.jar
wrapper.java.classpath.5=3D../lib/j2ee/activation.jar
wrapper.java.classpath.6=3D../lib/j2ee/servlet.jar
wrapper.java.classpath.7=3D../lib/apache/commons/commons-lang-1.0.1.jar
wrapper.java.classpath.8=3D../lib/db/mysql.jar
wrapper.java.classpath.9=3D../lib/util/concurrent.jar
wrapper.java.classpath.10=3D../lib/util/jetty.jar
wrapper.java.classpath.11=3D../lib/apache/commons/commons-logging-api.jar
wrapper.java.classpath.12=3D../lib/util/tools.jar
wrapper.java.classpath.13=3D../lib/apache/commons/commons-io-1.1.jar
wrapper.java.classpath.14=3D../lib/apache/ant/ant.jar
wrapper.java.classpath.15=3D../lib/apache/axis/axis.jar
wrapper.java.classpath.16=3D../lib/apache/axis/axis-ant.jar
wrapper.java.classpath.17=3D../lib/apache/axis/axis-schema.jar
wrapper.java.classpath.18=3D../lib/apache/commons/commons-discovery-0.2.jar
wrapper.java.classpath.19=3D../lib/apache/commons/commons-el.jar
wrapper.java.classpath.20=3D../lib/apache/jasper/jasper-compiler.jar
wrapper.java.classpath.21=3D../lib/apache/jasper/jasper-runtime.jar
wrapper.java.classpath.22=3D../lib/apache/axis/jaxrpc.jar
wrapper.java.classpath.23=3D../lib/util/jmx.jar
wrapper.java.classpath.24=3D../lib/apache/log4j/log4j-1.2.8.jar
wrapper.java.classpath.25=3D../lib/apache/mx4j/mx4j.jar
wrapper.java.classpath.26=3D../lib/apache/mx4j/mx4j-remote.jar
wrapper.java.classpath.27=3D../lib/apache/mx4j/mx4j-tools.jar
wrapper.java.classpath.28=3D../lib/apache/axis/opensaml-1.0.1.jar
wrapper.java.classpath.29=3D../lib/apache/axis/saaj.jar
wrapper.java.classpath.30=3D../lib/apache/axis/wsdl4j-1.5.1.jar
wrapper.java.classpath.31=3D../lib/apache/axis/wss4j.jar
wrapper.java.classpath.32=3D../lib/apache/xml/xercesImpl.jar
wrapper.java.classpath.33=3D../lib/apache/xml/xml-apis.jar
wrapper.java.classpath.34=3D../lib/xml/xmlsec-1.3.0.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=3D../wrapper/
wrapper.java.library.path.2=3D./

# Java Additional Parameters
wrapper.java.additional.1=3D-server
wrapper.java.additional.2=3D-Dase.tag=3D{tag}
wrapper.java.additional.3=3D-Dwrapper.actionserver.port=3D{actionport}
wrapper.java.additional.4=3D-Djava.io.tmpdir=3D.
wrapper.java.additional.5=3D-Dsun.rmi.server.exceptionTrace=3Dtrue

# Sets the working directory for the application.
wrapper.working.dir=3D../{tag}

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=3D64

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=3D512

#Dump threads when a failure to exit occurs
wrapper.request_thread_dump_on_failed_jvm_exit=3DTRUE

#Time before bailing the JVM
wrapper.jvm_exit.timeout=3D180

#Delay between an internal shutdown and start
wrapper.restart.delay=3D30

#How long to wait for the jvm to stop before killing it
wrapper.shutdown.timeout=3D250

#Maximum number of times to restart JVM
wrapper.max_failed_invocations=3D100

#********************************************************************
# Wrapper Logging Properties
#********************************************************************

# Format of output for the console.  (See docs for formats)
wrapper.console.format=3D

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=3DNONE

# Log file to use for wrapper output logging.
wrapper.logfile=3Dlog/ase.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=3DM

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=3DINFO

# 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 =3D 10 megabytes.
wrapper.logfile.maxsize=3D10m

# 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=3D50

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=3DERROR

# Ping Interval - How often the JVM will be pinged for life
wrapper.ping.interval=3D3595

#Ping Timeout - How long to wait for a response from the JVM
wrapper.ping.timeout=3D3600

#Filters and Triggers - Actions: RESTART, SHUTDOWN, NONE
#wrapper.filter.trigger.1=3Djava.lang.OutOfMemoryError
#wrapper.filter.action.1=3DRESTART

#********************************************************************
# 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=3D{tag}

# Display name of the service
wrapper.ntservice.displayname=3D{tag}

# Description of the service
wrapper.ntservice.description=3DDescription

# Service dependencies.  Add dependencies as needed starting from 1
#wrapper.ntservice.dependency.1=3Dmysql

# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=3DAUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=3Dfalse

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 th=
e
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=3D../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

Re: [Wrapper-user] hiding wrapper console

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

Anat,
    This is not currently possible to do with the Wrapper.  It is on my 
todo list.
I am going to have to create a second wrapperw.exe binary for windows which
runs as a windows application rather than a console app.  Java does the same
type of thing with java.exe and javaw.exe.

Cheers,
Leif

Anat Halpern wrote:
> Hi Ajmal,
>
> Thanks for your reply.
> I was having a problem with hiding the cmd window, not with creating 
> the shortcut. Maybe I didn't understand your solution, but I don't see 
> how creating another batch file will help in hiding the console.
> What I currently have is shortcuts from the programs menu that call 
> the different functions of the wrapper. However, the console always 
> pops up, even if for a couple of seconds - I don't like it...
>
> Thanks,
> Anat
>
> Ajmal Abdool wrote:
>> Hi Anat,
>>
>> You can do that by simply creating different batch
>> files. e.g to start the service, do the following:
>> 1. Open Notepad
>> 2. Write the command that you'ld normally type on the
>> cmd window eg "C:\JavaWrapper\MyApp.bat start" without
>> the quotes "
>> 3. Save the file as ServiceStart.bat on your desktop.
>> 4. Double click on file to start the service.
>>
>> The same can be repeated to install, uninstall, start
>> or stop the service.
>>
>> Hope that helped.
>>
>> Cheers,
>>
>> Ajmal
>>
>> --- Anat Halpern <an...@en...> wrote:
>>
>>   
>>> Hi Leif,
>>>
>>> I'd like to have shortcuts that will call
>>> wrapper.exe (for running the 
>>> service, uninstalling, etc.), but I don't want them
>>> to open up a cmd 
>>> window. Is there any way to get around it?
>>>
>>> BTW, still waiting on that linux question - just in
>>> case you forgot me ;)
>>>
>>> Thanks,
>>> Anat
>>>       

Re: [Wrapper-user] hiding wrapper console

[Anat H. <an...@en...>]

Hi Ajmal,

Thanks for your reply.
I was having a problem with hiding the cmd window, not with creating the 
shortcut. Maybe I didn't understand your solution, but I don't see how 
creating another batch file will help in hiding the console.
What I currently have is shortcuts from the programs menu that call the 
different functions of the wrapper. However, the console always pops up, 
even if for a couple of seconds - I don't like it...

Thanks,
Anat

Ajmal Abdool wrote:
> Hi Anat,
>
> You can do that by simply creating different batch
> files. e.g to start the service, do the following:
> 1. Open Notepad
> 2. Write the command that you'ld normally type on the
> cmd window eg "C:\JavaWrapper\MyApp.bat start" without
> the quotes "
> 3. Save the file as ServiceStart.bat on your desktop.
> 4. Double click on file to start the service.
>
> The same can be repeated to install, uninstall, start
> or stop the service.
>
> Hope that helped.
>
> Cheers,
>
> Ajmal
>
> --- Anat Halpern <an...@en...> wrote:
>
>   
>> Hi Leif,
>>
>> I'd like to have shortcuts that will call
>> wrapper.exe (for running the 
>> service, uninstalling, etc.), but I don't want them
>> to open up a cmd 
>> window. Is there any way to get around it?
>>
>> BTW, still waiting on that linux question - just in
>> case you forgot me ;)
>>
>> Thanks,
>> Anat
>>
>>
>>
>>
>>     
> -------------------------------------------------------
>   
>> This SF.Net email is sponsored by xPML, a
>> groundbreaking scripting language
>> that extends applications into web and mobile media.
>> Attend the live webcast
>> and join the prime developer group breaking into
>> this new coding territory!
>>
>>     
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>   
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>>
>>     
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>  
>  +++++++++++++++++++++++++++++++++++++++++++
>  This Mail Was Scanned By Mail-seCure System
>  at the Tel-Aviv University CC.
>   

Re: [Wrapper-user] hiding wrapper console

[Ajmal A. <ajm...@ya...>]

Hi Anat,

You can do that by simply creating different batch
files. e.g to start the service, do the following:
1. Open Notepad
2. Write the command that you'ld normally type on the
cmd window eg "C:\JavaWrapper\MyApp.bat start" without
the quotes "
3. Save the file as ServiceStart.bat on your desktop.
4. Double click on file to start the service.

The same can be repeated to install, uninstall, start
or stop the service.

Hope that helped.

Cheers,

Ajmal

--- Anat Halpern <an...@en...> wrote:

> Hi Leif,
> 
> I'd like to have shortcuts that will call
> wrapper.exe (for running the 
> service, uninstalling, etc.), but I don't want them
> to open up a cmd 
> window. Is there any way to get around it?
> 
> BTW, still waiting on that linux question - just in
> case you forgot me ;)
> 
> Thanks,
> Anat
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
> groundbreaking scripting language
> that extends applications into web and mobile media.
> Attend the live webcast
> and join the prime developer group breaking into
> this new coding territory!
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
>
https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Wrapper-user] hiding wrapper console

[Anat H. <an...@en...>]

Hi Leif,

I'd like to have shortcuts that will call wrapper.exe (for running the 
service, uninstalling, etc.), but I don't want them to open up a cmd 
window. Is there any way to get around it?

BTW, still waiting on that linux question - just in case you forgot me ;)

Thanks,
Anat

Re: [Wrapper-user] Win Server 2003 and GUI

[Ajmal A. <ajm...@ya...>]

Hi Leif,

Thanks for your support. I was working via remote
desktop. I've just connected locally and the GUI is
displayed. The issue must be with the remote desktop.

Cheers,

Ajmal


--- Leif Mortenson <le...@ta...> wrote:

> Ajmal,
>     Your configuration looks correct.   Are you
> connecting to this 2003 
> machine
> locally?  I have seen that on some systems, the
> service is unable to 
> access the
> desktop if you connect from a remote terminal.
>     On Windows XP, it is possible to have multiple
> users logs in at the 
> same time.
> Windows services only appear to "interact" with the
> desktop of the first 
> user
> that logs on after (or during) the service being
> started.
>     I don't have access to a 2003 system to play
> around with myself..  
> Does that
> apply to you?
> 
> Cheers,
> Leif
> 
> Ajmal Abdool wrote:
> > Hi,
> >
> > I have an encountered an issue displaying a GUI on
> Win
> > Server 2003. The service seems to start normally
> but
> > no GUI is visible. 
> >
> > This issue does not occur on Win XP Pro though. Is
> it
> > an OS specific error? Or is there some rights that
> > needs to be granted on the Server OS...?
> >
> > In my example, I'm using the Tray Example from
> JDIC
> > but I've tested other GUIs and it still doesnt
> work...
> >
> > Below is a snap shot of the logs file and wrapper
> > conf:
> >
> > /* Log File */
> > STATUS | wrapper  | 2006/02/22 17:56:03 | Starting
> the
> > Test Wrapper Sample Application service...
> > STATUS | wrapper  | 2006/02/22 17:56:03 | -->
> Wrapper
> > Started as Service
> > STATUS | wrapper  | 2006/02/22 17:56:03 |
> Launching a
> > JVM...
> > INFO   | jvm 1    | 2006/02/22 17:56:03 | Wrapper
> > (Version 3.1.2) http://wrapper.tanukisoftware.org
> > INFO   | jvm 1    | 2006/02/22 17:56:03 | 
> > STATUS | wrapper  | 2006/02/22 17:56:05 | Test
> Wrapper
> > Sample Application started.
> > /* End of Log File */
> >
> > /* Wrapper Conf */
> >
>
#********************************************************************
> > # 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=org.tanukisoftware.wrapper.WrapperSimpleApp
> >
> > # 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=C:\Program
> > Files\Java\jdic-bin\demo\Tray
> > wrapper.java.classpath.3=C:\Program
> > Files\Java\jdic-bin\jdic.jar
> >
> >
> >
> > # 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=3
> >
> > # Maximum Java Heap Size (in MB)
> > #wrapper.java.maxmemory=64
> >
> > # Application parameters.  Add parameters as
> needed
> > starting from 1
> > wrapper.app.parameter.1=Tray
> >
> >
> >
>
#********************************************************************
> > # 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=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=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=Test Wrapper Sample
> Application
> >
> >
>
#********************************************************************
> > # 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=testwrapper
> >
> > # Display name of the service
> > wrapper.ntservice.displayname=Test Wrapper Sample
> > Application
> >
> > # Description of the service
> > wrapper.ntservice.description=Test Wrapper Sample
> > Application Description
> >
> > # 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=true
> >
> > wrapper.ntservice.hide-console=false
> > /* End of Conf File */
> >
> > Any help would be much appreciated.
> >
> > Thanks,
> >
> > Ajmal
> >   
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by xPML, a
> groundbreaking scripting language
> that extends applications into web and mobile media.
> Attend the live webcast
> and join the prime developer group breaking into
> this new coding territory!
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
>
https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: [Wrapper-user] Win Server 2003 and GUI

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

Ajmal,
    Your configuration looks correct.   Are you connecting to this 2003 
machine
locally?  I have seen that on some systems, the service is unable to 
access the
desktop if you connect from a remote terminal.
    On Windows XP, it is possible to have multiple users logs in at the 
same time.
Windows services only appear to "interact" with the desktop of the first 
user
that logs on after (or during) the service being started.
    I don't have access to a 2003 system to play around with myself..  
Does that
apply to you?

Cheers,
Leif

Ajmal Abdool wrote:
> Hi,
>
> I have an encountered an issue displaying a GUI on Win
> Server 2003. The service seems to start normally but
> no GUI is visible. 
>
> This issue does not occur on Win XP Pro though. Is it
> an OS specific error? Or is there some rights that
> needs to be granted on the Server OS...?
>
> In my example, I'm using the Tray Example from JDIC
> but I've tested other GUIs and it still doesnt work...
>
> Below is a snap shot of the logs file and wrapper
> conf:
>
> /* Log File */
> STATUS | wrapper  | 2006/02/22 17:56:03 | Starting the
> Test Wrapper Sample Application service...
> STATUS | wrapper  | 2006/02/22 17:56:03 | --> Wrapper
> Started as Service
> STATUS | wrapper  | 2006/02/22 17:56:03 | Launching a
> JVM...
> INFO   | jvm 1    | 2006/02/22 17:56:03 | Wrapper
> (Version 3.1.2) http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2006/02/22 17:56:03 | 
> STATUS | wrapper  | 2006/02/22 17:56:05 | Test Wrapper
> Sample Application started.
> /* End of Log File */
>
> /* Wrapper Conf */
> #********************************************************************
> # 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=org.tanukisoftware.wrapper.WrapperSimpleApp
>
> # 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=C:\Program
> Files\Java\jdic-bin\demo\Tray
> wrapper.java.classpath.3=C:\Program
> Files\Java\jdic-bin\jdic.jar
>
>
>
> # 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=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters.  Add parameters as needed
> starting from 1
> wrapper.app.parameter.1=Tray
>
>
> #********************************************************************
> # 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=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=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=Test Wrapper Sample Application
>
> #********************************************************************
> # 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=testwrapper
>
> # Display name of the service
> wrapper.ntservice.displayname=Test Wrapper Sample
> Application
>
> # Description of the service
> wrapper.ntservice.description=Test Wrapper Sample
> Application Description
>
> # 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=true
>
> wrapper.ntservice.hide-console=false
> /* End of Conf File */
>
> Any help would be much appreciated.
>
> Thanks,
>
> Ajmal
>   

[Wrapper-user] Win Server 2003 and GUI

[Ajmal A. <ajm...@ya...>]

Hi,

I have an encountered an issue displaying a GUI on Win
Server 2003. The service seems to start normally but
no GUI is visible. 

This issue does not occur on Win XP Pro though. Is it
an OS specific error? Or is there some rights that
needs to be granted on the Server OS...?

In my example, I'm using the Tray Example from JDIC
but I've tested other GUIs and it still doesnt work...

Below is a snap shot of the logs file and wrapper
conf:

/* Log File */
STATUS | wrapper  | 2006/02/22 17:56:03 | Starting the
Test Wrapper Sample Application service...
STATUS | wrapper  | 2006/02/22 17:56:03 | --> Wrapper
Started as Service
STATUS | wrapper  | 2006/02/22 17:56:03 | Launching a
JVM...
INFO   | jvm 1    | 2006/02/22 17:56:03 | Wrapper
(Version 3.1.2) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2006/02/22 17:56:03 | 
STATUS | wrapper  | 2006/02/22 17:56:05 | Test Wrapper
Sample Application started.
/* End of Log File */

/* Wrapper Conf */
#********************************************************************
# 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=org.tanukisoftware.wrapper.WrapperSimpleApp

# 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=C:\Program
Files\Java\jdic-bin\demo\Tray
wrapper.java.classpath.3=C:\Program
Files\Java\jdic-bin\jdic.jar



# 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=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application parameters.  Add parameters as needed
starting from 1
wrapper.app.parameter.1=Tray


#********************************************************************
# 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=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=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=Test Wrapper Sample Application

#********************************************************************
# 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=testwrapper

# Display name of the service
wrapper.ntservice.displayname=Test Wrapper Sample
Application

# Description of the service
wrapper.ntservice.description=Test Wrapper Sample
Application Description

# 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=true

wrapper.ntservice.hide-console=false
/* End of Conf File */

Any help would be much appreciated.

Thanks,

Ajmal

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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

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

Sam,
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.

> >Strange. Where those two times on the same system? Or different ones? 
> It has occurred on two different systems, both running Windows 2003 
> and having varying amounts of windows updates completed.
>
> >I can't think of anything having to do with the Wrapper that would be 
> causing this.  Were there any
> >other files being accessed by that JVM? Did they also get deleted?  
> It does not appear that jvm related files are remove, only those files 
> related to the java service wrapper and listed in the wrapper.conf 
> file in the classpath.  In my case, this was our .jar files for both 
> services that had this issue occur, and the associated library files.
So you have seen this with multiple applications running? ...
> >Was the wrapper.log file still there?
> There is no wrapper.log file present (the wrapper.exe, .dll and .jar 
> are all removed - but the services do remain in the windows services 
> list) - where would the wrapper.log be located, and would it only be 
> created if particular log settings were in place in the wrapper.conf's?
See above.
> >Does it show that the JVM and Wrapper shutdown cleanly before the 
> reboot, or did the system >appear to shutdown suddenly?
> The system does not shutdown on its own, we merely performed a reboot 
> after an install and have now seen this occur 3 times (all the more 
> reason perhaps to move to our UNIX solution exclusively)
I have never seen or heard of any problems like this before, so that may 
still be
a bit hasty.
> I appreciate the quick response and the help though. Thanks Leif
No problem.  Still no help though :-/

Cheers,
Leif

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

[Sam R. <sam...@gm...>]

>Strange. Where those two times on the same system? Or different ones?
It has occurred on two different systems, both running Windows 2003 and
having varying amounts of windows updates completed.

>I can't think of anything having to do with the Wrapper that would be
causing this.  Were there any
>other files being accessed by that JVM? Did they also get deleted?
It does not appear that jvm related files are remove, only those files
related to the java service wrapper and listed in the wrapper.conf file in
the classpath.  In my case, this was our .jar files for both services that
had this issue occur, and the associated library files.

>Was the wrapper.log file still there?
There is no wrapper.log file present (the wrapper.exe, .dll and .jar are al=
l
removed - but the services do remain in the windows services list) - where
would the wrapper.log be located, and would it only be created if particula=
r
log settings were in place in the wrapper.conf's?

>Does it show that the JVM and Wrapper shutdown cleanly before the reboot,
or did the system >appear to shutdown suddenly?
The system does not shutdown on its own, we merely performed a reboot after
an install and have now seen this occur 3 times (all the more reason perhap=
s
to move to our UNIX solution exclusively)

>A few years ago, I was running a Windows XP system with a FAT32 file
system.  Every once in a >while the JVM would crash and would not come up
again unless I rebooted the system. I would get >strange errors about not
being able to read some of the DLLs.. After a reboot, it would sometimes
>work. But other times, the DLLs would be permanently corrupted, requiring =
a
Java reinstall. Never >made any sense to me as the system should only be
reading those files when running the JVM. >Hasn't happened since I moved to
NTFS.
I checked the file system type this morning and it is indeed NTFS, and our
problems don't seem to be related to the jvm files, but i won't rule
anything out at the moment.

>There will always be things in this universe that man was not meant to
understand...
Very true.

I appreciate the quick response and the help though. Thanks Leif

Sam Russell

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

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

Sam,
> Does the java service wrapper support Windows 2003?  I do not see it 
> listed in the Operating Systems list (NT, 2000 and XP are listed).  Is 
> this a simple omission or is it not tested/supported yet?
I don't have access to a Windows 2003 system to do testing personally, 
but I know
that users have used it successfully.
> Also, an issue has began occuring whereby all files associated with 
> our services are being removed upon reboot of the server.  All wrapper 
> files (jar, dll and exe) and all the jars listed in the classpath for 
> the services are removed - but not always(it's happened twice now)! 
>  I'm assuming this is something i'm going to have to troubleshoot 
> myself, but if anyone has any insight or has had similar issues please 
> let me know.  Our services are being installed with installshield and 
> the issues are being seen on Windows 2003 (note the question above).
Strange.  Where those two times on the same system?  Or different ones?  
I can't think
of anything having to do with the Wrapper that would be causing this.  
Were there any
other files being accessed by that JVM?  Did they also get deleted?
Was the wrapper.log file still there?  Does it show that the JVM and 
Wrapper shutdown
cleanly before the reboot, or did the system appear to shutdown suddenly?

A few years ago, I was running a Windows XP system with a FAT32 file system.
Every once in a while the JVM would crash and would not come up again unless
I rebooted the system.  I would get strange errors about not being able 
to read some
of the DLLs..  After a reboot, it would sometimes work.  But other 
times, the DLLs
would be permanently corrupted, requiring a Java reinstall.  Never made 
any sense to
me as the system should only be reading those files when running the 
JVM.  Hasn't
happened since I moved to NTFS.

There will always be things in this universe that man was not meant to 
understand...
:-/

Cheers,
Leif

[Wrapper-user] Windows 2003 support and restart issue

[Sam R. <sam...@gm...>]

Does the java service wrapper support Windows 2003?  I do not see it listed
in the Operating Systems list (NT, 2000 and XP are listed).  Is this a
simple omission or is it not tested/supported yet?

Also, an issue has began occuring whereby all files associated with our
services are being removed upon reboot of the server.  All wrapper files
(jar, dll and exe) and all the jars listed in the classpath for the service=
s
are removed - but not always(it's happened twice now)!  I'm assuming this i=
s
something i'm going to have to troubleshoot myself, but if anyone has any
insight or has had similar issues please let me know.  Our services are
being installed with installshield and the issues are being seen on Windows
2003 (note the question above).

Thanks,

Sam Russell

Re: [Wrapper-user] Linux daemon question

[Anat H. <an...@en...>]

Apparently, sourceforge is blocking zip file attachments, ans also attachment size is
limited to 40K. So I'll try the zip again (just change the extension).
--
Open WebMail Project (http://openwebmail.org)


---------- Original Message -----------
From: Leif Mortenson <le...@ta...>
To: wra...@li...
Sent: Wed, 15 Feb 2006 15:41:45 +0900
Subject: Re: [Wrapper-user] Linux daemon question

> Anat,
>     You forgot to attach the 4 log files.   I'll need to see them to 
> give you more help.
> I was expecting this to be working with 3.2.0.
> 
>     Also see my comments below.
> 
> Anat Halpern wrote:
> > Hi Leif,
> >
> > Thanks for your response. However, it doesn't seem to be working for 
> > me :'(
> >
> > Leif Mortenson wrote:
> >> Anat,
> >>    Looking at your log file, this is the cause of the application 
> >> being shut down:
> >> INFO   | jvm 1    | 2006/02/07 16:42:51 | Processing control 
> >> event(WRAPPER_CTRL_SHUTDOWN_EVENT)
> >>
> >>    There is a bug in 3.1.2 where the JVM is not correctly ignoring 
> >> TERM signals
> >> even if the IGNORE_SIGNALS flag is set in the sh script.  This has 
> >> been fixed
> >> for the unreleased 3.2.0.  Could you please download and try out the 
> >> latest
> >> snapshot build and verify that this fixes the problem for you?
> >>
> >>    
> >> http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-linux-x86-32-3.2.0-d.tar.gz 
> >>
> >>
> >>    You will want to use the new sh script and set the IGNORE_SIGNALS
> >> variable to true in the script.
> > I've tried the new files, with the property set to true, but it still 
> > shutting down when I logout. Attached are 4 logs - for a console run, 
> > and service run which I stopped using <app> stop - those have normal 
> > behavior. The other 2 logs are of service runs during which I logout - 
> > one running remote through VNC, and the other is run locally.
> >>
> >>    Also, from your logs, it looks like there is a GUI being 
> >> displayed?   That may
> >> why your JVM is getting the TERM signals in the first place.
> > Could you explain about that?
> I saw references to the "AgentFrame" class in your wrapper.log.  I assumed
> that this was referring to a GUI Frame.
> >> In general, daemon
> >> processes don't have GUIs.  You should add a call to
> >> WrapperManager.isLaunchedAsService()  This method will return true if 
> >> the
> >> Wrapper is running as a daemon process.  Only show your GUI if it is 
> >> false.
> >> If you don't want to add a dependency to the wrapper API, look for the
> >> "wrapper.service" system property.
> > I'm not actually showing the GUI, it's hidden when in service mode - 
> > it's just a temporary (messy) solution before I remove the GUI. Is 
> > there a problem with that?
> If it is not being shown, that should be fine.  I was thinking that that 
> might be
> the reason why you were getting the TERM signal.
It's hidden. I just don't understand should be the reason for the signal - sorry for the
ignorance...
> 
> Cheers,
> Leif
> 
------- End of Original Message -------

Thanks,
Anat

Re: [Wrapper-user] Wrapper pre release 3.2.0-d

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

I am aiming for next week.

Michael 'buk' Scherer wrote:
> Good morning.
>
> Going to test these babies right away.
> How long do you plan, if no major bugs appear, until the release?
>
> I know this is an awkward question but I definetly _need_ 3.2.0 :]
> Therese something I coded against a 3.2.0-b and I guess my boss starts bitching 
> about using an "unstable/unreleased" version. Which he is sort of right with.
>
> Greetings,
>  Michael
>   

Re: [Wrapper-user] Failed to connect to the Wrapper error, service will not start

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

Steve,
What does the very top of your log file look like? Version 3.0.5 starts as
follows with debug output enabled:
wrapper | --> Wrapper Started as Console
wrapperp | server listening on port 32001.
wrapper | Launching a JVM...
wrapper | command: "C:\Sun\jdk1.3.1_03\bin\java.exe" ...

Were there any warnings up there? Your java process is attempting to
open its backend socket to port 32000. From the error message, it doesn't
look like the Wrapper process is listening.

It this reproduceable? If so, could you try it with version 3.1.2? There
have been quite a few changes since 3.0.5, but I don't see anything that
would
be related.

Cheers,
Leif

Buchanan, Steve G. wrote:
>
> Wrapper service will not start, getting the following error. I have
> the same service running on several dell boxes but having problem with
> on one of the dell boxes.
>
> STATUS | wrapper | 2006/02/13 12:40:08 | Launching a JVM...
>
> DEBUG | wrapper | 2006/02/13 12:40:08 | command:
> "..\j2re1.4.2_03\bin\java" -Xss10M -Xms10m -Xmx256m
> -Djava.library.path="../lib" -classpath
> "../lib/wrapper.jar;../SitOhiServer.jar;../"
> -Dwrapper.key="gKvLC5ktpo1QecnA" -Dwrapper.port=32000
> -Dwrapper.debug="TRUE" -Dwrapper.service="TRUE"
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=5
> org.tanukisoftware.wrapper.WrapperSimpleApp sitohi.server.SitOhiServer
>
> DEBUG | wrapper | 2006/02/13 12:40:08 | Java Virtual Machine started
> (PID=2460)
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Wrapper Manager: JVM #5
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Wrapper Manager: Registering
> shutdown hook
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Wrapper Manager: Using wrapper
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Calling native initialization method.
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Initializing WrapperManager
> native library.
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Java Executable:
> C:\SitOhiServer\j2re1.4.2_03\bin\java.exe
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Java Version : 1.4.2_03-b02 Java
> HotSpot(TM) Client VM
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Java VM Vendor : Sun Microsystems
> Inc.
>
> INFO | jvm 5 | 2006/02/13 12:40:08 |
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Wrapper (Version 3.0.5)
>
> INFO | jvm 5 | 2006/02/13 12:40:08 |
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Open socket to wrapper...
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Failed to connect to the Wrapper.
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | java.net.ConnectException:
> Connection refused: connect
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Exiting JVM...
>
> INFO | jvm 5 | 2006/02/13 12:40:08 | Send a packet STOP : 1
>
> INFO | jvm 5 | 2006/02/13 12:40:09 | Send a packet STOPPED : 1
>
> ERROR | wrapper | 2006/02/13 12:40:09 | JVM exited while loading the
> application.
>
> DEBUG | wrapper | 2006/02/13 12:40:09 | JVM was only running for 1
> seconds leading to a failed restart count of 5.
>
> FATAL | wrapper | 2006/02/13 12:40:09 | There were 5 failed launches
> in a row, each lasting less than 300 seconds. Giving up.
>
> FATAL | wrapper | 2006/02/13 12:40:09 | There may be a configuration
> problem: please check the logs.
>
> STATUS | wrapper | 2006/02/13 12:40:09 | <-- Wrapper Stopped
>

Re: [Wrapper-user] Linux daemon question

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

Anat,
    You forgot to attach the 4 log files.   I'll need to see them to 
give you more help.
I was expecting this to be working with 3.2.0.

    Also see my comments below.

Anat Halpern wrote:
> Hi Leif,
>
> Thanks for your response. However, it doesn't seem to be working for 
> me :'(
>
> Leif Mortenson wrote:
>> Anat,
>>    Looking at your log file, this is the cause of the application 
>> being shut down:
>> INFO   | jvm 1    | 2006/02/07 16:42:51 | Processing control 
>> event(WRAPPER_CTRL_SHUTDOWN_EVENT)
>>
>>    There is a bug in 3.1.2 where the JVM is not correctly ignoring 
>> TERM signals
>> even if the IGNORE_SIGNALS flag is set in the sh script.  This has 
>> been fixed
>> for the unreleased 3.2.0.  Could you please download and try out the 
>> latest
>> snapshot build and verify that this fixes the problem for you?
>>
>>    
>> http://wrapper.tanukisoftware.org/tmp/3.1.2-d/wrapper-linux-x86-32-3.2.0-d.tar.gz 
>>
>>
>>    You will want to use the new sh script and set the IGNORE_SIGNALS
>> variable to true in the script.
> I've tried the new files, with the property set to true, but it still 
> shutting down when I logout. Attached are 4 logs - for a console run, 
> and service run which I stopped using <app> stop - those have normal 
> behavior. The other 2 logs are of service runs during which I logout - 
> one running remote through VNC, and the other is run locally.
>>
>>    Also, from your logs, it looks like there is a GUI being 
>> displayed?   That may
>> why your JVM is getting the TERM signals in the first place.
> Could you explain about that?
I saw references to the "AgentFrame" class in your wrapper.log.  I assumed
that this was referring to a GUI Frame.
>> In general, daemon
>> processes don't have GUIs.  You should add a call to
>> WrapperManager.isLaunchedAsService()  This method will return true if 
>> the
>> Wrapper is running as a daemon process.  Only show your GUI if it is 
>> false.
>> If you don't want to add a dependency to the wrapper API, look for the
>> "wrapper.service" system property.
> I'm not actually showing the GUI, it's hidden when in service mode - 
> it's just a temporary (messy) solution before I remove the GUI. Is 
> there a problem with that?
If it is not being shown, that should be fine.  I was thinking that that 
might be
the reason why you were getting the TERM signal.

Cheers,
Leif