: monitoring an application
Hi Sumit,
Yes! that shows that we are on course in the right direction .. it
would be an interface like that .. can't use that interface as is as
it belongs to the com.sun.* namespace
Cheers
Piyush
On 11/14/06, Piyush Purang [EMAIL PROTECTED] wrote:
Yes, John this is a real world requirement this we are out for a
coffee thingy :)
Indeed. :-)
Throttling usage during overloads is critically important to
gracefully surviving things like getting slashdotted. Doing this at
the application
On 11/14/06, Jerome Louvel [EMAIL PROTECTED] wrote:
We can feel the heat just by reading your requirement!
:-)
Creating a public search engine for developers like Krugle makes me a
bit sensitive/paranoid about these sorts of issues.
Definitely worth
considering more seriously. Added new
Hi Sumit,
I have a question about how other are using the
Application.isStopped() method.
If a given application is unhealthy (for example, broken
client connectors), is
it appropriate for the Application to mark itself stopped?
There is a simple lifecycle: an application is created in
I think we need to put in a little more thought about lifecycles first
... the states that i would love to have is
created (The application was created/initialized properly but never started)
started (The application has been asked to run)
running (The application is successfully running maybe
Objet : Re: monitoring an application
I think we need to put in a little more thought about lifecycles first
... the states that i would love to have is
created (The application was created/initialized properly but
never started)
started (The application has been asked to run)
running
Hi all,
I have a question about how other are using the Application.isStopped() method.
If a given application is unhealthy (for example, broken client connectors), is
it appropriate for the Application to mark itself stopped?
I am writing a restlet that monitors the state of all applications
7 matches
Mail list logo
