tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Preißer <>
Subject RE: BufferOverflowException in AjpNioProcessor
Date Thu, 17 Jan 2013 13:51:30 GMT

> -----Original Message-----
> From: Mark Thomas []
> Sent: Thursday, January 17, 2013 1:11 PM
> On 17/01/2013 11:07, Steve Mactaggart wrote:
> > Hi All,
> >
> > I have been hunting a BufferOverflowException on our production system
> > the last while, and initially thought this was resolved by issue 53119,
> > 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.

Yes, I got these BufferOverflowExceptions when switching from AJP-APR to
I added a comment to the bug for the AJP-APR connector:


> The two possibilities at this point are:
> a) Tomcat bug
> b) Application bug
> b would be caused by something (e.g. servlet, filter) retaining a
> reference to a request and using it after the request had finished
> processing.
> If you set the following system property:
> org.apache.catalina.connector.RECYCLE_FACADES
> to true (e.g. in setenv.[bat|sh]) and your application is retaining
> references you should start to see NPEs and the stack trace should point
> to where the problem is.
> If you still see BufferOverflowException with that setting in place then
> that would make a Tomcat bug more likely.

I'm certain that my applications don't retain references to request objects,
but I will also try your suggestion with setting the RECYCLE_FACADES
property and switching back to the AJP-NIO connector, to see if these
BufferOverflowExceptions still occur.


Konstantin Preißer

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message