----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Jerome Gudgeon wrote:
>
>
> Solaris 2.6, Apache 1.9 JDK1.1.8, JServ 1.1
>
> I have a fairly high demand site that uses 25 JServs using loadbalancing
> that works fast, however, I regularly get the following in the
> mod_jserv.log for differing port numbers:
>
> [15/03/2000 14:55:02:126] (EMERGENCY) ajp12: can not connect to host
> 127.0.0.1:9521
> [15/03/2000 14:55:02:159] (EMERGENCY) ajp12: connection fail
> [15/03/2000 14:55:02:159] (ERROR) an error returned handling request via
> protocol "ajpv12"
>
> They generally carry on working but is this a symptom of overdemand or that
> the loadbalancer is not picking an available JServ?
>
> If the above error occurs should I restart that particular JServ?
>
> A further observation is that I need to restart the JServs on average three
> times a day otherwise it more regularly fails to serve pages - Im guessing
> that this is again the load balancer not detecting bad JServs.
The load-balancer does not itself monitor JServs. In 2 words :
- we get a hit.
- we choose a working (looking at the shared memory) JServ target
(depends if a session is already established/not)
- we send the request to the chosen JServ
- if the request fails this JServ is marked "down" in the shared memory.
>
> Any advise on monitoring individual JServs and the load balancing
try to use the shmedit tool that is accessible in the web CVS interface
to examine the status of the shared memory (or use the GUI)
Tell us what you found in this area.
Jean-Luc
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]