Hi!
Running current trunk + Nio connector + JDK 7u7, I see a lot of the
following exceptions.
It looks like there is some bug in AccessLogValve optimization when
StringBuilder was replaced with a CharBuffer.
A CharBuffer cannot grow itself?
02-Oct-2012 22:17:29.000 SEVERE [http-nio-8080-exec-2]
org.apache.coyote.http11.AbstractHttp11Processor.process Error
processing request
java.nio.BufferOverflowException
at java.nio.Buffer.nextPutIndex(Buffer.java:513)
at java.nio.HeapCharBuffer.put(HeapCharBuffer.java:163)
at java.nio.CharBuffer.put(CharBuffer.java:892)
at java.nio.CharBuffer.put(CharBuffer.java:915)
at java.nio.CharBuffer.append(CharBuffer.java:1311)
at
org.apache.catalina.valves.AccessLogValve$RequestElement.addElement(AccessLogValve.java:1577)
at
org.apache.catalina.valves.AccessLogValve.log(AccessLogValve.java:944)
at
org.apache.catalina.core.AccessLogAdapter.log(AccessLogAdapter.java:51)
at
org.apache.catalina.core.ContainerBase.logAccess(ContainerBase.java:1043)
at
org.apache.catalina.core.ContainerBase.logAccess(ContainerBase.java:1050)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:480)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:963)
at
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:234)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:617)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1568)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
