Error details propagation among proxies

Question

Hi all,
I've a question about how to propagate back error details from one proxy to another.
I've setup a simple alsb project:
- proxyA that calls proxyB
- proxyB a local proxy with only one stage where there is a 'raise error' action with a custom error code & message
In proxyB I've also added a service error handler only for tracing what error has been raised.
In proxyA I've also added a service error handler where I would like to catch error raised by proxyB and get details about the error raised by proxyB.
From log file I see:
####<Sep 11, 2007 1:04:31 PM CEST> <Error> < [null, null, null, ERROR] ERROR catched in proxyB: <fault xmlns="http://www.bea.com/wli/sb/context">
<errorCode>999</errorCode>
<reason>error in proxyB</reason>
<location>
<node>ProxyB-Pipeline</node>
<pipeline>ProxyB-Pipeline_request</pipeline>
<stage>stage1</stage>
<path>request-pipeline</path>
</location>
</fault>>
####<Sep 11, 2007 1:04:31 PM CEST> <Error> < [null, null, null, ERROR] ERROR catched in proxyA: <event-bus:fault xmlns:event-bus="http://www.bsource.ch/EventBus" xmlns="http://www.bea.com/wli/sb/context" xmlns:con="http://www.bea.com/wli/sb/stages/transform/config">
<event-bus:fault>
<errorCode>BEA-382502</errorCode>
<reason>ALSB Service Callout action received an error response</reason>
<details>
<con:ErrorResponseDetail/> // I'm wondering how to get here details about the error raised by proxyB
</details>
<location>
<node>ProxyA-Pipeline</node>
<pipeline>ProxyA-Pipeline_request</pipeline>
<stage>callout to ProxyB</stage>
<path>request-pipeline</path>
</location>
</event-bus:fault>
<event-bus:body>
<test xmlns="">ciao</test>
</event-bus:body>
</event-bus:fault>>
Do you have any idea?
Thanks in advance
ferp

Answer 1

We filed a CR to address the soap fault propagation from one proxy to another and we got confirmation from engineering that it is work as designed. As a workaround, if you want to get the actual cause, you need to get that from fault (by replacing the body with fault in the error handler of proxy A).
For eg. In your process A error handler, you can do the following.
Replace [ node contents ] of [ . ] in [ body ] with [ $fault ]
and you will get the following output.
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382502</con:errorCode>
     <con:reason>
     ALSB Service Callout action received an error response
     </con:reason>
     <con:details>
     <con1:ErrorResponseDetail
xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
     <con1:detail>
     <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382515</con:errorCode>
     <con:reason>[ALSB Transform:382515]Callout to java method "public
static void com.bea.test.TestJavaCallout.throwException() throws
java.lang.Exception" resulted in exception: Exception raised
here........:</con:reason>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>Java Callout</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
     </con1:detail>
     </con1:ErrorResponseDetail>
     </con:details>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>stage1</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
The actual fault will be wrapped into the con1:detail. Hope this helps.
Thanks,
Muthu.