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

[Wrapper-user] Unable to load the Wrapper's native library 'wrapper.dll'

[Dominik.S <Dom...@se...>]

Hi,

i have a problem when using the wrapper.
I use the wrapper after the installation of some software to check
(under windows) if the user has admin rights. This all works perfect
"standalone", but when i am using the wrapper=20
within my installer (izPack by the way) i get an error when the wrapper
tries to load the DLL:

I just copy'd the wrapper.dll to a directory and have written an own
izpack panel to check for windows userrights using the wrapper. But when
the wrapper tries to acccess the "wrapper.dll" I get the following
error:


Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org

WARNING - The wrapper.native_library system property was not
          set. Using the default value, 'wrapper'.

WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
          The file is located on the path at the following location but
          could not be loaded:
            C:\Programme\SOME_APPLICATION\ext\wrapper\lib\wrapper.dll
          Please verify that the file is readable by the current user
          and that the file has not been corrupted in any way.
          One common cause of this problem is running a 32-bit version
          of the Wrapper with a 64-bit version of Java, or vica versa.
          This is a 32-bit JVM.
          System signals will not be handled correctly.


I can't figure out what should be wrong with the wrapper.dll...

Any ideas what could be the reason for this problem?

Thanks in advance,
   dominik
###########################################=0A=
=0A=
This message has been scanned by F-Secure Anti-Virus.=0A=
For more information, connect to http://www.f-secure.com/

Re: [Wrapper-user] Cannot find library libwrapper.so on HPUX

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

Francois,
Sorry about the lack of the 3.2.0 64 bit HP-UX distribution.  I was not 
able to find
someone to help with the build that time around.

The correct file name should be libwrapper.sl.  As I understand it, that 
is true for both the
32 and 64 bit versions of HP-UX.   3.2.1 will do things slightly 
differently.  But up until
3.2.0, I had some code which manually built what I thought would be the 
correct native
library name and then used that in error messages.  The JVM has always 
used its own
logic to actually locate the file however.

With the libwrapper.sl naming, what is the exact error message that you 
are seeing.
Please set the wrapper.debug=true property and then post the portion of 
the log which
includes the attempted load of the library.

As a note.  You should be able to easily build the 64 bit 3.2.0 version 
by downloading
the "prerelease" build and then running "./build64.sh release" from the 
expanded archive's
root directory.   That will produce the 64 bit distribution in a dist 
directory.
I would like to know about any problems there anyway as I am about to 
release the
3.2.1 version.

Cheers,
Leif

Francois ten Have wrote:
>
> Hello,
>
>  
>
> Today we tried to install the latest build (3.1.2) for the wrapper on 
> a hpux 64 (3.2 is not available for 64 bits!). The wrapper reports 
> that the libwrapper.so cannot be found. Renaming the libwrapper.sl to 
> libwrapper.so does NOT solve the problem, although the error changes 
> if we do so)! Pls help! The path (SHLIB) is set correctly and so are 
> the environment variables (through the set. commands in the config file).
>
>  
>
> Regards,
>
> Francois ten Have
>
>  
>

[Wrapper-user] Cannot find library libwrapper.so on HPUX

[Francois t. H. <f.t...@Go...>]

Hello,

=20

Today we tried to install the latest build (3.1.2) for the wrapper on a
hpux 64 (3.2 is not available for 64 bits!). The wrapper reports that
the libwrapper.so cannot be found. Renaming the libwrapper.sl to
libwrapper.so does NOT solve the problem, although the error changes if
we do so)! Pls help! The path (SHLIB) is set correctly and so are the
environment variables (through the set. commands in the config file).

=20

Regards,

Francois ten Have

=20

Gouw Informatie Technologie B.V.

=20

Bezoekadres:

Oude Bosscheweg 9

5301 LA  Zaltbommel

=20

Postadres:

Postbus 98

5300 AB  Zaltbommel

=20

Tel:                  0418 - 511 522

Helpdesk:         0418 - 517 158

Fax:                 0418 - 511 240

Internet:           http://www.gouwit.nl <http://www.gouwit.nl/>=20

E-mail:             f.t...@go... <mailto:f.t...@go...>=20

=20

Disclaimer

Aan de email kunnen geen rechten worden ontleend. GouwIT sluit iedere
aansprakelijkheid uit die voortvloeit uit de elektronische verzending
van dit bericht. De informatie verspreid via dit emailbericht is
uitsluitend bestemd voor de geadresseerde(n) en kan vertrouwelijk
materiaal bevatten. Mocht u dit bericht bij vergissing ontvangen hebben
dan wordt u verzocht de afzender hierover te informeren en het bericht
te verwijderen. Indien u niet de geadresseerde bent noch een
geautoriseerde werknemer die kennis mag nemen van berichten voor de
geadresseerde, mag u dit bericht niet openbaar maken of op enige wijze
verspreiden of vermeningvuldigen.

End of disclaimer

=20

Re: [Wrapper-user] Service dependencies

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

Sylvain,
Please post requests to the user list rather than to me directly.

The shutdown problem is not a wrapper bug. It is a problem with the way the
Windows OS handles the shutdown of services. An OS bug / design flaw.

Unfortunately as you pointed out, it sounds like the communications service
is being shutdown before the wrapper's service. There is no way to
control the
shutdown order.

Is there always a user logged on your system? One option would be to trap
the logout event of the user just before the shutdown. You will always
get that
a couple seconds before the wrapper service gets shot down. It wouldn't be
reliable but it might give you enough time to get the message out before the
communications service gets shutdown.

Ceers,
Leif

Sylvain Bond wrote:
>
> Hi
>
> I have been using your Service wrapper and it works well, but I got a
> question for you.
>
> I am trying to trap windows event and seng a message through a COM
> Port before windows shuts down but it looks like COM Ports become
> closed before my service try to send a message. I did try to put some
> depedencies on my service to a few windows services but I am not sure
> which handles COM Ports. I also saw in your documentation that there
> is a known bug about windows and services dependencies when it comes
> to a shut down.
>
> So basically I cannot make my application send the message before
> windows closes his COM Ports.
>
> Do you have any suggestions or solutions on how I could manage to send
> a message through a COM Port when my service traps a shut down event ?
>
> Thank you
>
> Sylvain
>

Re: [Wrapper-user] Wrapper syslog facility

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

Bruce,
    Wanted to let you know.  I just got this committed for the 3.2.1 
release.
Thanks for the patch.

Cheers,
Leif

Bruce Pennypacker wrote:
> Leif,
>
> Attached are the files.  I used the 3.2.0 sources.  Everything should 
> be very straightforward - it basically mirrors the code for 
> implementing the wrapper.syslog.loglevel property with a new property 
> named wrapper.syslog.facility .  It defaults to LOG_USER but can be 
> set to any of the LOG_LOCAL* values as well.
>
> -Bruce
>
>
> On 6/16/06, *Leif Mortenson* < le...@ta... 
> <mailto:le...@ta...>> wrote:
>
>     Bruce,
>         Sorry for not having gotten it implemented yet.
>         Yes please send it to me.  Let me know what your source files are
>     based on.
>     3.2.0 or the  CVS source.
>
>     Cheers,
>     Leif
>
>
>
>     Bruce Pennypacker wrote:
>     > Hi Leif,
>     >
>     > Our need to set the syslog facility for wrapper logging just became
>     > more important so I took the time to add the functionality into the
>     > source code.  Would you like a copy to merge into the official
>     > version?  It was a fairly small set of changes to logger.c,
>     logger.h ,
>     > and wrapper.c that pretty much mirrors setting the syslog
>     logging level.
>     >
>     > -Bruce
>     >
>
>

Re: [Wrapper-user] Changin user

[David H. <da...@sm...>]

Martin, I'll copy from previous posts...
I hope it helps
Davy Boy Out...

--------------------------------------------------------------------------
Hi JSW developers.

I couldn't find info on your web pages / docs about whether JSW implements
this feature, so I'm guessing it doesn't -- the ability to run a Java
program as a non-root user and open privileged server ports.  For example,
run Tomcat through JSW as user "tomcat" and still open web server port 80.

The Apache Jakarta Commons Daemon jsvc binary that comes with Tomcat does
this, but has fewer other features:

http://jakarta.apache.org/commons/daemon/jsvc.html

JSW doesn't do it as far as I can see, but has lots of nice service features
that Tomcat users could make use of -- but most will want the port 80
capability.

Have you considered adding this feature already?  I searched this mailing
list archive and did not see it discussed.

Cheers.

--
Jason Brittain
--------------------------------------------------------------------------
Jason,
    This is discussed in this feature request.
http://sourceforge.net/tracker/index.php?func=detail&aid=490806&group_id=394
28&atid=425190
    If there is anything that I have overlooked, feel free to add to this
issue.  It is something I would like to make available, I am just not sure
how.

    The problem is that the Tomcat loader binds to the port as root and then
changes to
another user while maintaining a reference to the port.   Once the user 
has been changed,
there is of course no way to go back to being root.

    The Wrapper could do something like this once, but it would not be
possible to recover from failures and launch a new JVM as that would require
becoming root a second time.

    In your case, it sounds like you want to let your live users connect
directly to Tomcat.
I haven't used the newest version, but older versions were not really
designed for this.
Usually, you would have Apache running and then connect to Tomcat using
mod_jk.
This makes it possible for Tomcat to only need high ports, resolving this
problem completely.

Cheers,
Leif
--------------------------------------------------------------------------
On 4/9/06, Leif Mortenson <le...@ta...> wrote:
> Jason,
>     This is discussed in this feature request.
>
http://sourceforge.net/tracker/index.php?func=detail&aid=490806&group_id=394
28&atid=425190
>     If there is anything that I have overlooked, feel free to add to 
> this issue.  It is something I would like to make available, I am just 
> not sure how.

Thanks for the link.  I figured I wouldn't be the first to ask about it.
I'll add to the issue.

>     The problem is that the Tomcat loader binds to the port as root 
> and then changes to
> another user while maintaining a reference to the port.   Once the user
> has been changed,
> there is of course no way to go back to being root.
>
>     The Wrapper could do something like this once, but it would not be 
> possible to recover from failures and launch a new JVM as that would 
> require becoming root a second time.

>From what I can tell, jsvc does not do it this way.  So, you should 
>really have
a look at their implementation.  I believe it's something you could add to
JSW.

>     In your case, it sounds like you want to let your live users 
> connect directly to Tomcat.

I do indeed.

> I haven't used the newest version, but older versions were not really 
> designed for this.

As of at least 3 years ago they were.  This is an area where Tomcat has
improved every year for many years.  At this point, Tomcat is at least as
fast at serving static content as Apache httpd.

> Usually, you would have Apache running and then connect to Tomcat 
> using mod_jk.

