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

Sagara Gunathunga  commented on AXIS2-5257:
-------------------------------------------

Since we all can have our own POV I'm happily accept your idea but still  this 
seems a user issue to me :)  and with initial details we can't  get any clue 
too.

Could you mention your outcome when invoking SoapUI ? Also you can place TCPMon 
middle of the Axis2 to your server communication and try to capture messages on 
wire.

With above steps you can determine where is the exact error whether in server 
side or client side. If you get successful response with SoapUI please attach 
it here.   
                
> "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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to