This problem is one of those missing feature in AJP13 project. For now,
Mod_jk2 can not see if your application is ready yet.
But i too am loooking for an interim alternative from tomcat side. I have
got suggestions from these mail forums that it is almost not a realistic
incident, and this happens only at the start-up time of the servers and so
tomcat should be started before apache.
But it doesnt work with our network model. We have 2 apaches and i cant down
both the apaches at the same time.
Please post if you guy find any thing on this.
Cheers,
BK
This appears to be a basic issue with using Apache Web Server ->
modjk2 -> Tomcat instances in cluster configuration. A Tomcat
Instance's going down or joining the cluster should not be noticed by
end users. Still wondering if anyone has configured the cluster so
that when a Tomcat Node is still not completely up, Apache Web Server
does not forward requests to it.
Thanks
Nanda
>
>
> > Hi!
> >
> > tomcat 4.1.29/apache 2.0.49
> >
> > I have a cluster with Apache Web Server load balancing over three
> > tomcat workers. In the middle of the tests, when one of the tomcat
> > workers was restarted, I noticed even before the server was
brought
> up
> > completely*, Apache forwarded requests to the server, which
resulted
> > in "HTTP Status 500 - No Context configured to process this
> request".
> >
> > * all web applications are completely deployed and ready for
access
> >
> > Is there a configuration option to instruct Apache Web Server to
> > forward requests only after server is started up completely (maybe
> > detecting the status code 200)?
> >
> > regards
---
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
__________________________________________________________________________________________________________________________________
For information about the Standard Bank group visit our web site
<www.standardbank.co.za>
__________________________________________________________________________________________________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relating to the official business of
Standard Bank Group Limited is proprietary to the group.
It is confidential, legally privileged and protected by law.
Standard Bank does not own and endorse any other content. Views and opinions are those
of the sender unless clearly stated as being that of the group.
The person addressed in the e-mail is the sole authorised recipient. Please notify the
sender immediately if it has unintentionally reached you and do not read,
disclose or use the content in any way.
Standard Bank can not assure that the integrity of this communication has been
maintained nor that it is free of errors, virus, interception or interference.
___________________________________________________________________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
