axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Bradley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5497) Occasional End of Stream but boundary not found using MTOM
Date Wed, 01 Apr 2015 15:28:53 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14390803#comment-14390803
] 

Richard Bradley commented on AXIS2-5497:
----------------------------------------

[~straud] Did you fix this?

We are seeing a similar issue in our load testing -- under very high load and high concurrency
we occasionally see exceptions like the following from Axis2
{code}
Caused by: org.apache.axis2.AxisFault: org.apache.james.mime4j.MimeIOException: Unexpected
end of stream
        at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) ~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:446)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
~[na:1.6.0_20]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
~[na:1.6.0_20]
        at java.lang.Thread.run(Thread.java:619) ~[na:1.6.0_20]
Caused by: org.apache.axiom.om.OMException: org.apache.james.mime4j.MimeIOException: Unexpected
end of stream
        at org.apache.axiom.attachments.MIMEMessage.<init>(MIMEMessage.java:137) ~[axiom-api-1.2.13.jar:1.2.13]
        at org.apache.axiom.attachments.Attachments.<init>(Attachments.java:93) ~[axiom-api-1.2.13.jar:1.2.13]
        at org.apache.axis2.builder.BuilderUtil.createAttachments(BuilderUtil.java:592) ~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.builder.BuilderUtil.createAttachmentsMap(BuilderUtil.java:543)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:39) ~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:179)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)
~[axis2-kernel-1.6.2-msw.jar:1.6.2]
        ... 7 common frames omitted
Caused by: org.apache.james.mime4j.MimeIOException: Unexpected end of stream
        at org.apache.james.mime4j.io.MimeBoundaryInputStream.verifyEndOfStream(MimeBoundaryInputStream.java:205)
~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.james.mime4j.io.MimeBoundaryInputStream.readAllowed(MimeBoundaryInputStream.java:129)
~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.james.mime4j.io.MimeBoundaryInputStream.read(MimeBoundaryInputStream.java:152)
~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.james.mime4j.io.LineReaderInputStreamAdaptor.read(LineReaderInputStreamAdaptor.java:67)
~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at java.io.FilterInputStream.read(FilterInputStream.java:90) ~[na:1.6.0_20]
        at org.apache.james.mime4j.stream.MimeEntity.advanceToBoundary(MimeEntity.java:390)
~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.james.mime4j.stream.MimeEntity.advance(MimeEntity.java:331) ~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.james.mime4j.stream.MimeTokenStream.next(MimeTokenStream.java:360) ~[apache-mime4j-core-0.7.2.jar:0.7.2]
        at org.apache.axiom.attachments.MIMEMessage.<init>(MIMEMessage.java:135) ~[axiom-api-1.2.13.jar:1.2.13]
        ... 14 common frames omitted
Caused by: org.apache.james.mime4j.MimeException: Unexpected end of stream
        ... 23 common frames omitted
{code}

We have been unable to reproduce this in an isolated test.

> 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: MTOMSampleClient.jar, MTOMStressClient.java, axis2-1.6.3-SNAPSHOT_A-failed.log,
axis2-1.6.3-SNAPSHOT_B-failed.log, 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_failed.log, client_exception-A-axis2-1.6.3-SNAPSHOT.log, client_exception-A-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log,
client_exception-B-axis2-1.6.3-SNAPSHOT.log, client_exception-B-axis2-1.6.3-axiom-1.2.15-SNAPSHOT.log,
client_exception.log
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
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