Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of jamin.short@gmail.com
 designates 64.233.162.234 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=B1WWPkW+ughHPkaTjsqm+bSHWMuZtFrmhBFNL8ynyiISMx2Xy+4rQHdehFJ9Y23aG0IEIml5ynRtV1Vx5Xb+qOnWf9xSw0bY9G2yqXDua+P6hQH5rA7+PAvoSc0qTbT3c+RGjDw10vINkMY+4hJGOwdaCvF8JTdhh2D9BhIrwQc=
Message-ID: <86aa493a0708020301v77ba3322g2043fc95b7a98b24@mail.gmail.com>
Date: Thu, 2 Aug 2007 11:01:23 +0100
From: "ben short" <jamin.short@gmail.com>
To: "Tomcat Users List" <users@tomcat.apache.org>
Subject: Re: Tomcat cluster serving ~50 lines of the page when a request hits
 a stopped webapp for the first time
In-Reply-To: <86aa493a0708011536y1e688654t5f5be17c24888d3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <86aa493a0707300530s40858585yf34f4931c2801282@mail.gmail.com>
	 <86aa493a0707310607m77c899ewdfb08a0ca988c427@mail.gmail.com>
	 <46AF3544.9030707@kippdata.de>
	 <86aa493a0707310818o7b915171pbc942b593c9ad9cd@mail.gmail.com>
	 <46AF55DD.8010005@kippdata.de>
	 <86aa493a0707310838m71c70062tf1db9a48a82ec5f7@mail.gmail.com>
	 <46B0A268.2070906@kippdata.de>
	 <86aa493a0708010820j42bfb20el1a82a8be9aa2e6cc@mail.gmail.com>
	 <46B0AF0F.1020008@kippdata.de>
	 <86aa493a0708011536y1e688654t5f5be17c24888d3@mail.gmail.com>

Rainer,

I setup a test httpd + loadbalancer with jk 1.2.24 and could reproduce
the problem over and over again. Then I patched the source and have
been unable to reproduce the problem with the patched mod_jk.so.

So the patch looks good.

Regards

Ben

On 8/1/07, ben short <jamin.short@gmail.com> wrote:
> I'll give it ago first thing tomorrow, well after a cup of tea :)
>
> On 8/1/07, Rainer Jung <rainer.jung@kippdata.de> wrote:
> > hi Ben,
> >
> > could you try the following patch for 1.2.24:
> >
> > http://people.apache.org/~rjung/mod_jk-dev/patches/fail-on-status.patch
> >
> > I guess you can build the module yourself (it's easy: configure
> > --with-apxs=PATHTOAPXS; make; make install). Now simply download the
> > source of 1.2.24 and use the patch command to add the above file as a
> > patch. Then build and retest. If you really can't build it yourself let
> > me know.
> >
> > The patch is not well tested, don't go straight to production with it :)
> >
> > Regards,
> >
> > Rainer
> >
> > ben short wrote:
> > > Sure for stable operation, but what if the machine reboots, tomcat
> > > starts up and your webapp doesn't for some reason. This situation
> > > could occur then.
> > >
> > > Many thanks for your help with this one.
> > >
> > > Regards
> > >
> > > Ben
> > >
> > > On 8/1/07, Rainer Jung <rainer.jung@kippdata.de> wrote:
> > >> Hi Ben,
> > >>
> > >> I think I understand the problem now, and it is a jk bug. For stable
> > >> operation you should really use the disable/stop feature. Nevertheless
> > >> I'm starting thinking about how to fix this in a good way.
> > >>
> > >> The bug has to do with the new "fail on status" feature you use. It is
> > >> not very old, so we didn't experience the bug before.
> > >>
> > >> Stay tuned ...
> > >>
> > >> Regards,
> > >>
> > >> Rainer
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
>

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org