You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 18, 2026. It is now read-only.
I'm currently dealing with some Java applications that spew some uncommon error messages at the beginning of its stacktrace.
Here's an example:
2020-11-09 10:50:20,714 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-156) Interceptor for {http://impl.webservices.example.com/}numeracaoUnicaWS#{http://impl.webservices.example.com/}existeNumeroUnico has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message.
at org.apache.cxf@3.3.3//org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:67)
at org.apache.cxf@3.3.3//org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at org.apache.cxf@3.3.3//org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
at org.apache.cxf@3.3.3//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:441)
at org.apache.cxf@3.3.3//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:356)
at org.apache.cxf@3.3.3//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:314)
at org.apache.cxf.impl//org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at org.apache.cxf.impl//org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
...
Because it fails to match any of the hardcoded regular expressions, the plugin fails to group subsequent lines from the log.
Since it is not possible to predict how every application handles the output of a stacktrace, it would be an interesting addition to the plugin the ability to define custom regular expressions to further detect these uncommon cases.
I'm currently dealing with some Java applications that spew some uncommon error messages at the beginning of its stacktrace.
Here's an example:
Because it fails to match any of the hardcoded regular expressions, the plugin fails to group subsequent lines from the log.
Since it is not possible to predict how every application handles the output of a stacktrace, it would be an interesting addition to the plugin the ability to define custom regular expressions to further detect these uncommon cases.