[ 
https://issues.apache.org/jira/browse/AXIS2-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Traud updated AXIS2-5497:
--------------------------------

    Attachment: client_exception-B-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log
                client_exception-A-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log
                axis2-1.6.3-axiom-1.2.15-SNAPSHOT_B-failed.log
                axis2-1.6.3-axiom-1.2.15-SNAPSHOT_A-failed.log

Attached log outputs using SNAPSHOTS from axis2-1.6.3 / axiom-1.2.15. A: 
"Failed to fetch the MIME part content" B: "Connection reset"
                
> 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, 1.6.2
>         Environment: Client running on Windows XP JRE 1.6.0_32-b05
>            Reporter: Stefan Traud
>            Priority: Minor
>              Labels: mtom
>         Attachments: axis2-1.6.3-axiom-1.2.15-SNAPSHOT_A-failed.log, 
> axis2-1.6.3-axiom-1.2.15-SNAPSHOT_B-failed.log, 
> axis2-1.6.3-SNAPSHOT_A-failed.log, axis2-1.6.3-SNAPSHOT_B-failed.log, 
> axis2_failed.log, client_exception-A-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log, 
> client_exception-A-axis2-1.6.3-SNAPSHOT.log, 
> client_exception-B-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log, 
> client_exception-B-axis2-1.6.3-SNAPSHOT.log, client_exception.log, 
> MTOMSampleClient.jar, MTOMStressClient.java
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to