I had that problem with 4.1.16 and I opened a bug in bugzilla. But I couldn't come up with a test case and the bug got closed. Maybe you can add your experience to the bug report and reopen it: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15251
Aymeric. >>> [EMAIL PROTECTED] 12/18/02 02:14PM >>> > > 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. The problem is still there for both 4.1.12 and 4.1.17, it's just not very visible up front on x.12 And monitoring the logs for that context tells me my pages start returning blank at the exact same time that exception happens. > I have not seen any sort of socket exception, but possibly my > logging is not > configured to see that. Perhaps try to add a log file dump for that specific context as I did in my little context blurb. Then check that file out after your pages start returning blank pages. Then perhaps it will be a little more filtered from the rest of the context serving... Luc -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
