|
From: Christian <chr...@ta...> - 2010-09-17 02:43:41
|
vishal,
please have a look on the Service Controller ("sc") command available on
windows since WinNT4.
you might take a look at the "failure"-part:
DESCRIPTION:
Changes the actions upon failure
USAGE:
sc <server> failure [service name] <option1> <option2>...
OPTIONS:
reset= <Length of period of no failures (in seconds)
after which to reset the failure count to 0 (may be
INFINITE)>
(Must be used in conjunction with actions= )
reboot= <Message broadcast before rebooting on failure>
command= <Command line to be run on failure>
actions= <Failure actions and their delay time (in
milliseconds),
separated by / (forward slash) -- e.g.,
run/5000/reboot/800
Valid actions are <run|restart|reboot> >
(Must be used in conjunction with the reset= option)
Hope this helps you out.
Sincerely,
Christian
-----Original Message-----
From: Vishal K <vis...@gm...>
Reply-to: wra...@li...
To: wra...@li...
Subject: Re: [Wrapper-user] Wrapper-user Digest, Vol 52, Issue 4
Date: Thu, 16 Sep 2010 10:50:23 -0400
Hi Leif,
Thanks for the info. This method does not work for us since it requires
manual setup. I think this is a serious limitation of the wrapper.
Unfortunately, without this fix we may not be able to use Tanuki. Do you
have an estimate of when a fix for this would be released? Can we do the
recovery settings that you mentioned by running an external command (and
need not be part of wrapper.exe)? If yes, that would work as an
temporary solution until a real fix is available, because we can script
it.
Your help will be greatly appreciated.
Regards,
-Vishal
Date: Thu, 16 Sep 2010 19:42:57 +0900
From: Leif Mortenson <lei...@ta...>
Subject: Re: [Wrapper-user] What happens if wrapper.exe dies?
To: wra...@li...
Message-ID:
<AANLkTikHFr3ht
+gFR...@ma...>
Content-Type: text/plain; charset=ISO-8859-1
Vishal,
After you have installed the Wrapper as a service, go into the
Windows
Service Manager and view the Properties for the Wrapper
service. You
can set this up using the "Recovery" tab.
http://mdenomy.files.wordpress.com/2008/02/configuring-recovery-2.jpg?w=500
If you kill the Wrapper process, then the JVM will keep running
for up
to 3 times the value of the wrapper.ping.timeout property. It
will
then shut itself down. If you use the Recovery feature, I
recommend
setting the delay before restart to at least this long. If you
start
a second JVM before the first has shut itself down then you
would
encounter port conflicts when the second JVM tries to start.
You
could handle such errors with the normal JVM restart features in
the
second Wrapper instance however.
We are looking into what would be involved to support this
directly
from the Wrapper configuration file. That would be in a future
release however.
Please let me know how this works for you.
Cheers,
Leif
On Thu, Sep 16, 2010 at 8:35 AM, Vishal K <vis...@gm...>
wrote:
> Hi All,
>
> I am using java service wrapper on Windows. While
experimenting with the
> wrapper I noticed that if I kill wrapper.exe my also
application dies. After
> wards, neither the wrapper.exe nor my application gets
restarted. Looks like
> we need to run wrapper.exe as a windows service as well.
>
> Any advise on how I can programatically get around this
problem?
>
> Thanks.
> -Vishal
------------------------------
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user
|