That pattern is still popular, but slows down Tomcat.  I no longer suggest
this pattern, mainly because Tomcat stand-alone is plenty capable now, and
setting up two servers (both httpd and Tomcat), plus a connector to connect
them is much more difficult to get working, and to maintain.  And, Tomcat is
now full featured enough that most people don't need Apache httpd anymore
(although most don't realize this).

> This makes it possible for Tomcat to only need high ports, resolving 
> this problem completely.

And creating the problem of lower performance, more difficult maintenance,
more difficult troubleshooting since you have two servers involved in each
request, etc..  Some folks will always set up Tomcat behind httpd, and will
insist that it is the right way, but that's more of a resistance to change
than anything.  Meanwhile, a large percentage of Tomcat users are now
happily using it without Apache httpd. and they want to run it on port 80 as
a non-root user.

Thanks.

--
Jason Brittain
--------------------------------------------------------------------------

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Martin
Novak
Sent: 25 June 2006 17:07
To: wra...@li...
Subject: [Wrapper-user] Changin user

Hello,

I want to start using wrapper in my server as a daemon under unix. The 
problem is that in unix as a normal user I cannot listen to the port 
lower than 1000, and nobody would allow server to run my server under 
root account because of security reasons. So what would I like to do is 
to start as root, bind ports, and then switch to different user.

I would appretiate if somebody can write me if this is supported by wrapper.

thanks,
Martin

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Changin user

[David H. <da...@sm...>]

This has been discussed before, and off the top of my head (I may/will be
wrong) this directly isn't supported in Wrapper. However, take a look at the
way that Apache Tomcat does this, as it has exactly the same issues, but
does work around it.

Sorry for not being more helpful, anyone else?

Davy Boy Out..

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Martin
Novak
Sent: 25 June 2006 17:07
To: wra...@li...
Subject: [Wrapper-user] Changin user

Hello,

I want to start using wrapper in my server as a daemon under unix. The 
problem is that in unix as a normal user I cannot listen to the port 
lower than 1000, and nobody would allow server to run my server under 
root account because of security reasons. So what would I like to do is 
to start as root, bind ports, and then switch to different user.

I would appretiate if somebody can write me if this is supported by wrapper.

thanks,
Martin

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Changin user

[Martin N. <mn...@ma...>]

Hello,

I want to start using wrapper in my server as a daemon under unix. The 
problem is that in unix as a normal user I cannot listen to the port 
lower than 1000, and nobody would allow server to run my server under 
root account because of security reasons. So what would I like to do is 
to start as root, bind ports, and then switch to different user.

I would appretiate if somebody can write me if this is supported by wrapper.

thanks,
Martin

Re: [Wrapper-user] How To Pause A Service

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

Ok.  It probably needs some more testing due to the scale of the 
modifications.  But the
new pause/resume feature has been committed to CVS if you want to try it 
out.

The changes were all as I described.

Cheers,
Leif

Leif Mortenson wrote:
> Joos, Heather,
>     I am working on it as we speak.  It will be in the 3.2.1 release.   
> There are some major
> changes to the state engine that are required so it is turning out to be 
> a little more work than
> I had expected.  I think I have everything worked out though.
>
>     The Wrapper will allow 2 modes of operation.  The first will stop 
> the JVM whenever
> the service is paused.  This stoppage will reset the failed invocation 
> count and allow
> restarts from that state even if restarts have been disabled.  A special 
> case.
>     The second mode will keep the JVM running while paused.  But send an 
> event to
> the JVM so it can handle it.   If the JVM crashes for any reason while 
> in this state,
> it will stay down until the service is continued.  When continued, the 
> exit will be
> counted and handled as a regular restart.  If restarts are disabled or 
> the restart count
> exceeds the configured max, the wrapper will stop at that point.
>
>     In either mode, the service can be stopped while paused.  If the JVM 
> is running
> at the time, it can initiate the stop.
>
>     The WrapperListener class itself can not be modified to handle the 
> pause/continue
> events as the addition of such a method would break things for existing 
> users.  I had
> added a new event/listener hierarchy for 3.2.0 that is much more 
> flexible.  This new
> method allows you to handle this as follows:
>
> WrapperManager.addWrapperEventListener( new WrapperEventListener() {
>     public void fired( WrapperEvent event ) {
>        if ( event instanceof WrapperServiceControlEvent ) {
>           WrapperServiceControlEvent scEvent = 
> (WrapperServiceControlEvent)event;
>           switch ( scEvent.getServiceControlCode() ) {
>           case WrapperManager.SERVICE_CONTROL_CODE_PAUSE:
>              myPauseCallback();
>              break;
>           case WrapperManager.SERVICE_CONTROL_CODE_CONTINUE:
>              myContinueCallback();
>              break;
>           }
>        }
>     }
> }, WrapperEventListener.EVENT_FLAG_SERVICE );
>
> You can write the above code in 3.2.0, but those event values will never 
> be received
> as things are implemented in that version.  I haven't compiled the 
> above, so hopefully
> there are no typos. :-)
>
> Cheers,
> Leif
>   

Re: [Wrapper-user] How To Pause A Service

[Joe R. <joe...@me...>]

Leif,

Thanks for this.  Do you have any idea when 3.2.1 will be released?

Joe=20

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: Thursday, June 22, 2006 4:04 AM
To: wra...@li...
Subject: Re: [Wrapper-user] How To Pause A Service

Joos, Heather,
    I am working on it as we speak.  It will be in the 3.2.1 release.  =20
There are some major
changes to the state engine that are required so it is turning out to be
a little more work than I had expected.  I think I have everything
worked out though.

    The Wrapper will allow 2 modes of operation.  The first will stop
the JVM whenever the service is paused.  This stoppage will reset the
failed invocation count and allow restarts from that state even if
restarts have been disabled.  A special case.
    The second mode will keep the JVM running while paused.  But send an
event to
the JVM so it can handle it.   If the JVM crashes for any reason while=20
in this state,
it will stay down until the service is continued.  When continued, the
exit will be counted and handled as a regular restart.  If restarts are
disabled or the restart count exceeds the configured max, the wrapper
will stop at that point.

    In either mode, the service can be stopped while paused.  If the JVM
is running at the time, it can initiate the stop.

    The WrapperListener class itself can not be modified to handle the
pause/continue events as the addition of such a method would break
things for existing users.  I had added a new event/listener hierarchy
for 3.2.0 that is much more flexible.  This new method allows you to
handle this as follows:

WrapperManager.addWrapperEventListener( new WrapperEventListener() {
    public void fired( WrapperEvent event ) {
       if ( event instanceof WrapperServiceControlEvent ) {
          WrapperServiceControlEvent scEvent =3D
(WrapperServiceControlEvent)event;
          switch ( scEvent.getServiceControlCode() ) {
          case WrapperManager.SERVICE_CONTROL_CODE_PAUSE:
             myPauseCallback();
             break;
          case WrapperManager.SERVICE_CONTROL_CODE_CONTINUE:
             myContinueCallback();
             break;
          }
       }
    }
}, WrapperEventListener.EVENT_FLAG_SERVICE );

You can write the above code in 3.2.0, but those event values will never
be received as things are implemented in that version.  I haven't
compiled the above, so hopefully there are no typos. :-)

Cheers,
Leif

Joost Jens wrote:
> I have asked this before. The service registers itself in such a way=20
> that pausing is disabled. I have given a reason as to why I want it=20
> enabled but they haven't responded on it yet.
> I made a workaround using a remote interface but that is not always=20
> desirable I think.
>
> Joos
>
> Heather Leonard wrote:
>>
>> My appologies if this question is already in the archives (currently=20
>> unavailable).
>>
>> I need to pause my service (Windows).  I wrote an implementation of=20
>> the WrapperListener in order to be able to do this.  When I install=20
>> the service and start it, the pause button is disabled in the=20
>> Services window and the net pause command is not valid for the=20
>> service.  I spent my day yesterday looking through documentation in=20
>> order to find a solution but have been unable to find one so far.
>>
>> Any help you can give will be greatly appreciated.
>>
>> Thanks,
>> Heather
>>


All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications
in the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D107521&bid=3D248729&dat=3D=
121642
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] How To Pause A Service

[Joost J. <jj...@fi...>]

Thanks Leif,

This is a good solution and I for one am happy with it.

Thanks for your response.
With regards,
Joost.

Leif Mortenson wrote:
> Joos, Heather,
>     I am working on it as we speak.  It will be in the 3.2.1 release.   
> There are some major
> changes to the state engine that are required so it is turning out to be 
> a little more work than
> I had expected.  I think I have everything worked out though.
>
>     The Wrapper will allow 2 modes of operation.  The first will stop 
> the JVM whenever
> the service is paused.  This stoppage will reset the failed invocation 
> count and allow
> restarts from that state even if restarts have been disabled.  A special 
> case.
>     The second mode will keep the JVM running while paused.  But send an 
> event to
> the JVM so it can handle it.   If the JVM crashes for any reason while 
> in this state,
> it will stay down until the service is continued.  When continued, the 
> exit will be
> counted and handled as a regular restart.  If restarts are disabled or 
> the restart count
> exceeds the configured max, the wrapper will stop at that point.
>
>     In either mode, the service can be stopped while paused.  If the JVM 
> is running
> at the time, it can initiate the stop.
>
>     The WrapperListener class itself can not be modified to handle the 
> pause/continue
> events as the addition of such a method would break things for existing 
> users.  I had
> added a new event/listener hierarchy for 3.2.0 that is much more 
> flexible.  This new
> method allows you to handle this as follows:
>
> WrapperManager.addWrapperEventListener( new WrapperEventListener() {
>     public void fired( WrapperEvent event ) {
>        if ( event instanceof WrapperServiceControlEvent ) {
>           WrapperServiceControlEvent scEvent = 
> (WrapperServiceControlEvent)event;
>           switch ( scEvent.getServiceControlCode() ) {
>           case WrapperManager.SERVICE_CONTROL_CODE_PAUSE:
>              myPauseCallback();
>              break;
>           case WrapperManager.SERVICE_CONTROL_CODE_CONTINUE:
>              myContinueCallback();
>              break;
>           }
>        }
>     }
> }, WrapperEventListener.EVENT_FLAG_SERVICE );
>
> You can write the above code in 3.2.0, but those event values will never 
> be received
> as things are implemented in that version.  I haven't compiled the 
> above, so hopefully
> there are no typos. :-)
>
> Cheers,
> Leif
>
> Joost Jens wrote:
>   
>> I have asked this before. The service registers itself in such a way 
>> that pausing is disabled. I have given a reason as to why I want it 
>> enabled but they haven't responded on it yet.
>> I made a workaround using a remote interface but that is not always 
>> desirable I think.
>>
>> Joos
>>
>> Heather Leonard wrote:
>>     
>>> My appologies if this question is already in the archives (currently 
>>> unavailable).
>>>
>>> I need to pause my service (Windows).  I wrote an implementation of 
>>> the WrapperListener in order to be able to do this.  When I install 
>>> the service and start it, the pause button is disabled in the 
>>> Services window and the net pause command is not valid for the 
>>> service.  I spent my day yesterday looking through documentation in 
>>> order to find a solution but have been unable to find one so far.
>>>
>>> Any help you can give will be greatly appreciated.
>>>
>>> Thanks,
>>> Heather
>>>
>>>       
>
>
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

Re: [Wrapper-user] How To Pause A Service

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

Joos, Heather,
    I am working on it as we speak.  It will be in the 3.2.1 release.   
There are some major
changes to the state engine that are required so it is turning out to be 
a little more work than
I had expected.  I think I have everything worked out though.

    The Wrapper will allow 2 modes of operation.  The first will stop 
the JVM whenever
the service is paused.  This stoppage will reset the failed invocation 
count and allow
restarts from that state even if restarts have been disabled.  A special 
case.
    The second mode will keep the JVM running while paused.  But send an 
event to
the JVM so it can handle it.   If the JVM crashes for any reason while 
in this state,
it will stay down until the service is continued.  When continued, the 
exit will be
counted and handled as a regular restart.  If restarts are disabled or 
the restart count
exceeds the configured max, the wrapper will stop at that point.

    In either mode, the service can be stopped while paused.  If the JVM 
