ALSB 2.6 Problems With WebServices When Responses are Sent Using HTTP 1.0
(Doc ID 1209123.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle Service Bus - Version 2.6 to 2.6.1RP [Release Aqualogic Service Bus]Information in this document applies to any platform.
Symptoms
While calling an external web service from ALSB, some of the responses fail with the below exception even though correct response (Soap Envelop-XML) is sent from external web service to ALSB.
[ALSB Tracing] Entering error handler of route node RouteToContactsBusinessService with message context: [MessageContextImpl
attachments="<con:attachments
xmlns:con="http://www.bea.com/wli/sb/context"/>"
fault="<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382030</con:errorCode>
<con:reason>Failure while unmarshalling message: Failed to parse XML
text</con:reason>
<con:location>
<con:node>RouteToContactsBusinessService</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>"
The only way to see the response XML is either collect tcpdump or collect the response through tcpmon or some other utility to trace the network traffic.
The issue occurs only when the response message type is chunked. For content-length message type the issue won't occur.
Sample Chunked response:
X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
Set-Cookie: JSESSIONID=6DD16003D6FF04632CCDD12349D42BF3; Path=/
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/xml;charset=UTF-8
19a
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header/><env:Body><ns1:orderMailoutResponse xmlns:ns1='http://org.jboss.ws/samples/docstyle/bare/types' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><mailoutId>100084021</mailoutId><responseCode>0</responseCode><responseMessage>Request written to SAP queue.</responseMessage></ns1:orderMailoutResponse></env:Body></env:Envelope>
0
In the above sample chunked response the highlighted "19a" and "0" tells the response is chunked. For Content-length response type, the http header should have a content-length parameter with the size of the payload.
For eg.
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
User-Agent: Java1.5.0_17
Host: localhost
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: Keep-Alive
Content-Length: 1591
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |