How to hide log message "SAAJ0303" for component tESBProviderFault?

One Star

How to hide log message "SAAJ0303" for component tESBProviderFault?

During execution of an integration job with the component tESBProviderFault (Talend ESB 5.3.1) a log message appears on the console output:
 PhaseInterceptorChain          WARN  Application {}myTransferSvc#{}retrieveFiles has thrown exception, unwinding now
org.apache.cxf.binding.soap.SoapFault: Error
at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(
at org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(
at org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(
at org.apache.cxf.service.invoker.AbstractInvoker.invoke(
at org.apache.cxf.interceptor.ServiceInvokerInterceptor$
at java.util.concurrent.Executors$ Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at Source)
at org.apache.cxf.workqueue.SynchronousExecutor.execute(
at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(
at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(
at org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(
at org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(
at org.eclipse.jetty.server.AbstractHttpConnection.content(
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(
at org.eclipse.jetty.http.HttpParser.parseNext(
at org.eclipse.jetty.http.HttpParser.parseAvailable(
at org.eclipse.jetty.server.AsyncHttpConnection.handle(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$
at Source)
Jul 02, 2013 3:54:33 PM com.sun.xml.internal.messaging.saaj.soap.ver1_1.Fault1_1Impl getFaultSubcodes
SEVERE: SAAJ0303: Operation getFaultSubcodes not supported by SOAP 1.1

A short research in the internet has produced the following results:
A similar exeception message (with »getFault« instead of »getFaultSubcodes«) was handled with issue TESB-5894. In the web article JAX-WS: Throwing generic SOAPFaults under WLS 10.3 a solution is described, where the initialization of the SOAPFactory object has to be changed to avoid the exception.

Is there a simple solution to prevent the logging of this message to the system console?

Community Manager

Re: How to hide log message "SAAJ0303" for component tESBProviderFault?

Hi Sebastian
Please reopen TESB-5894 or report a new issue for this problem, the error message as showed in issue TESB-5894 is still printed on the console. Now, you can use a component called tRedirectOutput to redirect the error message to a log file, for more information, see this topic:
Talend | Data Agility for Modern Business
One Star

Re: How to hide log message "SAAJ0303" for component tESBProviderFault?

Hello All,
We have the same problem with Talend 5.3.1. The component tESBProviderFault gives a fault message back to the caller when the job runs local but when this job is deployed in Talend Runtime afterwards nothing is send to the caller anymore. That is very evil to send nothing back.
How can we avoid the exception be thrown of tESBProviderFault?
Kind Regards
Four Stars

Re: How to hide log message "SAAJ0303" for component tESBProviderFault?
This may help to redirect talend console output to file...
One Star

Re: How to hide log message "SAAJ0303" for component tESBProviderFault?

Hello sanvaibhav,
Thank you for this hint. But we don't need one more log file with the console output. We try to avoid this exception so the component tESBProviderFault works properly and returns a fault message to the Web Service Caller.
We need a way to rectify this misbehavior of tESBProviderFault.
Kind Regards


Talend named a Leader.

Get your copy


Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

An API-First Approach to Modernizing Applications

Learn how to use an API-First Approach to Modernize your Applications

Watch Now

Talend API Designer – Technical Overview

Take a look at this technical overview video of Talend API Designer

Watch Now

Getting Started with APIs

Find out how to get started with APIs