Friday, April 29, 2011

This is the most irritating exception I encountered in my experience.

You will get the following SOAP Message in log files

<env:Envelope xmlns:env="http//schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>oracle.fabric.common.FabricInvocationException</faultstring>
<faultactor/>
<detail>
<exception>null</exception>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>

This will happen when there is an empty  detail tag in the SOAP Fault message

There is no single solution to this. As this indicates something wrong at the underlying SOAP stack, you can enable detailed logging to find out the cause for this issue. 

The following are few of the scenario’s from my experience. Please comment if you have more.

1. WS-Addressing elements sent in the request by web services stack and service provider rejected the request message.(check my post Here to suppress these headers)

2. SSL Handshake errors . Enable SSL debug when starting server to get the detailed SSL log.

-Djavax.net.debug=all

3.  more ……

0 comments :

Post a Comment