Re: Tried to remove Log4jServletFilter reference to avoid "GC overhead limit exceeded", but still happens

This appears to have been useful for people: http://stackoverflow.com/a/1393503/1446916 My guess would be that your application is creating objects in a tight loop somewhere. If you run the app with FlightRecorder you should be able to zoom in on where the allocation is taking place. See

Re: Tried to remove Log4jServletFilter reference to avoid "GC overhead limit exceeded", but still happens

I hope you realize that the Log4jServletFilter is probably not the culprit here. It is just a servlet filter in your filter chain. Ralph > On Sep 9, 2016, at 1:17 PM, KARR, DAVID wrote: > > At one point, I had changed my webapp's web.xml to reference the >

Re: Tried to remove Log4jServletFilter reference to avoid "GC overhead limit exceeded", but still happens

If you're using Servlet 3.x, the filter is automatically injected. If you don't want to use it, you can just remove the log4j-web dependency entirely. On 9 September 2016 at 15:17, KARR, DAVID wrote: > At one point, I had changed my webapp's web.xml to reference the >

Tried to remove Log4jServletFilter reference to avoid "GC overhead limit exceeded", but still happens

At one point, I had changed my webapp's web.xml to reference the "Log4jServletFilter", but I since decided I didn't need to use that, and I was also seeing my app dying with stacktraces like the following: -- org.apache.cxf.interceptor.Fault: GC overhead limit exceeded at