Re: question about passing Large string from Client to Apache Soap 2.2 Service

[Scott Nichol <sc...@yahoo.com>]

I have not experienced a similar problem, but I have an observation.  When you
run under Tomcat 4.x, your Apache SOAP code will use the versions of Xerces,
JavaMail and JAF that are bundled with Tomcat.  Under Tomcat 3.x, your Tomcat
startup script had to be changed to point to versions of those jars that you
specified.  Are the versions of any of these different?  If so, try running
under Tomcat 3.x using the versions of the jars that come with Tomcat 4.x to see
whether they are to blame.

Scott Nichol

----- Original Message -----
From: "Ding, Chengmin" <Ch...@issproxy.com>
To: <so...@xml.apache.org>
Cc: <so...@discuss.develop.com>
Sent: Wednesday, April 17, 2002 6:11 PM
Subject: question about passing Large string from Client to Apache Soap 2.2
Service


> Hello,
> We need to pass a large XML string(1-2 MB) from VB client to a Apache 2.2
> soap service.
> The XML String is MIME64 encoded before the invoke of the service and it is
> received in the service as a Binary array. This works fine(within 1 minute)
> in a Tomcat 3.2.3(3.3) + Soap 2.2 scenario. It used to take a long time
> before we started MIME64 encoding.
>
> Recently we setup another server which uses Tomcat 4.0.3 + Soap 2.2 and now
> the string passing takes about 30-40 minutes. We have some logging routine
> at the beginning of the invoked function and it started logging 30-40
> minutes after the client called the service. We think probably Tomcat 4.0.3
> delayed the passing the string from RPCRouter servlet to our service class
> but we cannot prove it.
> Has anyone encountered a similar problem? Any of your hints are highly
> appreciated.
>
> Thanks.
>
> -Chengmin


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com