Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 90521 invoked from network); 13 Jul 2006 02:04:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Jul 2006 02:04:30 -0000 Received: (qmail 24330 invoked by uid 500); 13 Jul 2006 02:04:26 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 24269 invoked by uid 500); 13 Jul 2006 02:04:26 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 24258 invoked by uid 99); 13 Jul 2006 02:04:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2006 19:04:26 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of csethil@gmail.com designates 64.233.182.190 as permitted sender) Received: from [64.233.182.190] (HELO nf-out-0910.google.com) (64.233.182.190) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Jul 2006 19:04:25 -0700 Received: by nf-out-0910.google.com with SMTP id g2so67553nfe for ; Wed, 12 Jul 2006 19:04:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=QzZuUumUKPm+bOGt5UNPbTVPSu0jCvQfY+cGshrWPJFa/d9F1IctEczZfcbTgvdDGDK3kRH7UwrPjCoEoxJEY4BpRRldd6LmzvaIq9SlhOYJQn+dqftBU9RG72JuxlhexBXlb0yVwndUIEeien4OT7FHH9GlBJFsfmySRD94Bgs= Received: by 10.78.177.11 with SMTP id z11mr151790hue; Wed, 12 Jul 2006 19:04:04 -0700 (PDT) Received: by 10.78.26.16 with HTTP; Wed, 12 Jul 2006 19:04:04 -0700 (PDT) Message-ID: Date: Thu, 13 Jul 2006 08:04:04 +0600 From: "Thilina Gunarathne" To: axis-dev@ws.apache.org Subject: [Axis2] MTOM Large file sending problem MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1887_21773539.1152756244246" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_1887_21773539.1152756244246 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, After further investigating in to recent reports of MTOM not being able to send large files, I found out that the problem lies with the Async invocation. In the sync+file caching everything works fine and smoothly for server uploads, without giving any noticeable increase of memory usage. But server gets out of memory exception when trying to echo back the received attachment. Reason may be the same as for the following async case. In the Async case memory usage goes high, proportionally to the attachment size. It seems Axis2 is trying to read the attachment in to memory in the async case. I went on debugging and still didn't get any clue. This is a very strange behaviour, cause both sync and async internally use the same code base, except for the new thread. I would be glad if somebody can shed some light on to this. Any pointers would be great. Thanks, ~Thilina -- "May the SourcE be with u" http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina ------=_Part_1887_21773539.1152756244246 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all,
After further investigating in to recent reports of MTOM not being able to send large files, I found out that the problem lies with the Async invocation.
In the sync+file caching everything works fine and smoothly for server uploads, without giving any noticeable increase of memory usage. But server gets out of memory exception  when trying to echo back the received attachment. Reason may be the same as for the following async case.

In the Async case memory usage goes high, proportionally to the attachment size. It seems Axis2 is trying to read the attachment in to memory in the async case. I went on debugging and still didn't get any clue. This is a very strange behaviour, cause both sync and async internally use the same code base, except for the new thread.

I would be glad if somebody can shed some light on to this. Any pointers would be great.

Thanks,
~Thilina
--
"May the SourcE be with u"            
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/                 http://www.bloglines.com/blog/Thilina                ------=_Part_1887_21773539.1152756244246--