Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Subject: Re: When is Axis 1.2 expected to be "final"?
From: Nishant Kumar <nishant.kumar@itellix.com>
To: axis-dev@ws.apache.org
In-Reply-To: <E0C16E55-D5C2-11D8-9E84-000A95AF91FC@axonstudios.net>
References: 
	 <480B2C0FB4E3C248A58A69BF5A68D19F448C7A@ad2kex02.informatica.com>
	 <19e0530f040714053273f40a5a@mail.gmail.com>
	 <02b901c469a0$518f82e0$7b00a8c0@AURORA>
	 <19e0530f0407140621fb5b805@mail.gmail.com>
	 <E0C16E55-D5C2-11D8-9E84-000A95AF91FC@axonstudios.net>
Content-Type: text/plain; charset=UTF-8
Organization: 
Message-Id: <1089954596.9517.17.camel@it-nishant>
Mime-Version: 1.0
Date: 16 Jul 2004 10:39:56 +0530
Content-Transfer-Encoding: 8bit

hi Peter,
	i tried looking into this matter. let me first explain what i modified
in your test case.

firstly i replaced your java client by a simple UNIX POST command.

something like this.

POST -H 'Content-Type: text/xml; charset=utf-8' -H 'Accept:
application/soap+xml, application/dime, multipart/related, text/*' -H
'User-Agent: Axis/1.2beta2' -H 'Host: localhost:8080' -H 'Cache-Control:
no-cache' -H 'Pragma: no-cache' -H 'SOAPAction: ""'
http://10.0.2.124:8080/axis/services/MemoryTester <getRoot.xml >
response

where getRoot.xml has the packet you used to send by your java client.

the benefit of doing this was that one can avoid having deserialization
cost at the client.

i hope you were anyway running the client on a different machine than
the server. this is a MUST. 

you can run with verbosegc to find out how much memory the server is
actually taking. no need to run gc.

after doing this i was able to run 8 such concurrent client with just
300M set as -mx.

another thing i noted was that the response was 13MB in size. that is a
huge response, that too when you are generating the same and not serving
some static file.

thanks,
nishant


On Wed, 2004-07-14 at 23:53, Peter Molettiere wrote:
> I reported 1423, with the test case -- If there's anything I can do to 
> help you out at all, please let me know. I'm more than happy to help.
> 
> --Peter
> 
> On Jul 14, 2004, at 6:21 AM, Davanum Srinivas wrote:
> 
> > Glen,
> >
> > I'd REALLY like your help with the following:
> > http://nagoya.apache.org/jira/browse/AXIS-1120 (DefaultTypeMappingImpl
> > is not compliant with JAX-RPC 1.1)
> > http://nagoya.apache.org/jira/browse/AXIS-1423 (OutOfMemoryError in
> > axis with multi-threaded usage)
> > http://nagoya.apache.org/jira/browse/AXIS-1391 (severe memory leakage
> > in server side service (with tomcat))
> >
> > 1120 involves exposing the currently internal flag
> > (jaxrpc11Compliance) via the various command line utils and ant tasks.
> > the other two 1423 and 1391 are severe problems with performance with
> > test cases that recreate the problem.
> >
> > Thanks,
> > dims
> >
> > On Wed, 14 Jul 2004 08:44:33 -0400, Glen Daniels 
> > <glen@thoughtcraft.com> wrote:
> >> dims:
> >>
> >> Can you please let us know which bugs those were?  I'd like to take 
> >> another
> >> brief look at them during beta-2.
> >>
> >> --Glen
> >>
> >>
> >>
> >> ----- Original Message -----
> >> From: "Davanum Srinivas" <davanum@gmail.com>
> >> To: <axis-dev@ws.apache.org>
> >> Sent: Wednesday, July 14, 2004 8:32 AM
> >> Subject: Re: When is Axis 1.2 expected to be "final"?
> >>
> >> WSE 2.0 is FINAL now!!!! (see
> >> http://msdn.microsoft.com/webservices/building/wse/). Also changed the
> >> priority for the blockers to major.
> >>
> >> -- dims
> >>
> >> On Wed, 14 Jul 2004 13:32:24 +0200, Banck, Arent-Jan
> >> <ajbanck@informatica.com> wrote:
> >>> As .NET 2.0 is only a beta, 1.1 is the most recent .NET version.
> >>>
> >>> There are currently 5 cases marked as blocker in Jira. If these are 
> >>> not
> >> blockers for 1.2 they should probably be given another priority.
> >>>
> >>> - Arent-Jan
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Davanum Srinivas [mailto:davanum@gmail.com]
> >>> Sent: Wednesday, July 14, 2004 1:22 PM
> >>> To: axis-dev@ws.apache.org
> >>> Subject: Re: When is Axis 1.2 expected to be "final"?
> >>>
> >>> Thomas,
> >>>
> >>> IF someone submits a test case that displays this problem with 
> >>> latest .NET
> >> 2.0 FINAL and Axis LATEST CVS, then am willing to hold up the beta. 
> >> Not
> >> otherwise.
> >>>
> >>> -- dims
> >>>
> >>> On Wed, 14 Jul 2004 10:07:48 +0200, Thomas Börkel <tbo@ap-ag.com> 
> >>> wrote:
> >>>> HI!
> >>>>
> >>>> Sorry, but how can Axis 1.2 going to be released, if there are 
> >>>> severe
> >>>> interop problems with .NET?
> >>>>
> >>>> http://nagoya.apache.org/jira/browse/AXIS-1308
> >>>>
> >>>> Thomas
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Tom Jordahl [mailto:tomj@macromedia.com]
> >>>>> Sent: Freitag, 9. Juli 2004 17:03
> >>>>> To: 'axis-dev@ws.apache.org'
> >>>>> Subject: RE: When is Axis 1.2 expected to be "final"?
> >>>>>
> >>>>>
> >>>>>
> >>>>> Real soon now....
> >>>>>
> >>>>> --
> >>>>> Tom Jordahl
> >>>>> Macromedia Server Development
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: ricky_frost@peoplesoft.com 
> >>>>> [mailto:ricky_frost@peoplesoft.com]
> >>>>> Sent: Thursday, July 08, 2004 1:18 PM
> >>>>> To: axis-dev@ws.apache.org
> >>>>> Subject: When is Axis 1.2 expected to be "final"?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> A project I'm looking at (ws-wsrp4j) just incorporated the 1.2 beta
> >>>>> and so I would like to know. I asked on that list but they referred
> >>>>> me here...
> >>>>>
> >>>>>
> >>>>
> >>>
> >>> --
> >>> Davanum Srinivas - http://webservices.apache.org/~dims/
> >>>
> >>
> >> --
> >> Davanum Srinivas - http://webservices.apache.org/~dims/
> >>
> >>
> >
> >
> > -- 
> > Davanum Srinivas - http://webservices.apache.org/~dims/
>