axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Traud (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AXIS2-5497) Occasional End of Stream but boundary not found using MTOM
Date Fri, 08 Mar 2013 12:02:14 GMT
Stefan Traud created AXIS2-5497:
-----------------------------------

             Summary: Occasional End of Stream but boundary not found using MTOM
                 Key: AXIS2-5497
                 URL: https://issues.apache.org/jira/browse/AXIS2-5497
             Project: Axis2
          Issue Type: Bug
    Affects Versions: 1.6.1
         Environment: Client running on Windows XP JRE 1.6.0_32-b05
            Reporter: Stefan Traud
            Priority: Minor


Using MTOMSample service (sample/mtom/service) to upload big amount (>1000) of files sequentially,
it happens occasionally that client aborts with exception caused by "java.net.SocketTimeoutException:
Read timed out." The axis2 debug log show "End of Stream but boundary not found".
In the testing environment, the client timeout was set to 10s, the size of the uploaded file
is 75KB. It is also noteable that the End of Stream log on the service is shown only after
> 1 minute after end of header initialisation.
The issue was reproducable on Windows XP/JRE 1.6

The issue could not be reproduced 
- when the client was executed on CentOS5 JRE 1.6/1.7 or Windows Vista JRE 1.6
- when TCPMon was used to monitor soap packages (probably because this reduces throughput
drastically)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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