[
https://issues.apache.org/jira/browse/AXIS2-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649342#comment-13649342
]
Andreas Veithen commented on AXIS2-5497:
----------------------------------------
Between 1.2.12 and 1.2.13 the MIME parsing code in Axiom was completely
rewritten (see AXIOM-326). The fact that the problem can be reproduced with
both implementations makes it less likely that it is caused by a bug in Axiom.
On the other hand, the fact that the problem disappears with TCPMon makes it
less likely that the root cause is a client side bug. I would concentrate on
the components in between the two. The logs indicate that you are using Tomcat
with the AJP connector, i.e. with an Apache HTTPD as a reverse proxy I guess.
Does the problem also occur if you send the request directly to Tomcat, i.e. if
you use Tomcat's HTTP connector?
> 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]
