The ability to exclude lines from the stacktrace is little known and extremely helpful, especially when using frameworks that use proxies and have deeply nested calls and exceptions.

We are using this feature with the configuration below in Spring Boot but we lose some information if the Exception originates in some of the framework code.

For example if the exception is thrown from "org.springframework.web.filter" the location of the problem is suppressed!

In ThrowableProxyConverter a single line change will improve this. I have made the change locally and provided a new junit test method in ThrowableProxyConverterTest.

If you are receptive to the change I will create a PR.

thank you,
Mark

<pattern>%-4relative [%thread] %-5level %logger{35} - %msg %n%ex{1000000,
    com.sun.proxy.,
    java.lang.reflect.,
    javax.servlet.,
    org.springframework.cglib.,
    org.springframework.aop.,
    org.springframework.transaction.interceptor.TransactionAspectSupport.,
    org.springframework.validation.beanvalidation.MethodValidationInterceptor.,
    org.springframework.boot.actuate.web.trace.,
    org.springframework.security.web.,
    org.springframework.boot.actuate.,
    org.springframework.web.servlet.,
    org.springframework.web.method.,
    org.springframework.web.filter.,
    org.apache.coyote.,
    org.apache.catalina.,
    org.apache.tomcat.,
    sun.reflect.}