tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject RE: mod_jk release preparation: ready for test
Date Thu, 07 Dec 2006 19:17:21 GMT

> -----Original Message-----
> From: Remy Maucherat [] 
> Sent: Thursday, December 07, 2006 6:08 AM
> To: Tomcat Developers List
> Subject: Re: mod_jk release preparation: ready for test
> 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):

From Henri's logs, what happened is that mod_jk didn't see 0x4142 as the
first two bytes of the message, and so it dropped the connection to Tomcat.
Don't know how that could happen, but that is what his logs say :).

>      protected void flush()
>          throws IOException {
>          if (outputBuffer.position() > 0) {
>              if (Socket.sendbb(socket, 0, 
> outputBuffer.position()) < 0) {
>  >>                throw new IOException();
>              }
>              outputBuffer.clear();
>          }
>      }
> Rémy
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message