Invalid http response: HTTP/1.1 200

Question

Hi gurus!
I have a problem with an asynchronous interface.
We are calling a Webservice which we don't need any response. In sxmb_moni it's OK, but in our RWB we see it as failed, with this entry:  invalid http response: HTTP/1.1 200.
I have search in logs, and in defaultTrace_00.0.trc we can see the following entry:
Marked transaction for rollback for meesage 4b4ed19f-bbe6-0062-e100-8000ac1f041d(INBOUND). Reason: java.io.IOException: invalid http response: HTTP/1.1 200
We have captured the HTTP header response, and is:
HTTP/1.1 200
Date: Thu, 14 Jan 2010 10:26:03 CET
Server: Mule/1.2
Connection: close
Expires: Thu, 14 Jan 2010 10:26:03 CET
Content-Type: text/xml
Content-Length: 508
X-MULE_CORRELATION_ID: d595447a-00ee-11df-a6a5-becd407b7daa
X-MULE_CORRELATION_GROUP_SIZE: 3
X-MULE_CORRELATION_SEQUENCE: -1
Could it be problem of the X-MULE_CORRELATION headers? Or Maybe PI needs an HTTP/1.1 200 OK?
Thak you!!!!

Answer 1

Hi Ignasi,
I personally donu2019t think you will have much luck getting XI to accept this response since itu2019s not an XI issue.  Itu2019s true that the client (XI in this case) is not required to examine or display the reason-phrase, but that statement doesnu2019t negate the requirement on the server to provide it.  The client has the option to look at it or not, but the server must still provide it either way.
I didn't notice the http header before, but the server you are connecting to is actually Mule version 1.2.  This release dates back to 2005.  I ran a quick test and reproduced the issue using Mule 1.2 (hello-http sample).  This may not be the same exact issue, but I did observe the same issue with the missing reason-phrase.  The issue is fixed in the Mule 1.3 release.
Perhaps they can request a patch for 1.2.  This may not be possible since they are working on the Mule 3.0 version now, but I really donu2019t know.  Itu2019s literally one line of code.   I made one small change and was able to get the hello-http sample working (code is open source):
Class: org.mule.providers.http.transformers.UMOMessageToHttpResponse
From this:
httpMessage.append(status).append(HttpConstants.CRLF);
To this:
httpMessage.append(status).append(" ").append(org.apache.commons.httpclient.HttpStatus.getStatusText(status)).append(HttpConstants.CRLF);
org.apache.commons.httpclient.HttpStatus.getStatusText is the method they are using in 1.3 to resolve the reason-phrase using the status code.
Thanks,
-Russ