You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Abhijeet Shinde (JIRA)" <ji...@apache.org> on 2005/06/30 08:51:57 UTC
[jira] Created: (AXIS2-54) Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC)
Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC)
-------------------------------------------------------------------------------------
Key: AXIS2-54
URL: http://issues.apache.org/jira/browse/AXIS2-54
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: transports
Environment: Tomcat 5, SOLARIS SPARC
Reporter: Abhijeet Shinde
Priority: Critical
After analysing the Axis code, we found the problem lies with the Content-Length not set by the Aapache AXIS. The code in the AxisServlet is not setting the Content-Length and thats the reason the Client is not able to read the response properly.
The client waits till the timeout is reached during reading the response (byte-by-byte).
Also the Axis has another bug, where the getContentLength() method in org.apache.axis.Message returns the wrong Content-Length. On debugging I found that the response contains the <?xml version="1.0" encoding="UTF-8"?> declaration followed by the soap message, but the Content-Length returned was only that of the soap message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS-2108) Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC)
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2108?page=all ]
Davanum Srinivas resolved AXIS-2108:
------------------------------------
Resolution: Invalid
Use commons httpsender on the client. automatically uses HTTP1.1 which does not need content-length.
-- dims
> Client not able to read the response sent by Axis on Tomcat (platform: Solaris SPARC)
> -------------------------------------------------------------------------------------
>
> Key: AXIS-2108
> URL: http://issues.apache.org/jira/browse/AXIS-2108
> Project: Apache Axis
> Type: Bug
> Components: Basic Architecture
> Environment: Tomcat 5, SOLARIS SPARC
> Reporter: Abhijeet Shinde
> Priority: Critical
>
> After analysing the Axis code, we found the problem lies with the Content-Length not set by the Aapache AXIS. The code in the AxisServlet is not setting the Content-Length and thats the reason the Client is not able to read the response properly.
> The client waits till the timeout is reached during reading the response (byte-by-byte).
> Also the Axis has another bug, where the getContentLength() method in org.apache.axis.Message returns the wrong Content-Length. On debugging I found that the response contains the <?xml version="1.0" encoding="UTF-8"?> declaration followed by the soap message, but the Content-Length returned was only that of the soap message.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira