axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Dmitriev (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5257) "Premature end of file encountered" when parsing empty response
Date Fri, 02 Mar 2012 08:47:13 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220777#comment-13220777
] 

Vadim Dmitriev commented on AXIS2-5257:
---------------------------------------

Remote side is accessible via SSL only, so I cannot dump network traffic direcly. Raw request/response
from SoapUI are attached. 

I debugged Axis response processing and schematically here is what happens:
1. HTTP headers are parsed;
2. Response length is determined (actually client failes to determine it, so it is left undefined);
3. XMLReader is created to parse reponse message, but server already closed the connection
(internally, weblogic stax implementation detects EOF on the first 'read' attempt).

I'm not that familiar with RFC2616, but it seems that XMLReader should not be created if connection
is closed after response headers are received, because it is perfectly valid server behavior.
As a side note - it causes XMLReader to throw parsing exception which shadows "error 400".
If server is doing wrong here, it may be useful for the end-user if Axis2 would throw something
like "transfer-coding and content-length cannot both be undefined".

P.S. If after these details you still insist it is a user issue, I will move the discussion
to the mailing list then.
                
> "Premature end of file encountered" when parsing empty response
> ---------------------------------------------------------------
>
>                 Key: AXIS2-5257
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5257
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.6.1
>         Environment: Oracle 1.6.0_31
> WebLogic 10.3.5
>            Reporter: Vadim Dmitriev
>         Attachments: dump.txt
>
>
> Server response:
> "HTTP/1.1 400 Bad Request
> Connection: close
> Date: Thu, 01 Mar 2012 14:12:07 GMT
> Server: Microsoft-IIS/6.0
> X-Powered-By: ASP.NET
> X-AspNet-Version: 2.0.50727
> Cache-Control: private
> Content-Type: text/html
> "
> Axis tries to parse response message body and XMLStreamReader fails with "premature end
of file". Is this Axis issue or is there a problem with servers response?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message