Hi All, I have been hunting a BufferOverflowException on our production system for the last while, and initially thought this was resolved by issue 53119, we have subsequently upgraded to 7.0.32 and have still seen the issues.
Reading through the mailing list archive it seems I am not the only one having issues with the NIO AJP Processor. http://www.mailinglistarchive.com/html/users@tomcat.apache.org/2012-10/msg00477.html Below is what we are seeing pretty regularly in our production environment. This is probably load based, as we don't seem to see this in any of our development environments. Caused by: java.nio.BufferOverflowException at java.nio.HeapByteBuffer.put(HeapByteBuffer.java:183) at org.apache.coyote.ajp.AjpNioProcessor.output(AjpNioProcessor.java:281) at org.apache.coyote.ajp.AbstractAjpProcessor$SocketOutputBuffer.doWrite(AbstractAjpProcessor.java:1122) at org.apache.coyote.Response.doWrite(Response.java:504) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:383) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:342) at org.apache.tomcat.util.buf.IntermediateOutputStream.write(C2BConverter.java:278) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207) at org.apache.tomcat.util.buf.WriteConvertor.write(C2BConverter.java:242) at java.io.BufferedWriter.write(BufferedWriter.java:188) at org.apache.tomcat.util.buf.C2BConverter.convert(C2BConverter.java:125) at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:476) at org.apache.catalina.connector.CoyoteWriter.write(CoyoteWriter.java:152) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:119) at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:336) at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:353) at ... 72 more As mentioned in the mailing list, could this be an issue that just needs to be re-applied to the nio version of the Processor from the original issue I thought this was? I don't really know why this is happening, so can't provide a test case but do know this is happening pretty regularly. Steve
