Didn't you say you could already do this?
Yes, but it is a little hacky. MBeans seem a more approiate way to go and
wanted to know if they could be used for this.
You need to write a service that knows that all webapps have started, or
have your load balancer test each one before reporting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stront,
Stront wrote:
| Didn't you say you could already do this?
|
| Yes, but it is a little hacky. MBeans seem a more approiate way to go and
| wanted to know if they could be used for this.
|
| You need to write a service that knows that all
So can anyone answer my initial question: How can I determine
1. That the server is not in the a startup, shutdown stage in it lifecycle;
has acheived the after_start state
2. That all of the webapps are started
?
Thanks.
David Fisher wrote:
I think what the experts are saying is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stront,
Stront wrote:
| So can anyone answer my initial question: How can I determine
|
| 1. That the server is not in the a startup, shutdown stage in it
lifecycle;
| has acheived the after_start state
Didn't you say you could already do this?
|
From: Stront [mailto:[EMAIL PROTECTED]
2. That all of the webapps are running.
That's webapp-dependent, surely? Tomcat can't determine all the ways in
which your application can fail.
But it can tell if the app has started; Tomcat's manager displays a list of
apps and whether it is
From: Stront [mailto:[EMAIL PROTECTED]
2. That all of the webapps are running.
That's webapp-dependent, surely? Tomcat can't determine all the ways in which
your application can fail.
- Peter
-
To start a
I think what the experts are saying is that even if your webapps is
started it could be dependent on a large startup operation.
Take for example Apache Roller which can take several minutes to
rebuild its persistence state and while up will reject requests.
The only way to know if the
