Hi, I attach the ajp log for two cases: one ok and one ko.
http://www.nabble.com/file/p20971586/headers_ok_and_ko.txt headers_ok_and_ko.txt I'm going crazy in order to understand when tomcat lost headers... :( Many thanks, regards Marco marcobalc wrote: > > Hi, > > an other strange behavior is that some times when I reboot tomcat and I > refresh browser while I wait that tomcat is up and runnig I see the > "normal" error page displayed when the tomcat is not yet started but also > in this case I see the source html code on the browser instead of HTML > interpreted. > > This is the source the was displayed > > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>200 OK</title> > </head><body> > <h1>OK</h1> > <p>The server is temporarily unable to service your > request due to maintenance downtime or capacity > problems. Please try again later.</p> > </body></html> > > and the response header visible on firefox > > Date: Thu, 11 Dec 2008 15:58:32 GMT > Server: Apache/2.2.9 (Unix) mod_jk/1.2.27 > Keep-Alive: timeout=5, max=100 > Connection: Keep-Alive > Transfer-Encoding: chunked > Content-Type: text/plain > > 200 OK > > best regards, > Marco > > > > Rainer Jung-3 wrote: >> >> Hi Marco, >> >> marcobalc schrieb: >>> Hi, >>> >>> now I have the stacktrace but the problem is that the stack do not >>> involve >>> my classes :| >>> >>> java.lang.Throwable: Stack Info >>> at org.apache.jk.core.MsgContext.action(MsgContext.java:263) >>> at org.apache.coyote.Response.action(Response.java:183) >>> at org.apache.coyote.Response.sendHeaders(Response.java:380) >>> at >>> org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:305) >>> at >>> org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) >>> at >>> org.apache.catalina.connector.Response.finishResponse(Response.java:492) >>> at >>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:310) >>> at >>> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190) >>> at >>> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283) >>> at >>> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767) >>> at >>> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) >>> at >>> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) >>> at >>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690) >>> at java.lang.Thread.run(Thread.java:619) >>> >>> Any idea? i'm going crazy on this problem :( >> >> Could you please post a more complete part of the log file, when used >> with the increased log level I posted to you earlier in this thread. >> With the more complete log we will have timestamps, and we can also see >> the second commit etc. >> >> Regards, >> >> Rainer >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> > > -- View this message in context: http://www.nabble.com/bad-content-type-mod_jk-1.2.27-tp20892496p20971586.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org