Return-Path: X-Original-To: apmail-axis-java-dev-archive@www.apache.org Delivered-To: apmail-axis-java-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 011A0F231 for ; Tue, 16 Apr 2013 11:15:24 +0000 (UTC) Received: (qmail 86254 invoked by uid 500); 16 Apr 2013 11:15:23 -0000 Delivered-To: apmail-axis-java-dev-archive@axis.apache.org Received: (qmail 85656 invoked by uid 500); 16 Apr 2013 11:15:20 -0000 Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@axis.apache.org Delivered-To: mailing list java-dev@axis.apache.org Received: (qmail 84592 invoked by uid 99); 16 Apr 2013 11:15:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2013 11:15:17 +0000 Date: Tue, 16 Apr 2013 11:15:17 +0000 (UTC) From: "Stefan Traud (JIRA)" To: java-dev@axis.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AXIS2-5497) Occasional End of Stream but boundary not found using MTOM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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-SNAPSHOT.log client_exception-A-axis2-1.6.3-SNAPSHOT.log axis2-1.6.3-SNAPSHOT_B-failed.log axis2-1.6.3-SNAPSHOT_A-failed.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: 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-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, 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: java-dev-unsubscribe@axis.apache.org For additional commands, e-mail: java-dev-help@axis.apache.org