is running
at the time, it can initiate the stop.

    The WrapperListener class itself can not be modified to handle the 
pause/continue
events as the addition of such a method would break things for existing 
users.  I had
added a new event/listener hierarchy for 3.2.0 that is much more 
flexible.  This new
method allows you to handle this as follows:

WrapperManager.addWrapperEventListener( new WrapperEventListener() {
    public void fired( WrapperEvent event ) {
       if ( event instanceof WrapperServiceControlEvent ) {
          WrapperServiceControlEvent scEvent = 
(WrapperServiceControlEvent)event;
          switch ( scEvent.getServiceControlCode() ) {
          case WrapperManager.SERVICE_CONTROL_CODE_PAUSE:
             myPauseCallback();
             break;
          case WrapperManager.SERVICE_CONTROL_CODE_CONTINUE:
             myContinueCallback();
             break;
          }
       }
    }
}, WrapperEventListener.EVENT_FLAG_SERVICE );

You can write the above code in 3.2.0, but those event values will never 
be received
as things are implemented in that version.  I haven't compiled the 
above, so hopefully
there are no typos. :-)

Cheers,
Leif

Joost Jens wrote:
> I have asked this before. The service registers itself in such a way 
> that pausing is disabled. I have given a reason as to why I want it 
> enabled but they haven't responded on it yet.
> I made a workaround using a remote interface but that is not always 
> desirable I think.
>
> Joos
>
> Heather Leonard wrote:
>>
>> My appologies if this question is already in the archives (currently 
>> unavailable).
>>
>> I need to pause my service (Windows).  I wrote an implementation of 
>> the WrapperListener in order to be able to do this.  When I install 
>> the service and start it, the pause button is disabled in the 
>> Services window and the net pause command is not valid for the 
>> service.  I spent my day yesterday looking through documentation in 
>> order to find a solution but have been unable to find one so far.
>>
>> Any help you can give will be greatly appreciated.
>>
>> Thanks,
>> Heather
>>

Re: [Wrapper-user] How To Pause A Service

[Joost J. <jj...@fi...>]

I have asked this before. The service registers itself in such a way 
that pausing is disabled. I have given a reason as to why I want it 
enabled but they haven't responded on it yet.
I made a workaround using a remote interface but that is not always 
desirable I think.

Joos

Heather Leonard wrote:
>
> My appologies if this question is already in the archives (currently 
> unavailable).
>
> I need to pause my service (Windows).  I wrote an implementation of 
> the WrapperListener in order to be able to do this.  When I install 
> the service and start it, the pause button is disabled in the Services 
> window and the net pause command is not valid for the service.  I 
> spent my day yesterday looking through documentation in order to find 
> a solution but have been unable to find one so far.
>
> Any help you can give will be greatly appreciated.
>
> Thanks,
> Heather
>
> ------------------------------------------------------------------------
>
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> ------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>   

[Wrapper-user] How To Pause A Service

[Heather L. <hea...@me...>]

My appologies if this question is already in the archives (currently
unavailable).

I need to pause my service (Windows).  I wrote an implementation of the
WrapperListener in order to be able to do this.  When I install the
service and start it, the pause button is disabled in the Services
window and the net pause command is not valid for the service.  I spent
my day yesterday looking through documentation in order to find a
solution but have been unable to find one so far.

Any help you can give will be greatly appreciated.

Thanks,
Heather

Re: [Wrapper-user] WrapperStartStopApp stopping service prematurely?

[<TEI...@te...>]

Leif, I think that's exactly what was happening. I removed the System.exit =
call and then everything started to work as expected. The CTRL +=20
C feature is interesting, will take a look into that.

Many thanks to both David and Leif
teix


----Mensaje original----
De: le...@ta...
Recibido: 19/06/2006 16:36
Para: <TEI...@te...>, <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

Prueba,
    It looks like you may have already figured this out.  But here is=20
what is
happening.   First the end of your log file and then I'll explain it to you=
.

INFO   | jvm 1    | 2006/06/19 10:17:57 | [Manager (console)] Finished.
INFO   | jvm 1    | 2006/06/19 10:17:57 | 34 mon 19/06/2006 10:17:57=20
[Manager] Finished.
INFO   | jvm 1    | 2006/06/19 10:17:57 | Wrapper Manager: ShutdownHook=20
started
INFO   | jvm 1    | 2006/06/19 10:17:57 | WrapperManager.stop(0) called=20
by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2006/06/19 10:17:57 | Thread, Wrapper-Shutdown-Hook,=20
waiting for the JVM to exit.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Thread, Wrapper-Shutdown-Hook,=20
continuing after 5 seconds.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Send a packet STOPPED : 0
DEBUG  | wrapperp | 2006/06/19 10:18:02 | read a packet STOPPED : 0
DEBUG  | wrapper  | 2006/06/19 10:18:02 | JVM signalled that it was stopped=
.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Wrapper Manager: ShutdownHook=20
complete
DEBUG  | wrapper  | 2006/06/19 10:18:02 | JVM process exited with a code=20
of 0, leaving the wrapper exit code set to 0.

    You see in the first few lines that after your Manager has sent the
shutdown command, and completes, the Wrapper's shutdown hook is immediately
being activated.  This is most likely because your Manager class is calling
System.exit.  In this mode, the original shutdown was triggered by the=20
Wrapper
and not by the JVM shutting down so the JVM has not yet started the=20
registered
shutdown hooks.  It will do so now.

    The Wrapper's shutdown hook is designed to block until the
WrapperListener.stop method has completed.  When it calls System.exit, this
will never happen.   To avoid a deadlock, the Wrapper is able to detect tha=
t
state and will only deadlock for a maximum of 5 seconds.

    The JVM itself will exit as soon as all of its shutdown hooks have been
completed.  It sounds like you are looping over your worker threads and
stopping each of them within a normal non daemon thread.   The problem
is that none of that shutdown work is happening within the call stack of
a shutdown hook so the JVM is not going to wait for it all to complete
before shutting down.

    You can solve this in one of two ways.
1) Remove the System.exit from your Manager shutdown process.
2) Add a shutdown hook to Server which loops until all of your worker
threads are stopped.  That will keep the JVM up until it is safe to exit.
That would also make your Server application shutdown reliably when
it is running stand alone without the Wrapper and is killed with a CTRL-C.

    I added the following note to the debug output for the next release.
The message will show up in the logs if the Wrapper's shutdown process
is initiated from within the WrapperListener.stop method by calling
System.exit.

---
System.exit appears to have been called from within the
  WrapperListener.stop() method.  If possible the application
  should be modified to avoid this behavior.
  To avoid a deadlock, this thread will only wait 5 seconds
  for the application to shutdown.  This may result in the
  application failing to shutdown completely before the JVM
  exists.  Removing the offending System.exit call will
  resolve this.
---

    I also added a note about this to the documentation for the
WrapperStartStopApp.

Cheers,
Leif

TEI...@te... wrote:
> I think I found the problem. I was finishing both Server and Manager with=
 System.exit(0) which caused the ShutdownHook to be called.=20
This=20
> happens before WrapperStartStopApp  starts waiting for all non-daemon thr=
eads to terminate. Perhaps there's a configuration property=20
> regarding this ...
>  =20



_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.

Re: [Wrapper-user] WrapperStartStopApp stopping service prematurely?

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

Prueba,
    It looks like you may have already figured this out.  But here is 
what is
happening.   First the end of your log file and then I'll explain it to you.

INFO   | jvm 1    | 2006/06/19 10:17:57 | [Manager (console)] Finished.
INFO   | jvm 1    | 2006/06/19 10:17:57 | 34 mon 19/06/2006 10:17:57 
[Manager] Finished.
INFO   | jvm 1    | 2006/06/19 10:17:57 | Wrapper Manager: ShutdownHook 
started
INFO   | jvm 1    | 2006/06/19 10:17:57 | WrapperManager.stop(0) called 
by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2006/06/19 10:17:57 | Thread, Wrapper-Shutdown-Hook, 
waiting for the JVM to exit.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Thread, Wrapper-Shutdown-Hook, 
continuing after 5 seconds.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Send a packet STOPPED : 0
DEBUG  | wrapperp | 2006/06/19 10:18:02 | read a packet STOPPED : 0
DEBUG  | wrapper  | 2006/06/19 10:18:02 | JVM signalled that it was stopped.
INFO   | jvm 1    | 2006/06/19 10:18:02 | Wrapper Manager: ShutdownHook 
complete
DEBUG  | wrapper  | 2006/06/19 10:18:02 | JVM process exited with a code 
of 0, leaving the wrapper exit code set to 0.

    You see in the first few lines that after your Manager has sent the
shutdown command, and completes, the Wrapper's shutdown hook is immediately
being activated.  This is most likely because your Manager class is calling
System.exit.  In this mode, the original shutdown was triggered by the 
Wrapper
and not by the JVM shutting down so the JVM has not yet started the 
registered
shutdown hooks.  It will do so now.

    The Wrapper's shutdown hook is designed to block until the
WrapperListener.stop method has completed.  When it calls System.exit, this
will never happen.   To avoid a deadlock, the Wrapper is able to detect that
state and will only deadlock for a maximum of 5 seconds.

    The JVM itself will exit as soon as all of its shutdown hooks have been
completed.  It sounds like you are looping over your worker threads and
stopping each of them within a normal non daemon thread.   The problem
is that none of that shutdown work is happening within the call stack of
a shutdown hook so the JVM is not going to wait for it all to complete
before shutting down.

    You can solve this in one of two ways.
1) Remove the System.exit from your Manager shutdown process.
2) Add a shutdown hook to Server which loops until all of your worker
threads are stopped.  That will keep the JVM up until it is safe to exit.
That would also make your Server application shutdown reliably when
it is running stand alone without the Wrapper and is killed with a CTRL-C.

    I added the following note to the debug output for the next release.
The message will show up in the logs if the Wrapper's shutdown process
is initiated from within the WrapperListener.stop method by calling
System.exit.

---
System.exit appears to have been called from within the
  WrapperListener.stop() method.  If possible the application
  should be modified to avoid this behavior.
  To avoid a deadlock, this thread will only wait 5 seconds
  for the application to shutdown.  This may result in the
  application failing to shutdown completely before the JVM
  exists.  Removing the offending System.exit call will
  resolve this.
---

    I also added a note about this to the documentation for the
WrapperStartStopApp.

Cheers,
Leif

TEI...@te... wrote:
> I think I found the problem. I was finishing both Server and Manager with System.exit(0) which caused the ShutdownHook to be called. This 
> happens before WrapperStartStopApp  starts waiting for all non-daemon threads to terminate. Perhaps there's a configuration property 
> regarding this ...
>   

Re: [Wrapper-user] wrapper.on_exit seems not to work in 3.2.0

[Richard E. <rem...@ed...>]

Leif,

Do you have an ETA for release 3.2.1 - just trying to
coordinate with our release schedule.

Richard


