RE: [Wrapper-user] Wrapper notification...

[Luis G. <lui...@sk...>]

Leif,
Yes tell me about it.  What we run is a backend / app / client
environment, and our app does a lot of number crunching which requires a
lot of system for just one client environment.  One of our client has 2
environment, one prod and the second is their test env which they test
our new releases.  This totals about 30 machines.   Plus our own
environments for testing and for our other clients givings us the grand
total of about 80 machines. =20
We use JBoss as our platform env.  Well to put it simple terms.  With
the exception of the app servers, the computing jobs are sent to servers
running several instances of the wrapper launching separate JVMs.  Our
app isn't multi threaded to handle multiple jobs due to memory
constraints with the data that is handled.  When that happens, which
won't be in the near future, there would only be 1 instance.  So we need
to have separate JVMs.  As you can see, I how truly happy I was to find
the wrapper and made every effort to support the software.  This has
made my job easier to script stopping and starting services and
monitoring.  =20

We already use log4j to manage our systems logging, etc.. but the issue
arises with getting notification when a jvm dies due to out of memory
errors, where log4j dies with that jvm.

As I read from the previous email, I'm guessing my option of the wrapper
on filter.action=3Dshutdown, would not invoke the NT service recovery.  =
Is
this correct or did I misread?

So back to the discussion, I can see the issue of supporting multiple
events.  But since the focus of the wrapper is running jvm as service
and providing reliability, this should be limited to events that are not
controllable within a JVM which usually turns out to be a JVM shutdown.
This should be supported by allowing executing a system call, keeping
the changes to the wrapper to a minimal.

Thanks for your help.

Luis


-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...]=20
Sent: Wednesday, November 05, 2003 9:58 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Wrapper notification...

Luis,

>Now the question about sending email can be rephrased.  Instead of an
>email, the ability to execute something on shutdown would leave the
door
>open for everyone to create their own custom tools around the event.
>
>Again, my reason for asking is mainly because on some machines we are
>running 5 different services.  Now multiply that 60 machines, that's
300
>services that I would need to modify.  And our dynamics could change 3
>of those services to different configuration for different databases.
>So, I hope you can understand where I'm heading with these figures.
> =20
>
If you have 300 copies of the Wrapper running, A) I am impressed, what=20
are  you running?
But I do see the maintenance problem you are trying to avoid.   Once I=20
add the ability to
register additional WrapperListeners, this will be easier.  But for now,

I would suggest making
a copy of the WrapperSimpleApp or WrapperStartStopApp class and then=20
modifying the
start, stop, and controlEvent methods to do what you need.  You will=20
then be able to reuse
that new helper class on all of your services without having to modify=20
any other code.  You
will have problems when you need to upgrade the from the original code=20
on the next
release.  But hopefully I will be able to modify the classes so that=20
they can be "extended"
without the need to modify them in the future.

Cheers,
Leif




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

_______________________________________________________
This message is for the named recipient's use only.  It may contain =
sensitive and private proprietary information.  No confidentiality is =
waived or lost by any incorrect transmission.  If you are not the =
intended recipient, please immediately delete it and all copies of it =
from your system, destroy any hard copies of it and notify the sender.  =
You must not, directly or indirectly, use, disclose, distribute, print, =
or copy any part of this message if you are not the intended recipient.  =
Sakonnet Technology, LLC and its subsidiaries reserve the right to =
monitor all e-mail communications through their networks. Any views =
expressed in this message are those of the individual sender, except =
where the message states otherwise and the sender is authorized to state =
them to be the views of any such entity.  Unless otherwise stated, any =
pricing information given in this message is indicative only, is subject =
to change and does not constitute an offer to deal at any price quoted. =
Any reference to the terms of executed transactions should be treated as =
preliminary only and subject to our formal written confirmation.=20