+++ This bug was initially created as a clone of Bug #845165 +++

Created attachment 601863 [details]
reproducer app

Description of problem:

When a pipeline includes a SOAPProcessor action which calls a Web Service, if the wrapped web service returns a soap fault, and HTTP response code 500, the HTTP Provider Gateway returns a response code 200 to an ESB Client, instead of the expected 500 response.

This seems contrary to the WS-I 1.0 Basic Profile specification, and breaks some Spring WS Clients.

This issue does not happen with a JBR-Provider using the HTTP protocol. The expected 500 response code is returned by it.

Version-Release number of selected component (if applicable):

ESB 4.11

How reproducible:

You can use the attached project to reproduce the issue.

Steps to Reproduce:

1. Replace the 'webservice_producer' quickstart in SOA-P 5.2 samples/quickstart directory with the one attached.

2. Run 'ant clean deploy' to deploy it to a running instance

3. Run 'ant runtest' to send a WS Request to the HTTP Provider gateway.

  
Actual results:

runtest:
[echo] Http Client
[java] Request payload:
[java] <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:good="http://webservice_producer/goodbyeworld">
[java] <soapenv:Header/>
[java] <soapenv:Body>
[java] <good:sayGoodbye>
[java] <message>goodbye</message>
[java] </good:sayGoodbye>
[java] </soapenv:Body>
[java] </soapenv:Envelope>
[java] --------------------------
[java]
[java] 16:30:38,927 DEBUG [main][header] >> "POST /Quickstart_webservice_producer/http/test/x HTTP/1.1[\r][\n]"
[java] 16:30:38,970 DEBUG [main][header] >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "Host: localhost:8080[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "Content-Length: 292[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "[\r][\n]"
[java] 16:30:38,973 DEBUG [main][content] >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:good="http://webservice_producer/goodbyeworld">[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <soapenv:Header/>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <soapenv:Body>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <good:sayGoodbye>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <message>goodbye</message>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> " </good:sayGoodbye>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> " </soapenv:Body>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> "</soapenv:Envelope>"
[java] 16:30:39,265 DEBUG [main][header] << "HTTP/1.1 200 OK[\r][\n]"
[java] 16:30:39,266 DEBUG [main][header] << "HTTP/1.1 200 OK[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "Server: Apache-Coyote/1.1[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "asyncServiceInvoke: false[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "Content-Length: 298[\r][\n]"
[java] 16:30:39,268 DEBUG [main][header] << "Date: Mon, 30 Jul 2012 06:30:39 GMT[\r][\n]"
[java] 16:30:39,268 DEBUG [main][header] << "[\r][\n]"
[java] 16:30:39,273 DEBUG [main][content] << "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>app exception!</faultstring><detail><ns1:AppException xmlns:ns1="http://webservice_producer/goodbyeworld" /></detail"
[java] 16:30:39,273 DEBUG [main][content] << "></soap:Fault></soap:Body></soap:Envelope>"
[java]
[java] Response Status Code: 200
[java] Response payload:
[java] <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>app exception!</faultstring><detail><ns1:AppException xmlns:ns1="http://webservice_producer/goodbyeworld" /></detail></soap:Fault></soap:Body></soap:Envelope>
[java] --------------------------
[java]


Expected results:

runtest:
[echo] Http Client
[java] Request payload:
[java] <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:good="http://webservice_producer/goodbyeworld">
[java] <soapenv:Header/>
[java] <soapenv:Body>
[java] <good:sayGoodbye>
[java] <message>goodbye</message>
[java] </good:sayGoodbye>
[java] </soapenv:Body>
[java] </soapenv:Envelope>
[java] --------------------------
[java]
[java] 16:30:38,927 DEBUG [main][header] >> "POST /Quickstart_webservice_producer/http/test/x HTTP/1.1[\r][\n]"
[java] 16:30:38,970 DEBUG [main][header] >> "Content-Type: text/xml;charset=UTF-8[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "User-Agent: Jakarta Commons-HttpClient/3.1[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "Host: localhost:8080[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "Content-Length: 292[\r][\n]"
[java] 16:30:38,973 DEBUG [main][header] >> "[\r][\n]"
[java] 16:30:38,973 DEBUG [main][content] >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:good="http://webservice_producer/goodbyeworld">[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <soapenv:Header/>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <soapenv:Body>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <good:sayGoodbye>[\n]"
[java] 16:30:38,973 DEBUG [main][content] >> " <message>goodbye</message>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> " </good:sayGoodbye>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> " </soapenv:Body>[\n]"
[java] 16:30:38,974 DEBUG [main][content] >> "</soapenv:Envelope>"
[java] 16:30:39,265 DEBUG [main][header] << "HTTP/1.1 500 Error[\r][\n]"
[java] 16:30:39,266 DEBUG [main][header] << "HTTP/1.1 500 Error[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "Server: Apache-Coyote/1.1[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "asyncServiceInvoke: false[\r][\n]"
[java] 16:30:39,267 DEBUG [main][header] << "Content-Length: 298[\r][\n]"
[java] 16:30:39,268 DEBUG [main][header] << "Date: Mon, 30 Jul 2012 06:30:39 GMT[\r][\n]"
[java] 16:30:39,268 DEBUG [main][header] << "[\r][\n]"
[java] 16:30:39,273 DEBUG [main][content] << "<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>app exception!</faultstring><detail><ns1:AppException xmlns:ns1="http://webservice_producer/goodbyeworld" /></detail"
[java] 16:30:39,273 DEBUG [main][content] << "></soap:Fault></soap:Body></soap:Envelope>"
[java]
[java] Response Status Code: 500
[java] Response payload:
[java] <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><soap:Fault><faultcode>soap:Server</faultcode><faultstring>app exception!</faultstring><detail><ns1:AppException xmlns:ns1="http://webservice_producer/goodbyeworld" /></detail></soap:Fault></soap:Body></soap:Envelope>
[java] --------------------------
[java]

Additional info:

--- Additional comment from JBoss JIRA Server on 2012-08-28 01:39:14 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

This issue should have been addressed as part of JBESB-2511.

--- Additional comment from JBoss JIRA Server on 2012-08-28 03:18:17 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

Attached a patch for this issue. I've verified it by running the existing unit and integration tests. We need a QA test to verify this fix itself.

--- Additional comment from JBoss JIRA Server on 2012-08-28 03:18:57 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

Attached a patch (JBESB-3838.patch) for this issue. I've verified it by running the existing unit and integration tests. We need a QA test to verify this fix itself.

--- Additional comment from JBoss JIRA Server on 2012-08-28 03:19:26 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

Attached a patch (JBESB-3838.patch) for this issue. I've verified it by running all the existing unit and integration tests. We need a QA test to verify this fix itself.

--- Additional comment from JBoss JIRA Server on 2012-08-28 04:45:12 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

Attached a recompiled jar (jbossesb-soap.jar) with the patch against the latest JBESB_4_11_CP branch (rev. 38166).
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_11_CP/product/

--- Additional comment from JBoss JIRA Server on 2012-08-28 05:41:26 EDT ---

Lucie Fabrikova <lfabriko> made a comment on jira JBESB-3838

I verified the problem on version SOA-P 5.3.0 GA, the patched version with reproducer generated status code 500.
Now we modify our test to reproduce the problem (add HTTP Provider).

--- Additional comment from JBoss JIRA Server on 2012-08-29 10:05:08 EDT ---

Lucie Fabrikova <lfabriko> made a comment on jira JBESB-3838

If the webservice works properly and returns correct result and there is no need to return fault code (500), the patch is not working, it returns response code 0. It should return 200.

--- Additional comment from JBoss JIRA Server on 2012-08-30 04:13:24 EDT ---

Sato Tadayoshi <tadayosi> made a comment on jira JBESB-3838

Thanks Lucie for your feedback! While a quick fix to my patch is easy, I am wondering if I should rather fix Http Gateway (HttpMessageComposer) instead of SOAPProcessor, because  SOAPProcessor + JBR Gateway doesn't observe this issue. My previous patch was for SOAPProcessor.

--- Additional comment from JBoss JIRA Server on 2012-08-30 08:16:56 EDT ---

Jiri Sedlacek <jsedlace> made a comment on jira JBESB-3838

Hi Sato, 

we have new information for you. We tested with JBoss WS Native stack by mistake and that's the reason why we found the problem mentioned by Lucie. 

If JBoss WS CXF Stack is used, your patch returns proper codes both for OK(200) and server error(500), we will have to cover other possible response codes in our tests too. 

If JBoss WS Native Stack is used, the method call at line 212 cause the problem:

requestHandler.handleHttpRequest(endpoint, servletRequest, servletResponse, servletContext) ;

JBossWS Native implementation of this sets servlet response code in servletReponse object to 0 when call of WS was successful. Without your patch, in org.jboss.soa.esb.listeners.gateway.http.HttpMessageComposer.decompose(...) method, there is always used status 200 OK, response is not attached to message. With your patch, there is properly propagated reponseStatus into message, if there is fault in WS, status is 500 (which is desirable), but if WS is called without fault, status code is 0. 

My conclusion - the patch can be used as is now if JBossWS native stack problem will be fixed or a condition to check the status code when JBossWS native is used can be placed somewhere (into SOAPProcessor or HTTPMessageComposer?)  and fix it.

--- Additional comment from JBoss JIRA Server on 2012-09-04 02:08:35 EDT ---

Magesh Bojan <mageshbk> made a comment on jira JBESB-3838

Done At revision: 38168

Sato, I completely took a different approach for setting the status. Please have a look at the commit and let me know.

--- Additional comment from JBoss JIRA Server on 2012-09-04 02:42:50 EDT ---

Magesh Bojan <mageshbk> made a comment on jira JBESB-3838

At revision: 38169 for the JBossWS Native fix.

--- Additional comment from Tadayoshi Sato on 2012-09-05 04:06:11 EDT ---

Created attachment 609887 [details]
untested patch built against JBESB_4_11_CP (rev.38169)

Hi Jiri and Lucie,

this (jbossesb-rosetta.jar) is the revised patch. Could you please test it again? We took a different approach from the previous one, so before applying it you have to rollback the previous one (jbossesb-soap.jar).

To apply this patch, replace the following jar with this patch:
$JBOSS_AS/server/$CONFIG/deployers/esb.deployer/lib/jbossesb-rosetta.jar

Thanks.

--- Additional comment from Jiri Sedlacek on 2012-09-11 03:00:29 EDT ---

Hi Tadayoshi, 

Lucie tested provided patched jboss-rosetta.jar and our tests passed, I checked diffs of fixes and it looks ok so We agree with the patch.

--- Additional comment from JBoss JIRA Server on 2012-09-13 08:06:01 EDT ---

Magesh Bojan <mageshbk> updated the status of jira JBESB-3838 to Closed

--- Additional comment from Lucie Fabrikova on 2012-11-21 04:07:26 EST ---

Verified in SOA-P 5.3.1 ER1.