Leif Mortenson wrote:
> Andreas,
>     Sorry.  That is a known bug in 3.2.0 that has been fixed in CVS.  It 
> will be in the 3.2.1
> release.  I need to hurry up and get that out the door.
> 
>     Here is the current list of changes for the 3.2.1 release:
> 
> Cheers,
> Leif
> 
> Java Service Wrapper Revision History.
> --------------------------------------
> 3.2.1
> * Fix a problem with the solaris-sparc-64 makefile.
> * Add a solaris-x86-64 makefile.
> * Merge in a patch by Hugo Weber to make it possible to configure the 
> Wrapper
>   to pull the JRE from the system registry on windows.
> * Fix a batch file bug added in 3.2.0 where the scripts would not function
>   correctly if the full path to the batch file contained spaces.
>   Bug #1450601.
> * Modify the message shown when a native library fails to load so the
>   exception message text is now shown in the log without having to enable
>   debug log output.
> * Modify the UNIX shell script to be more informative if the script is 
> unable
>   to locate a wrapper binary due to a executable bit permission problem.
> * Fix a minor permission problem with the build for the delta-pack.
> * Commit a patch by Juergen Hermann to make the error shown when realpath
>   fails clearer.
> * Add the ability to use a default wrapper.conf file that is in the same
>   directory as the wrapper binary.  The file will be named based on the
>   name of the wrapper binary.
> * Synchronize the command line so that both the Windows and UNIX versions
>   are now the same.  The old command line syntaxes are now supported
>   everywhere so there will be no compatibility problems.
> * It is no longer possible to specify arguments using the '/c' syntax.
>   This was undocumented so hopefully it is not being used.  The documented
>   '-c' syntax must now be used.  The change was necessary to synchronize
>   the command line between UNIX and windows platforms.
> * The 32-bit HP-UX 3.2.0 build was generating a libwrapper.so file rather
>   than libwrapper.sl.
> * Make the WrapperManager.setConsoleTitle, getWrapperPID, and getJavaPID
>   methods available through JMX.
> * Fix a state engine problem introduced in 3.2.0 which was causing the
>   wrapper.on_exit.<n> properties to be ignored in most cases.
> * Fix a potential problem that could have caused crashes when debug logging
>   was enabled.
> * Fix a problem where signals were not being handled correctly on some UNIX
>   platforms, including AIX.  This was making it impossible to shutdown the
>   wrapper cleanly with the TERM signal.  Bug #1477619.
> * Add new default environment variables which can be referenced in a
>   configuration file to configure platform specific directories and file
>   names.  WRAPPER_OS, WRAPPER_ARCH, and WRAPPER_BITS.
> * Add a -v argument to make it possible to request the version from a 
> wrapper
>   binary.
> * Add support for registering the WrapperManager MBean with the
>   PlatformMBeanServer when run on a 1.5+ JVM.  See the JMX section in the
>   documentation for details.
> * Rework the way timeout properties are handled.  Values of 0 now actually
>   disable the timeouts rather than setting them to a large value.  To avoid
>   overflow problems when converting to internal timer ticks, timeouts 
> are now
>   restricted to a maximum of 20 days, or 1728000 seconds.  Change 
> affects the
>   wrapper.cpu.timeout, wrapper.startup.timeout, wrapper.ping.timeout,
>   wrapper.shutdown.timeout, and wrapper.jvm_exit.timeout properties.  For
>   values less than 20 days, there should be no change in functionality.
> * Add support for debuggers.  The Wrapper will now show a warning on startup
>   and then again the first time a timeout occurs.  But all timeouts will be
>   ignored.  This is to avoid problems with the Wrapper restarting a 
> suspended
>   JVM in the middle of a debugging session.  The wrapper enters this mode if
>   the wrapper.java.command ends with the string "jdb" or "jdb.exe", or the
>   "-Xdebug" parameter is passed to the JVM.
> * Add 'athlon' to the list of supported architectures.
> * Fix a problem where the environment variables loaded when a service was
>   started were always the system environment even if the service was running
>   as a specific account.  The environment of a specific account will now be
>   loaded on top of the system environment if the USERNAME environment
>   variable is set by the system.  Bug #1491138.
> 
> 
> 
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


-- 
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

Re: [Wrapper-user] FW: can't post mail to wrapper-user list

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

Ewa,
Not sure about your send mail problems. This one seemed to work. The SF 
server may
have been having problems.

I had not seen that particular site. It shows you how to integrate with 
a particular example
but doesn't really describe what is going on. I would suggest starting 
with the Wrapper's
documentation :-) Try this page:
http://wrapper.tanukisoftware.org/doc/english/integrate.html

In your case, look at integration method #1. As that is what you have 
been using up to
this point.

My guess is that your program is being started but is completing because 
all of its threads
have stopped. If so, that is the correct behavior. I would need to see 
the debug output
in order to tell you for sure however.

After reading the docs above, if you are still having problems, add the 
wrapper.debug=true
property to your conf file. Starting with a clean wrapper.log, try 
running it again and then
reply with the resulting log file. I'll be able to say exactly what is 
going on then.

Cheers,
Leif


