Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of henri.gomez@gmail.com
 designates 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=KQgfIZcrGTZenoBTU/z8xle7yDaBQMb2si1HK5Su+BdAmQROX8doyO+8dVFoRMz6OLgW+pKlDbPliI97EOZJrtug6XV3VgNcUrV0CXIRL3tiZdftYiGMnzZTnpOu0Dh/I31hJO7su8RjNAkrM8Yb1qiajAzv3OX8POr+qE66BMM=
Message-ID: <6291fc850612070637h3e4c0256wb2983401cf51db16@mail.gmail.com>
Date: Thu, 7 Dec 2006 15:37:29 +0100
From: "Henri Gomez" <henri.gomez@gmail.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: mod_jk release preparation: ready for test
In-Reply-To: <6291fc850612070635l70f27b18mfe8dec1ba148e394@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <457743A2.2010806@apache.org>
	 <6291fc850612070322u7f2e57ccy137447bc1363fa9f@mail.gmail.com>
	 <457800C0.3040803@apache.org>
	 <6291fc850612070359w5085890co2fff91378202ec64@mail.gmail.com>
	 <45780326.3070205@apache.org>
	 <6291fc850612070530m5ab5761en2acd9fd1d43a8901@mail.gmail.com>
	 <45781B89.7080700@apache.org>
	 <6291fc850612070555s2f79577ag1cbdd4fab4cf92f4@mail.gmail.com>
	 <45782025.3030907@apache.org>
	 <6291fc850612070635l70f27b18mfe8dec1ba148e394@mail.gmail.com>

it works well even when your servlet is pushing PDF data ?

Did a tcpdump/ethereal could help you ?

>2006/12/7, Henri Gomez <henri.gomez@gmail.com>:
> In which project / class ?
>
>
>
> 2006/12/7, Remy Maucherat <remm@apache.org>:
> > Henri Gomez wrote:
> > > it's a seems to be a tomcat-native (1.1.7) problem
> > >
> > > And since we discuss Tomcat 6.0.4 release, should we consider that
> > > error as a show stopper ?
> >
> > No. It existed before, and it is not known if it's a problem with the
> > Java code or not.
> >
> > What I see is that there's an IO exception here, so it means the send
> > call returned a status error (or maybe it returned one of these
> > mysterious codes which are an error but are not actually an error):
> >      protected void flush()
> >          throws IOException {
> >          if (outputBuffer.position() > 0) {
> >              if (Socket.sendbb(socket, 0, outputBuffer.position()) < 0)=
 {
> >  >>                throw new IOException();
> >              }
> >              outputBuffer.clear();
> >          }
> >      }
> >
> > R=E9my
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org