[
https://issues.apache.org/jira/browse/AXIS2C-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2C-1005.
-------------------------------------
Fix Version/s: 2.0.0
(was: 1.7.0)
Resolution: Fixed
Dual channel clients (echo_blocking_dual, echo_non_blocking_dual) were
logging
spurious errors on successful operation:
"Extra content at the end of the document"
"SOAP message does not have a SOAP envelope element"
The root cause was the HTTP transport sender trying to parse the HTTP
response
as SOAP even in dual channel mode. In dual mode, the HTTP response is just a
202 ACK with no body - the actual SOAP response comes later on the callback
channel. Attempting to parse the empty ACK response as SOAP caused the
errors.
Fix by checking the AXIS2_USE_SEPARATE_LISTENER property before attempting
to
parse the response. If using a separate listener (dual channel), skip the
response parsing since the response will arrive on the callback channel.
> dual clients report an error in log
> -----------------------------------
>
> Key: AXIS2C-1005
> URL: https://issues.apache.org/jira/browse/AXIS2C-1005
> Project: Axis2-C
> Issue Type: Bug
> Components: xml/soap
> Reporter: Dinesh Weerapurage
> Priority: Major
> Fix For: 2.0.0
>
>
> Although echo_blocking_dual and echo_non_blocking_dual clients executes
> successfully , they dump following message into log.
> [Tue Feb 26 15:30:01 2008] [error] libxml2_reader_wrapper.c(945) Extra
> content at the end of the document
> -- SEVERITY_ERROR
> [Tue Feb 26 15:30:01 2008] [error] libxml2_reader_wrapper.c(456) error
> occured in reading xml stream
> [Tue Feb 26 15:30:01 2008] [critical] soap_builder.c(812) SOAP message does
> not have a SOAP envelope element
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