> *To get myself started with Java Service Wrapper I have been following 
> “Running Java Applications as a Windows Service – By Rick Proctor” 
> (http://bdn1.borland.com/article/0,1410,32068,00.html) which got me 
> quite far, but not far enough…***
>
> *I managed to create a Windows service called MultipleSocketserver but 
> can’t start it: if I try to start it from Windows XP Services window 
> (in Control Panel / Administrative tools), I get error message** 
> (could not start the ….*
>
> *…on local computer. Error 1: Incorrect function)*
>
> * *
>
> If I try to do this from the console (running the Start…. bat file), I 
> get the following:
>
> C:\wrapper-windows-x86-32-3.2.0\bin>StartTestWrapper-NT
>
> wrapper | Starting the MultipleSocketServer service...
>
> wrapper | Stopping...
>
> wrapper | The MultipleSocketServer service was launched, but failed to 
> start
>
> I have wrapper-windows-x86-32-3.2.0 on Win XP computer
>
> Could someone help, please?
>
> Thanks
>
> * *
>
> Ewa
>

Re: [Wrapper-user] WrapperStartStopApp stopping service prematurely?

[<TEI...@te...>]

I think I found the problem. I was finishing both Server and Manager with S=
ystem.exit(0) which caused the ShutdownHook to be called. This=20
happens before WrapperStartStopApp  starts waiting for all non-daemon threa=
ds to terminate. Perhaps there's a configuration property=20
regarding this ...

----Mensaje original----
De: TEI...@te...
Recibido: 19/06/2006 13:55
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?


  Hi, again!

  Looking into WrapperStartStopApp I've noticed the 'stop' method is suppos=
ed to wait for all non-daemon threads to complete depending on=20
a boolean attribute called m_stopWait, which corresponds with the first par=
am passed to WrapperStartStopApp right after the shutdown=20
class=20
param.

            if ( m_stopWait )
            {
                int threadCnt;
                while( ( threadCnt =3D WrapperManager.getNonDaemonThreadCou=
nt() ) > 1 )
                {
                    if ( WrapperManager.isDebugEnabled() )
                    {
                        System.out.println( "WrapperStartStopApp: stopping.=
  Waiting for "
                            + (threadCnt - 1) + " threads to complete." );
                    }
                    try
                    {
                        Thread.sleep( 1000 );
                    }
                    catch ( InterruptedException e )
                    {
                    }
                }
            }

  The logfile I sent in the previous mail was produced by Wrapper logging i=
n DEBUG level, so this sentence
    - System.out.println( "WrapperStartStopApp: stopping.  Waiting for "+ (=
threadCnt - 1) + " threads to complete." );

should have been executed, which wasn't the case.
  I think I've configured WrapperStartStopApp properly so, perhaps, the ori=
gin of the problem might be when setting m_stopWait, or into=20
WrapperManager.getNonDaemonThreadCount()

  What do you think?
 =20

----Mensaje original----
De: TEI...@te...
Recibido: 19/06/2006 11:10
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

Hi!

I tryed configuring the following variables with no results. The logging ou=
tput is truncated right after the manager has finished.
wrapper.shutdown.timeout=3D0
wrapper.jvm_exit.timeout=3D0

I attached a logfile. I can't get any clues from it, except that the wrappe=
r seems to do its job.
My question is, when does WrapperStartStopApp stop the service?

Kind regards



----Mensaje original----
De: da...@sm...
Recibido: 17/06/2006 6:09
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

(sorry for the personal post - stupid webmail client)

You mention that your servers logging output is truncated. I guess =20
this means that your server was forceably closed by the Wrapper. This =20
normally happens when  the wrapper has been notified of the stopping, =20
but the actual app has not stopped within the expected time period. =20
Check out the .conf property wrapper.shutdown.timeout or possibly =20
consider calling WrapperManager.signalStopping(...) every few seconds.

To further get an understanding on what is going on under the bonnet, set t=
he
wrapper.debug to TRUE and inspect the results wrapper log file. This =20
will tell you exactly why the wrapper has shut down your application, =20
and will give you a better idea on how to solve it.

You could post it as well for us to see if we could help.

Cheers,

Davy Boy Out...

Quoting "TEI...@te..." <TEI...@te...>:

>
>   Thanks, David!
>
>   I don't think that's the case. I'll try to draw it with more  =20
> detail. I developed my application without Wrapper in mind in the  =20
> first
> instance. Lets call the first app "Server" and "Manager" would be  =20
> the second one.
>   Server is an event driven application, there's an event queue from =20
>  where it pops events. When a "shutdown" event is read, Server stops
> reading events, asks avery of its working threads (non daemon  =20
> threads) to stop (they will close connections) and waits until all  =20
> of them
> have stopped (this doesn't take more than 5s).
>   Server logs almost every meaningful event/action it takes.
>
>   The whole system, running alone, outside the wrapper, would log  =20
> something like this.
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications (more threads  =20
> and connections)
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>   7.  Server: Ask avery single thread to stop (threads will close  =20
> connections as soon as possible).
>   8.  Server: Wait for every single thread to stop.
>   9.  Server: Finish
>
>   The whole system, running into the wrapper
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications - more threads =20
>  and connections
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>       At this moment Manager is already dead and WrapperStartStopApp =20
>  seems has decided to kill Server too, cause logging output was
> truncated
>
>   I added a Thread.sleep(5000) to make sure Manager's death was  =20
> after Server's, the resulting logging output was the same as if the  =20
> system
> were running alone, that is, not into WrapperStartStopApp.
>
>   Further comments, please!
>
>
>
> Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, =20
> r=C3=A1pido, fiable.
>
>
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>




_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.



_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.

Re: [Wrapper-user] WrapperStartStopApp stopping service prematurely?

[<TEI...@te...>]

  Hi, again!

  Looking into WrapperStartStopApp I've noticed the 'stop' method is suppos=
ed to wait for all non-daemon threads to complete depending on=20
a boolean attribute called m_stopWait, which corresponds with the first par=
am passed to WrapperStartStopApp right after the shutdown class=20
param.

            if ( m_stopWait )
            {
                int threadCnt;
                while( ( threadCnt =3D WrapperManager.getNonDaemonThreadCou=
nt() ) > 1 )
                {
                    if ( WrapperManager.isDebugEnabled() )
                    {
                        System.out.println( "WrapperStartStopApp: stopping.=
  Waiting for "
                            + (threadCnt - 1) + " threads to complete." );
                    }
                    try
                    {
                        Thread.sleep( 1000 );
                    }
                    catch ( InterruptedException e )
                    {
                    }
                }
            }

  The logfile I sent in the previous mail was produced by Wrapper logging i=
n DEBUG level, so this sentence
    - System.out.println( "WrapperStartStopApp: stopping.  Waiting for "+ (=
threadCnt - 1) + " threads to complete." );

should have been executed, which wasn't the case.
  I think I've configured WrapperStartStopApp properly so, perhaps, the ori=
gin of the problem might be when setting m_stopWait, or into=20
WrapperManager.getNonDaemonThreadCount()

  What do you think?
 =20

----Mensaje original----
De: TEI...@te...
Recibido: 19/06/2006 11:10
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

Hi!

I tryed configuring the following variables with no results. The logging ou=
tput is truncated right after the manager has finished.
wrapper.shutdown.timeout=3D0
wrapper.jvm_exit.timeout=3D0

I attached a logfile. I can't get any clues from it, except that the wrappe=
r seems to do its job.
My question is, when does WrapperStartStopApp stop the service?

Kind regards



----Mensaje original----
De: da...@sm...
Recibido: 17/06/2006 6:09
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

(sorry for the personal post - stupid webmail client)

You mention that your servers logging output is truncated. I guess =20
this means that your server was forceably closed by the Wrapper. This =20
normally happens when  the wrapper has been notified of the stopping, =20
but the actual app has not stopped within the expected time period. =20
Check out the .conf property wrapper.shutdown.timeout or possibly =20
consider calling WrapperManager.signalStopping(...) every few seconds.

To further get an understanding on what is going on under the bonnet, set t=
he
wrapper.debug to TRUE and inspect the results wrapper log file. This =20
will tell you exactly why the wrapper has shut down your application, =20
and will give you a better idea on how to solve it.

You could post it as well for us to see if we could help.

Cheers,

Davy Boy Out...

Quoting "TEI...@te..." <TEI...@te...>:

>
>   Thanks, David!
>
>   I don't think that's the case. I'll try to draw it with more  =20
> detail. I developed my application without Wrapper in mind in the  =20
> first
> instance. Lets call the first app "Server" and "Manager" would be  =20
> the second one.
>   Server is an event driven application, there's an event queue from =20
>  where it pops events. When a "shutdown" event is read, Server stops
> reading events, asks avery of its working threads (non daemon  =20
> threads) to stop (they will close connections) and waits until all  =20
> of them
> have stopped (this doesn't take more than 5s).
>   Server logs almost every meaningful event/action it takes.
>
>   The whole system, running alone, outside the wrapper, would log  =20
> something like this.
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications (more threads  =20
> and connections)
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>   7.  Server: Ask avery single thread to stop (threads will close  =20
> connections as soon as possible).
>   8.  Server: Wait for every single thread to stop.
>   9.  Server: Finish
>
>   The whole system, running into the wrapper
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications - more threads =20
>  and connections
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>       At this moment Manager is already dead and WrapperStartStopApp =20
>  seems has decided to kill Server too, cause logging output was
> truncated
>
>   I added a Thread.sleep(5000) to make sure Manager's death was  =20
> after Server's, the resulting logging output was the same as if the  =20
> system
> were running alone, that is, not into WrapperStartStopApp.
>
>   Further comments, please!
>
>
>
> Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, =20
> r=C3=A1pido, fiable.
>
>
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>




_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.

[Wrapper-user] FW: can't post mail to wrapper-user list

[Ewa G. <eg...@ci...>]

________________________________

From: Ewa Gubb=20
Sent: 19 June 2006 11:26
To: ''wra...@li...'
Subject: FW: can't post mail to wrapper-user list

=20

=20

=20

________________________________

From: Ewa Gubb=20
Sent: 15 June 2006 16:07
To: 'wra...@li...'
Cc: Ewa Gubb
Subject: can't post mail to wrapper-user list

=20

I am new to this, so might be doing something silly: I tried to send =
message to wrapper-user list, but it seems to be bouncing back with:=20

=20

wra...@li... on 15/06/2006 16:00

            There was a SMTP communication problem with the recipient's =
email server.  Please contact your system administrator.

            <correo.cicbiogune.com #5.5.0 smtp;550-Postmaster =
verification failed while checking <eg...@ci...>>

=20

The message itself is included below (minus the picture, which is not =
really needed), although I don't think the message

as such is causing the problem....

=20

Thanks

=20

To get myself started with Java Service Wrapper I have been following =
"Running Java Applications as a Windows Service - By Rick Proctor" =
(http://bdn1.borland.com/article/0,1410,32068,00.html) which got me =
quite far, but not far enough...

I managed to create a Windows service called MultipleSocketserver but =
can't start it: if I try to start it from Windows XP  Services window =
(in Control Panel / Administrative tools), I get error message (could =
not start the ....

...on local computer. Error 1: Incorrect function)

=20

If I try to do this from the console  (running the Start....  bat file), =
 I get the following:

=20

C:\wrapper-windows-x86-32-3.2.0\bin>StartTestWrapper-NT

wrapper  | Starting the MultipleSocketServer service...

wrapper  | Stopping...

wrapper  | The MultipleSocketServer service was launched, but failed to =
start

=20

I have wrapper-windows-x86-32-3.2.0 on Win XP computer

=20

Could someone help, please?

=20

Thanks

=20

=20

=20

=20

        =20

                 Ewa

 =20

=20

Ewa Gubb

Bioinform=E1tica

CIC-Biogune

Parque Tecnol=F3gico de Vizcaya

Edificio 801A, 1pl.

48160-Derio

Spain

=20





Este correo electr=F3nico se ha enviado desde CIC bioGUNE. Su contenido, =
y el de cualquier fichero que le acompa=F1e, son confidenciales y de uso =
exclusivo de la persona f=EDsica o jur=EDdica a la que va destinado. =
Est=E1 estrictamente prohibida, y puede ser ilegal, la copia o =
difusi=F3n no autorizada de este correo, o de sus documentos adjuntos, o =
revelar cualquier informaci=F3n que pudieran contener. Si ha recibido =
este correo electr=F3nico por error, por favor notif=EDquelo al =
remitente o contacte con el tel=E9fono + 34 944 06 13 00 y b=F3rrelo de =
su sistema inform=E1tico.

=20

This e-mail is from CIC bioGUNE. The e-mail and any files transmitted =
with it are confidential and intended solely for the use of the =
individual or entity to whom they are addressed. Any unauthorised =
dissemination or copying of this e-mail or its attachments, and any use =
or disclosure of any information contained in them, is strictly =
prohibited and may be illegal. If you have received this e-mail in =
error, please notify or telephone + 34 944 06 13 00 and delete it from =
your system.

Re: [Wrapper-user] WrapperStartStopApp stopping service prematurely?

[<TEI...@te...>]

Hi!

I tryed configuring the following variables with no results. The logging ou=
tput is truncated right after the manager has finished.
wrapper.shutdown.timeout=3D0
wrapper.jvm_exit.timeout=3D0

I attached a logfile. I can't get any clues from it, except that the wrappe=
r seems to do its job.
My question is, when does WrapperStartStopApp stop the service?

Kind regards



----Mensaje original----
De: da...@sm...
Recibido: 17/06/2006 6:09
Para: <wra...@li...>
Asunto: Re: [Wrapper-user] WrapperStartStopApp stopping service=09premature=
ly?

(sorry for the personal post - stupid webmail client)

You mention that your servers logging output is truncated. I guess =20
this means that your server was forceably closed by the Wrapper. This =20
normally happens when  the wrapper has been notified of the stopping, =20
but the actual app has not stopped within the expected time period. =20
Check out the .conf property wrapper.shutdown.timeout or possibly =20
consider calling WrapperManager.signalStopping(...) every few seconds.

To further get an understanding on what is going on under the bonnet, set t=
he
wrapper.debug to TRUE and inspect the results wrapper log file. This =20
will tell you exactly why the wrapper has shut down your application, =20
and will give you a better idea on how to solve it.

You could post it as well for us to see if we could help.

Cheers,

Davy Boy Out...

Quoting "TEI...@te..." <TEI...@te...>:

>
>   Thanks, David!
>
>   I don't think that's the case. I'll try to draw it with more  =20
> detail. I developed my application without Wrapper in mind in the  =20
> first
> instance. Lets call the first app "Server" and "Manager" would be  =20
> the second one.
>   Server is an event driven application, there's an event queue from =20
>  where it pops events. When a "shutdown" event is read, Server stops
> reading events, asks avery of its working threads (non daemon  =20
> threads) to stop (they will close connections) and waits until all  =20
> of them
> have stopped (this doesn't take more than 5s).
>   Server logs almost every meaningful event/action it takes.
>
>   The whole system, running alone, outside the wrapper, would log  =20
> something like this.
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications (more threads  =20
> and connections)
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>   7.  Server: Ask avery single thread to stop (threads will close  =20
> connections as soon as possible).
>   8.  Server: Wait for every single thread to stop.
>   9.  Server: Finish
>
>   The whole system, running into the wrapper
>
>   1.  Server: Start
>   2.  Server: Launching a "connector" thread to handle incoming connectio=
ns.
>   3.  Server: Trying to connect to other applications - more threads =20
>  and connections
>       ...
>   4.  Server: Receiving an incoming connection -> a worker thread is =20
>  launched in order to handle it.
>       ...
>        At this moment a number of (non daemon) threads are running.
>       ...
>   5.  Manager: Connected to the server, sent a shutdown command,  =20
> closed connection and finish.
>   6.  Server: ( ... keeps doing its thing ...) A "shutdown"  =20
> command/event was read.
>       At this moment Manager is already dead and WrapperStartStopApp =20
>  seems has decided to kill Server too, cause logging output was
> truncated
>
>   I added a Thread.sleep(5000) to make sure Manager's death was  =20
> after Server's, the resulting logging output was the same as if the  =20
> system
> were running alone, that is, not into WrapperStartStopApp.
>
>   Further comments, please!
>
>
>
> Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, =20
> r=C3=A1pido, fiable.
>
>
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>




_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user





Prueba el correo Terra ( http://www.terra.es/correo ); Seguro, r=C3=A1pido,=
 fiable.

[Wrapper-user] wrapper.on_exit seems not to work in 3.2.0

[<And...@t-...>]

Re-sent after subscribing to list ... 

-----Original Message-----

Hi,

I switched from 3.1.2 to 3.2.0 recently and my processes do not restart any more.
I wrote a little test class to nail down the problem, and it seems to be the wrapper.
The test class only gets restarted when setting "disable_shutdown_hook" to TRUE, but then I cannot control the restart bevahior using System.exit(n)

Test code:
==========
public class Wrappertest
{
  public static void main( String[] args)
  {
    try
    {
      long sleepTime = Long.parseLong(args[0]);
      int exitCode = Integer.parseInt(args[1]);
      System.out.println("WRAPPERTEST: #############################################");
      System.out.println("WRAPPERTEST: Sleeping for "+sleepTime+"ms");
      Thread.sleep(sleepTime);
      System.out.println("WRAPPERTEST: Exiting with code "+exitCode);
      System.exit(exitCode);
    }
    catch( Exception e)
    {
      e.printStackTrace();
      System.err.println();
      System.err.println("Usage: java Wrappertest <sleeptime in ms> <exit code>");
      System.err.println();
    }
  }
}

Wrapper configuration:
======================
#include %AODB_HOME%/run/etc/set_classpath.cfg
wrapper.java.command=java
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=Wrappertest
wrapper.app.parameter.2=10000
# exit code 1 should initiate restart
wrapper.app.parameter.3=1
wrapper.on_exit.-1=RESTART
wrapper.on_exit.1=RESTART
wrapper.on_exit.255=RESTART
#wrapper.disable_shutdown_hook=TRUE
wrapper.console.format=PM
wrapper.console.loglevel=NONE
wrapper.logfile=%AODB_HOME%/run/log/wrappertest.log
wrapper.logfile.format=LPTM
wrapper.logfile.loglevel=DEBUG
wrapper.logfile.maxsize=1m
wrapper.logfile.maxfiles=10
wrapper.syslog.loglevel=NONE
wrapper.console.title=WRAPPERTEST
wrapper.ntservice.name=WRAPPERTEST
wrapper.ntservice.displayname=WRAPPERTEST
wrapper.ntservice.description=WRAPPERTEST
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.java.pidfile=%AODB_HOME%/run/var/wrappertest.pid
wrapper.lockfile=%AODB_HOME%/run/var/wrappertest.lck
wrapper.anchorfile=%AODB_HOME%/run/var/wrappertest.anc
wrapper.debug=TRUE

Wrappertest.log
===============
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Service command: D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin\wrapper.exe -s D:\Projects\CGN\Farms\aodb_install\run\config\Wrappertest.cfg set.WRAPPER_DIR=D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin set.SYSLIB_DIR=../common/syslib set.AODB_HOME=D:\Projects\CGN\Farms\aodb_install wrapper.working.dir=D:\Projects\CGN\Farms\aodb_install\run
ERROR  | wrapper  | 2006/06/19 09:07:54 | CreateService failed - Der angegebene Dienst ist bereits vorhanden. (0x431) DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
STATUS | wrapper  | 2006/06/19 09:07:54 | Starting the WRAPPERTEST service...
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
STATUS | wrapper  | 2006/06/19 09:07:54 | --> Wrapper Started as Service DEBUG  | wrapper  | 2006/06/19 09:07:54 | Using tick timer.
DEBUG  | wrapperp | 2006/06/19 09:07:54 | server listening on port 32000.
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.28, does not exist: ../common/syslib/extlib/jmx/jmxremote_optional.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.30, does not exist: ../common/syslib/extlib/jmx/jmxtools.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.31, does not exist: ../common/syslib/extlib/jmx/rmissl.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.83, does not exist: D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrappertest.jar
STATUS | wrapper  | 2006/06/19 09:07:54 | Launching a JVM...
DEBUG  | wrapper  | 2006/06/19 09:07:54 | command: "d:\Program Files\j2sdk1.4.2\bin\java.exe" -Djava.library.path="D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib;d:\Program Files\j2sdk1.4.2\bin;d:\ora92\bin;D:\Program Files\Perl\bin\;F:\oracle\product\10.1.0\Db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Program Files\Perl\bin;D:\ewu\NT-Tools\gnu;c:\win32app\ewu;C:\Programme\cvsnt;C:\Programme\QuickTime\QTSystem\\" -classpath "../common/syslib/lib/bc4jdomorcl.jar;../common/syslib/bigraphbean.jar;../common/syslib/extlib/bc4jstruts.jar;../common/syslib/extlib/commons-dbcp.jar;../common/syslib/extlib/commons-fileupload.jar;../common/syslib/extlib/commons-lang.jar;../common/syslib/extlib/commons-net-1.4.1.jar;../common/syslib/extlib/commons-pool.jar;../common/syslib/extlib/commons-resources.jar;../common/syslib/extlib/commons-validator.jar;../common/syslib/extlib/help4.jar;../common/syslib/extlib/hsqldb.jar;../common/syslib/extlib/j2ssh-core.jar;../common/syslib/extlib/jakarta-oro-2.0.8.jar;../common/syslib/extlib/jasper_1.1.1/commons-beanutils-1.5.jar;../common/syslib/extlib/jasper_1.1.1/commons-collections-2.1.jar;../common/syslib/extlib/jasper_1.1.1/commons-digester-1.7.jar;../common/syslib/extlib/jasper_1.1.1/commons-logging-1.0.2.jar;../common/syslib/extlib/jasper_1.1.1/itext-1.3.1.jar;../common/syslib/extlib/jasper_1.1.1/jasperreports-1.1.1.jar;../common/syslib/extlib/jasper_1.1.1/poi-2.0-final-20040126.jar;../common/syslib/extlib/javacc.jar;../common/syslib/extlib/jce-jdk13-119.jar;../common/syslib/extlib/jcommon-0.9.6.jar;../common/syslib/extlib/jfreechart-0.9.21.jar;../common/syslib/extlib/JGantt.jar;../common/syslib/extlib/jmx/jmxremote.jar;../common/syslib/extlib/jmx/jmxremote_optional.jar;../common/syslib/extlib/jmx/jmxri.jar;../common/syslib/extlib/jmx/jmxtools.jar;../common/syslib/extlib/jmx/rmissl.jar;../common/syslib/extlib/log4j-1.2.7.jar;../common/syslib/extlib/ohj-jewt.jar;../common/syslib/extlib/oracle_ice5.jar;../common/syslib/extlib/struts.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mq.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mqbind.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mqjms.jar;../common/syslib/extlib/WebSphereMQ/connector.jar;../common/syslib/extlib/WebSphereMQ/fscontext.jar;../common/syslib/extlib/WebSphereMQ/jms.jar;../common/syslib/extlib/WebSphereMQ/jndi.jar;../common/syslib/extlib/WebSphereMQ/jta.jar;../common/syslib/extlib/WebSphereMQ/ldap.jar;../common/syslib/extlib/WebSphereMQ/postcard.jar;../common/syslib/extlib/WebSphereMQ/providerutil.jar;../common/syslib/extlib/WebSphereMQ/rmm.jar;../common/syslib/extlib/xalan.jar;../common/syslib/extlib/xercesImpl.jar;../common/syslib/extlib/xml-apis.jar;../common/syslib/home/jsp/lib/taglib/ojsputil.jar;../common/syslib/home/lib/activation.jar;../common/syslib/home/lib/aqapi.jar;../common/syslib/home/lib/mail.jar;../common/syslib/home/lib/ojsp.jar;../common/syslib/home/lib/servlet.jar;../common/syslib/jdev-cm.jar;../common/syslib/jewt4-nls.jar;../common/syslib/jewt4.jar;../common/syslib/jlib/bc4jctvb.jar;../common/syslib/jlib/bc4jdatum.jar;../common/syslib/jlib/bc4jdomgnrc.jar;../common/syslib/jlib/bc4jimjui.jar;../common/syslib/jlib/bc4jmtvb.jar;../common/syslib/jlib/bc4jui.jar;../common/syslib/lib/bc4jct.jar;../common/syslib/lib/bc4jctejb.jar;../common/syslib/lib/bc4jdomorcl.jar;../common/syslib/lib/bc4jhtml.jar;../common/syslib/lib/bc4jimdomains.jar;../common/syslib/lib/bc4jmt.jar;../common/syslib/lib/bc4jmtejb.jar;../common/syslib/lib/classes12.jar;../common/syslib/lib/collections.jar;../common/syslib/lib/jdev-rt.jar;../common/syslib/lib/nls_charset12.jar;../common/syslib/LW_PfjBean.jar;../common/syslib/share.jar;../common/syslib/xmlparserv2.jar;D:\Projects\CGN\Farms\aodb_install/run/lib/aodb.jar;D:\Projects\CGN\Farms\aodb_install/run;D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrapper.jar;D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrappertest.jar" -Dwrapper.key="TfZd_kb2MCtMXNFB" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=2980 -Dwrapper.version="3.2.0" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp Wrappertest 10000 1 DEBUG  | wrapper  | 2006/06/19 09:07:54 | JVM started (PID=3464)
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@e80a59
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2006/06/19 09:07:57 | 
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Running a 32-bit JVM.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2006/06/19 09:07:57 | Load native library.  One or more attempts may fail if platform specific libraries do not exist.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Loading native library failed: wrapper-windows-x86-32.dll  Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path
INFO   | jvm 1    | 2006/06/19 09:07:57 | Loaded native library: wrapper.dll
INFO   | jvm 1    | 2006/06/19 09:07:57 | Calling native initialization method.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Initializing WrapperManager native library.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java Executable: d:\Program Files\j2sdk1.4.2\bin\java.exe
INFO   | jvm 1    | 2006/06/19 09:07:57 | Windows version: 5.1.2600
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java Version   : 1.4.2_03-b02 Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 1    | 2006/06/19 09:07:57 | 
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1256ea2, args["10000", "1"]) called by thread: main
INFO   | jvm 1    | 2006/06/19 09:07:57 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 1    | 2006/06/19 09:07:57 | Failed attempt to bind using local port 31000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Opened Socket from 31001 to 32000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Send a packet KEY : TfZd_kb2MCtMXNFB
INFO   | jvm 1    | 2006/06/19 09:07:57 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001])
DEBUG  | wrapperp | 2006/06/19 09:07:57 | accepted a socket from 127.0.0.1 on port 31001 DEBUG  | wrapperp | 2006/06/19 09:07:57 | read a packet KEY : TfZd_kb2MCtMXNFB DEBUG  | wrapper  | 2006/06/19 09:07:57 | Got key from JVM: TfZd_kb2MCtMXNFB DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet LOW_LOG_LEVEL : 1 DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet PING_TIMEOUT : 30 DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet PROPERTIES : (Property Values) DEBUG  | wrapper  | 2006/06/19 09:07:57 | Start Application.
DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet START : start
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet PING_TIMEOUT : 30
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: PingTimeout from Wrapper is 30000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 1    | 2006/06/19 09:07:57 | Monitoring of the JVM thread count will be delayed for 1 seconds.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet START : start
INFO   | jvm 1    | 2006/06/19 09:07:57 | calling listener.start()
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperSimpleApp: invoking main method
INFO   | jvm 1    | 2006/06/19 09:07:57 | WRAPPERTEST: #############################################
INFO   | jvm 1    | 2006/06/19 09:07:57 | WRAPPERTEST: Sleeping for 10000ms
INFO   | jvm 1    | 2006/06/19 09:07:58 | Send a packet START_PENDING : 5000
DEBUG  | wrapperp | 2006/06/19 09:07:58 | read a packet START_PENDING : 5000 DEBUG  | wrapper  | 2006/06/19 09:07:58 | JVM signalled a start pending with waitHint of 5000 millis.
INFO   | wrapper  | 2006/06/19 09:07:59 | Waiting to start...
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet START_PENDING : 5000
INFO   | jvm 1    | 2006/06/19 09:07:59 | WrapperSimpleApp: start(args) end.  Main Completed=false, exitCode=null
INFO   | jvm 1    | 2006/06/19 09:07:59 | returned from listener.start()
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet STARTED : 
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet START_PENDING : 5000 DEBUG  | wrapper  | 2006/06/19 09:07:59 | JVM signalled a start pending with waitHint of 5000 millis.
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet STARTED : 
DEBUG  | wrapper  | 2006/06/19 09:07:59 | JVM signalled that it was started.
DEBUG  | wrapperp | 2006/06/19 09:07:59 | send a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:07:59 | Received a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet PING : ok
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet PING : ok DEBUG  | wrapper  | 2006/06/19 09:07:59 | Got ping response from JVM STATUS | wrapper  | 2006/06/19 09:08:01 | WRAPPERTEST started.
DEBUG  | wrapperp | 2006/06/19 09:08:04 | send a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:08:04 | Received a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:08:04 | Send a packet PING : ok
INFO   | jvm 1    | 2006/06/19 09:08:04 | Non-daemon thread count = 2 - 1(system) = 1
DEBUG  | wrapperp | 2006/06/19 09:08:04 | read a packet PING : ok DEBUG  | wrapper  | 2006/06/19 09:08:04 | Got ping response from JVM
INFO   | jvm 1    | 2006/06/19 09:08:07 | WRAPPERTEST: Exiting with code 1
INFO   | jvm 1    | 2006/06/19 09:08:07 | Wrapper Manager: ShutdownHook started
INFO   | jvm 1    | 2006/06/19 09:08:07 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2006/06/19 09:08:07 | Send a packet STOP : 0
DEBUG  | wrapperp | 2006/06/19 09:08:07 | read a packet STOP : 0 DEBUG  | wrapper  | 2006/06/19 09:08:07 | JVM requested a shutdown. (0) DEBUG  | wrapper  | 2006/06/19 09:08:07 | wrapperStopProcess(0) called.
DEBUG  | wrapper  | 2006/06/19 09:08:07 | Sending stop signal to JVM DEBUG  | wrapperp | 2006/06/19 09:08:07 | send a packet STOP : NULL
INFO   | jvm 1    | 2006/06/19 09:08:07 | Received a packet STOP : 
INFO   | jvm 1    | 2006/06/19 09:08:07 | Non-daemon thread count = 3 - 1(system) = 2
INFO   | jvm 1    | 2006/06/19 09:08:08 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
INFO   | jvm 1    | 2006/06/19 09:08:08 | calling listener.stop()
INFO   | jvm 1    | 2006/06/19 09:08:08 | WrapperSimpleApp: stop(0)
INFO   | jvm 1    | 2006/06/19 09:08:08 | returned from listener.stop()
INFO   | jvm 1    | 2006/06/19 09:08:08 | Send a packet STOPPED : 0
DEBUG  | wrapperp | 2006/06/19 09:08:08 | read a packet STOPPED : 0 DEBUG  | wrapper  | 2006/06/19 09:08:08 | JVM signalled that it was stopped.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Closing socket.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Closed socket: java.net.SocketException: socket closed
DEBUG  | wrapperp | 2006/06/19 09:08:09 | socket read no code (closed?).
DEBUG  | wrapperp | 2006/06/19 09:08:09 | server listening on port 32001.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Server daemon shut down
INFO   | jvm 1    | 2006/06/19 09:08:09 | Wrapper Manager: ShutdownHook complete
DEBUG  | wrapper  | 2006/06/19 09:08:09 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
DEBUG  | wrapper  | 2006/06/19 09:08:09 | JVM exited normally.
STATUS | wrapper  | 2006/06/19 09:08:09 | <-- Wrapper Stopped

What am I doing wrong?

Thanks,
Andreas

Re: [Wrapper-user] wrapper.on_exit seems not to work in 3.2.0

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

Andreas,
    Sorry.  That is a known bug in 3.2.0 that has been fixed in CVS.  It 
will be in the 3.2.1
release.  I need to hurry up and get that out the door.

    Here is the current list of changes for the 3.2.1 release:

Cheers,
Leif

Java Service Wrapper Revision History.
--------------------------------------
3.2.1
* Fix a problem with the solaris-sparc-64 makefile.
* Add a solaris-x86-64 makefile.
* Merge in a patch by Hugo Weber to make it possible to configure the 
Wrapper
  to pull the JRE from the system registry on windows.
* Fix a batch file bug added in 3.2.0 where the scripts would not function
  correctly if the full path to the batch file contained spaces.
  Bug #1450601.
* Modify the message shown when a native library fails to load so the
  exception message text is now shown in the log without having to enable
  debug log output.
* Modify the UNIX shell script to be more informative if the script is 
unable
  to locate a wrapper binary due to a executable bit permission problem.
* Fix a minor permission problem with the build for the delta-pack.
* Commit a patch by Juergen Hermann to make the error shown when realpath
  fails clearer.
* Add the ability to use a default wrapper.conf file that is in the same
  directory as the wrapper binary.  The file will be named based on the
  name of the wrapper binary.
* Synchronize the command line so that both the Windows and UNIX versions
  are now the same.  The old command line syntaxes are now supported
  everywhere so there will be no compatibility problems.
* It is no longer possible to specify arguments using the '/c' syntax.
  This was undocumented so hopefully it is not being used.  The documented
  '-c' syntax must now be used.  The change was necessary to synchronize
  the command line between UNIX and windows platforms.
* The 32-bit HP-UX 3.2.0 build was generating a libwrapper.so file rather
  than libwrapper.sl.
* Make the WrapperManager.setConsoleTitle, getWrapperPID, and getJavaPID
  methods available through JMX.
* Fix a state engine problem introduced in 3.2.0 which was causing the
  wrapper.on_exit.<n> properties to be ignored in most cases.
* Fix a potential problem that could have caused crashes when debug logging
  was enabled.
* Fix a problem where signals were not being handled correctly on some UNIX
  platforms, including AIX.  This was making it impossible to shutdown the
  wrapper cleanly with the TERM signal.  Bug #1477619.
* Add new default environment variables which can be referenced in a
  configuration file to configure platform specific directories and file
  names.  WRAPPER_OS, WRAPPER_ARCH, and WRAPPER_BITS.
* Add a -v argument to make it possible to request the version from a 
wrapper
  binary.
* Add support for registering the WrapperManager MBean with the
  PlatformMBeanServer when run on a 1.5+ JVM.  See the JMX section in the
  documentation for details.
* Rework the way timeout properties are handled.  Values of 0 now actually
  disable the timeouts rather than setting them to a large value.  To avoid
  overflow problems when converting to internal timer ticks, timeouts 
are now
  restricted to a maximum of 20 days, or 1728000 seconds.  Change 
affects the
  wrapper.cpu.timeout, wrapper.startup.timeout, wrapper.ping.timeout,
  wrapper.shutdown.timeout, and wrapper.jvm_exit.timeout properties.  For
  values less than 20 days, there should be no change in functionality.
* Add support for debuggers.  The Wrapper will now show a warning on startup
  and then again the first time a timeout occurs.  But all timeouts will be
  ignored.  This is to avoid problems with the Wrapper restarting a 
suspended
  JVM in the middle of a debugging session.  The wrapper enters this mode if
  the wrapper.java.command ends with the string "jdb" or "jdb.exe", or the
  "-Xdebug" parameter is passed to the JVM.
* Add 'athlon' to the list of supported architectures.
* Fix a problem where the environment variables loaded when a service was
  started were always the system environment even if the service was running
  as a specific account.  The environment of a specific account will now be
  loaded on top of the system environment if the USERNAME environment
  variable is set by the system.  Bug #1491138.

[Wrapper-user] wrapper.on_exit seems not to work in 3.2.0

[<And...@t-...>]

Hi,

I switched from 3.1.2 to 3.2.0 recently and my processes do not restart any more.
I wrote a little test class to nail down the problem, and it seems to be the wrapper.
The test class only gets restarted when setting "disable_shutdown_hook" to TRUE, but
then I cannot control the restart bevahior using System.exit(n)

Test code:
==========
public class Wrappertest
{
  public static void main( String[] args)
  {
    try
    {
      long sleepTime = Long.parseLong(args[0]);
      int exitCode = Integer.parseInt(args[1]);
      System.out.println("WRAPPERTEST: #############################################");
      System.out.println("WRAPPERTEST: Sleeping for "+sleepTime+"ms");
      Thread.sleep(sleepTime);
      System.out.println("WRAPPERTEST: Exiting with code "+exitCode);
      System.exit(exitCode);
    }
    catch( Exception e)
    {
      e.printStackTrace();
      System.err.println();
      System.err.println("Usage: java Wrappertest <sleeptime in ms> <exit code>");
      System.err.println();
    }
  }
}

Wrapper configuration:
======================
#include %AODB_HOME%/run/etc/set_classpath.cfg
wrapper.java.command=java
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=Wrappertest
wrapper.app.parameter.2=10000
# exit code 1 should initiate restart
wrapper.app.parameter.3=1
wrapper.on_exit.-1=RESTART
wrapper.on_exit.1=RESTART
wrapper.on_exit.255=RESTART
#wrapper.disable_shutdown_hook=TRUE
wrapper.console.format=PM
wrapper.console.loglevel=NONE
wrapper.logfile=%AODB_HOME%/run/log/wrappertest.log
wrapper.logfile.format=LPTM
wrapper.logfile.loglevel=DEBUG
wrapper.logfile.maxsize=1m
wrapper.logfile.maxfiles=10
wrapper.syslog.loglevel=NONE
wrapper.console.title=WRAPPERTEST
wrapper.ntservice.name=WRAPPERTEST
wrapper.ntservice.displayname=WRAPPERTEST
wrapper.ntservice.description=WRAPPERTEST
wrapper.ntservice.starttype=AUTO_START
wrapper.ntservice.interactive=false
wrapper.java.pidfile=%AODB_HOME%/run/var/wrappertest.pid
wrapper.lockfile=%AODB_HOME%/run/var/wrappertest.lck
wrapper.anchorfile=%AODB_HOME%/run/var/wrappertest.anc
wrapper.debug=TRUE

Wrappertest.log
===============
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Service command: D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin\wrapper.exe -s D:\Projects\CGN\Farms\aodb_install\run\config\Wrappertest.cfg set.WRAPPER_DIR=D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin set.SYSLIB_DIR=../common/syslib set.AODB_HOME=D:\Projects\CGN\Farms\aodb_install wrapper.working.dir=D:\Projects\CGN\Farms\aodb_install\run
ERROR  | wrapper  | 2006/06/19 09:07:54 | CreateService failed - Der angegebene Dienst ist bereits vorhanden. (0x431)
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
STATUS | wrapper  | 2006/06/19 09:07:54 | Starting the WRAPPERTEST service...
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Working directory set to: D:\Projects\CGN\Farms\aodb_install\run
STATUS | wrapper  | 2006/06/19 09:07:54 | --> Wrapper Started as Service
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Using tick timer.
DEBUG  | wrapperp | 2006/06/19 09:07:54 | server listening on port 32000.
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.28, does not exist: ../common/syslib/extlib/jmx/jmxremote_optional.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.30, does not exist: ../common/syslib/extlib/jmx/jmxtools.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.31, does not exist: ../common/syslib/extlib/jmx/rmissl.jar
DEBUG  | wrapper  | 2006/06/19 09:07:54 | Classpath element, wrapper.java.classpath.83, does not exist: D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrappertest.jar
STATUS | wrapper  | 2006/06/19 09:07:54 | Launching a JVM...
DEBUG  | wrapper  | 2006/06/19 09:07:54 | command: "d:\Program Files\j2sdk1.4.2\bin\java.exe" -Djava.library.path="D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib;d:\Program Files\j2sdk1.4.2\bin;d:\ora92\bin;D:\Program Files\Perl\bin\;F:\oracle\product\10.1.0\Db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\Program Files\Perl\bin;D:\ewu\NT-Tools\gnu;c:\win32app\ewu;C:\Programme\cvsnt;C:\Programme\QuickTime\QTSystem\\" -classpath "../common/syslib/lib/bc4jdomorcl.jar;../common/syslib/bigraphbean.jar;../common/syslib/extlib/bc4jstruts.jar;../common/syslib/extlib/commons-dbcp.jar;../common/syslib/extlib/commons-fileupload.jar;../common/syslib/extlib/commons-lang.jar;../common/syslib/extlib/commons-net-1.4.1.jar;../common/syslib/extlib/commons-pool.jar;../common/syslib/extlib/commons-resources.jar;../common/syslib/extlib/commons-validator.jar;../common/syslib/extlib/help4.jar;../common/syslib/extlib/hsqldb.jar;../common/syslib/extlib/j2ssh-core.jar;../common/syslib/extlib/jakarta-oro-2.0.8.jar;../common/syslib/extlib/jasper_1.1.1/commons-beanutils-1.5.jar;../common/syslib/extlib/jasper_1.1.1/commons-collections-2.1.jar;../common/syslib/extlib/jasper_1.1.1/commons-digester-1.7.jar;../common/syslib/extlib/jasper_1.1.1/commons-logging-1.0.2.jar;../common/syslib/extlib/jasper_1.1.1/itext-1.3.1.jar;../common/syslib/extlib/jasper_1.1.1/jasperreports-1.1.1.jar;../common/syslib/extlib/jasper_1.1.1/poi-2.0-final-20040126.jar;../common/syslib/extlib/javacc.jar;../common/syslib/extlib/jce-jdk13-119.jar;../common/syslib/extlib/jcommon-0.9.6.jar;../common/syslib/extlib/jfreechart-0.9.21.jar;../common/syslib/extlib/JGantt.jar;../common/syslib/extlib/jmx/jmxremote.jar;../common/syslib/extlib/jmx/jmxremote_optional.jar;../common/syslib/extlib/jmx/jmxri.jar;../common/syslib/extlib/jmx/jmxtools.jar;../common/syslib/extlib/jmx/rmissl.jar;../common/syslib/extlib/log4j-1.2.7.jar;../common/syslib/extlib/ohj-jewt.jar;../common/syslib/extlib/oracle_ice5.jar;../common/syslib/extlib/struts.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mq.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mqbind.jar;../common/syslib/extlib/WebSphereMQ/com.ibm.mqjms.jar;../common/syslib/extlib/WebSphereMQ/connector.jar;../common/syslib/extlib/WebSphereMQ/fscontext.jar;../common/syslib/extlib/WebSphereMQ/jms.jar;../common/syslib/extlib/WebSphereMQ/jndi.jar;../common/syslib/extlib/WebSphereMQ/jta.jar;../common/syslib/extlib/WebSphereMQ/ldap.jar;../common/syslib/extlib/WebSphereMQ/postcard.jar;../common/syslib/extlib/WebSphereMQ/providerutil.jar;../common/syslib/extlib/WebSphereMQ/rmm.jar;../common/syslib/extlib/xalan.jar;../common/syslib/extlib/xercesImpl.jar;../common/syslib/extlib/xml-apis.jar;../common/syslib/home/jsp/lib/taglib/ojsputil.jar;../common/syslib/home/lib/activation.jar;../common/syslib/home/lib/aqapi.jar;../common/syslib/home/lib/mail.jar;../common/syslib/home/lib/ojsp.jar;../common/syslib/home/lib/servlet.jar;../common/syslib/jdev-cm.jar;../common/syslib/jewt4-nls.jar;../common/syslib/jewt4.jar;../common/syslib/jlib/bc4jctvb.jar;../common/syslib/jlib/bc4jdatum.jar;../common/syslib/jlib/bc4jdomgnrc.jar;../common/syslib/jlib/bc4jimjui.jar;../common/syslib/jlib/bc4jmtvb.jar;../common/syslib/jlib/bc4jui.jar;../common/syslib/lib/bc4jct.jar;../common/syslib/lib/bc4jctejb.jar;../common/syslib/lib/bc4jdomorcl.jar;../common/syslib/lib/bc4jhtml.jar;../common/syslib/lib/bc4jimdomains.jar;../common/syslib/lib/bc4jmt.jar;../common/syslib/lib/bc4jmtejb.jar;../common/syslib/lib/classes12.jar;../common/syslib/lib/collections.jar;../common/syslib/lib/jdev-rt.jar;../common/syslib/lib/nls_charset12.jar;../common/syslib/LW_PfjBean.jar;../common/syslib/share.jar;../common/syslib/xmlparserv2.jar;D:\Projects\CGN\Farms\aodb_install/run/lib/aodb.jar;D:\Projects\CGN\Farms\aodb_install/run;D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrapper.jar;D:\Projects\CGN\Farms\aodb_install\common\syslib\extlib\wrapper\windows\bin/../lib/wrappertest.jar" -Dwrapper.key="TfZd_kb2MCtMXNFB" -Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=2980 -Dwrapper.version="3.2.0" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp Wrappertest 10000 1
DEBUG  | wrapper  | 2006/06/19 09:07:54 | JVM started (PID=3464)
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@e80a59
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2006/06/19 09:07:57 | 
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Running a 32-bit JVM.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2006/06/19 09:07:57 | Load native library.  One or more attempts may fail if platform specific libraries do not exist.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Loading native library failed: wrapper-windows-x86-32.dll  Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in java.library.path
INFO   | jvm 1    | 2006/06/19 09:07:57 | Loaded native library: wrapper.dll
INFO   | jvm 1    | 2006/06/19 09:07:57 | Calling native initialization method.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Initializing WrapperManager native library.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java Executable: d:\Program Files\j2sdk1.4.2\bin\java.exe
INFO   | jvm 1    | 2006/06/19 09:07:57 | Windows version: 5.1.2600
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java Version   : 1.4.2_03-b02 Java HotSpot(TM) Client VM
INFO   | jvm 1    | 2006/06/19 09:07:57 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 1    | 2006/06/19 09:07:57 | 
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1256ea2, args["10000", "1"]) called by thread: main
INFO   | jvm 1    | 2006/06/19 09:07:57 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 1    | 2006/06/19 09:07:57 | Failed attempt to bind using local port 31000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Opened Socket from 31001 to 32000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Send a packet KEY : TfZd_kb2MCtMXNFB
INFO   | jvm 1    | 2006/06/19 09:07:57 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31001])
DEBUG  | wrapperp | 2006/06/19 09:07:57 | accepted a socket from 127.0.0.1 on port 31001
DEBUG  | wrapperp | 2006/06/19 09:07:57 | read a packet KEY : TfZd_kb2MCtMXNFB
DEBUG  | wrapper  | 2006/06/19 09:07:57 | Got key from JVM: TfZd_kb2MCtMXNFB
DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet PING_TIMEOUT : 30
DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet PROPERTIES : (Property Values)
DEBUG  | wrapper  | 2006/06/19 09:07:57 | Start Application.
DEBUG  | wrapperp | 2006/06/19 09:07:57 | send a packet START : start
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet PING_TIMEOUT : 30
INFO   | jvm 1    | 2006/06/19 09:07:57 | Wrapper Manager: PingTimeout from Wrapper is 30000
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 1    | 2006/06/19 09:07:57 | Monitoring of the JVM thread count will be delayed for 1 seconds.
INFO   | jvm 1    | 2006/06/19 09:07:57 | Received a packet START : start
INFO   | jvm 1    | 2006/06/19 09:07:57 | calling listener.start()
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the main method to complete.
INFO   | jvm 1    | 2006/06/19 09:07:57 | WrapperSimpleApp: invoking main method
INFO   | jvm 1    | 2006/06/19 09:07:57 | WRAPPERTEST: #############################################
INFO   | jvm 1    | 2006/06/19 09:07:57 | WRAPPERTEST: Sleeping for 10000ms
INFO   | jvm 1    | 2006/06/19 09:07:58 | Send a packet START_PENDING : 5000
DEBUG  | wrapperp | 2006/06/19 09:07:58 | read a packet START_PENDING : 5000
DEBUG  | wrapper  | 2006/06/19 09:07:58 | JVM signalled a start pending with waitHint of 5000 millis.
INFO   | wrapper  | 2006/06/19 09:07:59 | Waiting to start...
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet START_PENDING : 5000
INFO   | jvm 1    | 2006/06/19 09:07:59 | WrapperSimpleApp: start(args) end.  Main Completed=false, exitCode=null
INFO   | jvm 1    | 2006/06/19 09:07:59 | returned from listener.start()
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet STARTED : 
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet START_PENDING : 5000
DEBUG  | wrapper  | 2006/06/19 09:07:59 | JVM signalled a start pending with waitHint of 5000 millis.
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet STARTED : 
DEBUG  | wrapper  | 2006/06/19 09:07:59 | JVM signalled that it was started.
DEBUG  | wrapperp | 2006/06/19 09:07:59 | send a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:07:59 | Received a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:07:59 | Send a packet PING : ok
DEBUG  | wrapperp | 2006/06/19 09:07:59 | read a packet PING : ok
DEBUG  | wrapper  | 2006/06/19 09:07:59 | Got ping response from JVM
STATUS | wrapper  | 2006/06/19 09:08:01 | WRAPPERTEST started.
DEBUG  | wrapperp | 2006/06/19 09:08:04 | send a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:08:04 | Received a packet PING : ping
INFO   | jvm 1    | 2006/06/19 09:08:04 | Send a packet PING : ok
INFO   | jvm 1    | 2006/06/19 09:08:04 | Non-daemon thread count = 2 - 1(system) = 1
DEBUG  | wrapperp | 2006/06/19 09:08:04 | read a packet PING : ok
DEBUG  | wrapper  | 2006/06/19 09:08:04 | Got ping response from JVM
INFO   | jvm 1    | 2006/06/19 09:08:07 | WRAPPERTEST: Exiting with code 1
INFO   | jvm 1    | 2006/06/19 09:08:07 | Wrapper Manager: ShutdownHook started
INFO   | jvm 1    | 2006/06/19 09:08:07 | WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2006/06/19 09:08:07 | Send a packet STOP : 0
DEBUG  | wrapperp | 2006/06/19 09:08:07 | read a packet STOP : 0
DEBUG  | wrapper  | 2006/06/19 09:08:07 | JVM requested a shutdown. (0)
DEBUG  | wrapper  | 2006/06/19 09:08:07 | wrapperStopProcess(0) called.
DEBUG  | wrapper  | 2006/06/19 09:08:07 | Sending stop signal to JVM
DEBUG  | wrapperp | 2006/06/19 09:08:07 | send a packet STOP : NULL
INFO   | jvm 1    | 2006/06/19 09:08:07 | Received a packet STOP : 
INFO   | jvm 1    | 2006/06/19 09:08:07 | Non-daemon thread count = 3 - 1(system) = 2
INFO   | jvm 1    | 2006/06/19 09:08:08 | Thread, Wrapper-Shutdown-Hook, handling the shutdown process.
INFO   | jvm 1    | 2006/06/19 09:08:08 | calling listener.stop()
INFO   | jvm 1    | 2006/06/19 09:08:08 | WrapperSimpleApp: stop(0)
INFO   | jvm 1    | 2006/06/19 09:08:08 | returned from listener.stop()
INFO   | jvm 1    | 2006/06/19 09:08:08 | Send a packet STOPPED : 0
DEBUG  | wrapperp | 2006/06/19 09:08:08 | read a packet STOPPED : 0
DEBUG  | wrapper  | 2006/06/19 09:08:08 | JVM signalled that it was stopped.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Closing socket.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Closed socket: java.net.SocketException: socket closed
DEBUG  | wrapperp | 2006/06/19 09:08:09 | socket read no code (closed?).
DEBUG  | wrapperp | 2006/06/19 09:08:09 | server listening on port 32001.
INFO   | jvm 1    | 2006/06/19 09:08:09 | Server daemon shut down
INFO   | jvm 1    | 2006/06/19 09:08:09 | Wrapper Manager: ShutdownHook complete
DEBUG  | wrapper  | 2006/06/19 09:08:09 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
DEBUG  | wrapper  | 2006/06/19 09:08:09 | JVM exited normally.
STATUS | wrapper  | 2006/06/19 09:08:09 | <-- Wrapper Stopped

What am I doing wrong?

Thanks,
Andreas