Great! Now what do I do with these classes? And is this problem the same thing I am having in the "Tomcat 4.1.x and SocketException" thread???
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, December 19, 2002 8:56 AM > To: Tomcat Users List > Subject: Re: 4.1.17 Problems - Possibly Coyote Connector? > > > This is bug in 4.1.17 which will fixed in Tomcat 4.1.18, > > i attach the compiled classes that fixe it. > > update the tomcat-coyote and it should work... > > > On Thursday 19 December 2002 14:33, you wrote: > > * Luc Foisy <[EMAIL PROTECTED]> [1214 20:14]: > > > > > The actual web application did not seem to have a problem on > > > > > the front side. Everything went on as normal on 4.1.12 > > > > > Pages failed to be served correctly on 4.1.17 ( they are > > > > > blank ) though logging on with a new session will serve the > > > > > first couple pages then start blanking. > > > > > > > > This looks like exactly what is happening to me. 4.1.12 > > > > works, 4.1.17 gives me the problem. One thing to note is that my > > > > application does not use JSP so must be a catalina or > coyote issue. Are > > > > you using the stock Coyote/HTTP 1.1 connector or are > you using one of > > > > the JK connectors? > > > > > > I am using whatever 4.1.x is set to use by default. Which > I am pretty > > > sure is the Coyote/HTTP 1.1 connectors. > > > > This might be a dumb question, but have you tried using the > older http/1.1 > > connectors to see if the problem goes away? At least then > you know it's > > Coyote's fault. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
