axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Traud (JIRA)" <>
Subject [jira] [Updated] (AXIS2-5497) Occasional End of Stream but boundary not found using MTOM
Date Tue, 16 Apr 2013 11:15:17 GMT


Stefan Traud updated AXIS2-5497:

    Attachment: client_exception-B-axis2-1.6.3-SNAPSHOT.log

Attached log outputs from 1.6.3-SNAPSHOT. The problem persists in that the service still needs
> 1 min to process the message. The client either gets the returned Axis Fault "Failed
to fetch the MIME part content" (A) or ends with "Connection reset" (B)
> Occasional End of Stream but boundary not found using MTOM
> ----------------------------------------------------------
>                 Key: AXIS2-5497
>                 URL:
>             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-SNAPSHOT_A-failed.log, axis2-1.6.3-SNAPSHOT_B-failed.log,
axis2_failed.log, client_exception-A-axis2-1.6.3-SNAPSHOT.log, client_exception-B-axis2-1.6.3-SNAPSHOT.log,
client_exception.log, MTOMSampleClient.jar,
> Using MTOMSample service (sample/mtom/service) to upload big amount (>1000) of files
sequentially, it happens occasionally that client aborts with exception caused by "
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

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message