File getting truncated in WS response when tried bigger file
------------------------------------------------------------

                 Key: AXIS2-4830
                 URL: https://issues.apache.org/jira/browse/AXIS2-4830
             Project: Axis2
          Issue Type: Bug
          Components: client-api
    Affects Versions: 1.4
         Environment: Windows XP
            Reporter: Sunil


I have a web service client (Axis2) which is calling an external web service 
with one of the parameter as PDF file.
while invoking this service with a file size around 20 kb, everything works 
perfectly fine and returns back the updated PDF file.
The moment I use the bigger file (400kb), I get the incomplete response (pdf 
file content are getting truncated). 
I observed the log and once this message comes "Resorting to protocol version 
default close connection policy" I don't get any response.
In case of small file I get this message after getting complete response. But 
with the bigger file this message comes in between and results into problems. 
I am not sure that issue is related with the above message but looks like some 
timeout is happening.

Please help to receive the complete message. I also tried increasing Client 
Timeout/Socket Timeout in Axis Client but didn't help.

Log Message before getting PDF content 

2010/09/24 14:54:06:497 GMT+05:30 [DEBUG] HttpMethodBase - Resorting to 
protocol version default close connection policy
2010/09/24 14:54:06:497 GMT+05:30 [DEBUG] HttpMethodBase - Should NOT close 
connection, using HTTP/1.1
2010/09/24 14:54:06:513 GMT+05:30 [DEBUG] HttpConnection - Releasing connection 
back to connection manager.
2010/09/24 14:54:06:513 GMT+05:30 [DEBUG] MultiThreadedHttpConnectionManager - 
Freeing connection

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to