Hello,
We've analysed it with Artus Applicare and Jboss profiler. There is nothing
strange for Axis 1.5.
We are using axis on server side and on client side. Both of them seems fine.
what kind of tuning tool are you using ?
what kind of model are you using?(on client side? on server side?
Hi Ceri,
Apart from using 1.5 , did you do anything else. I just upgraded to 1.5.1 from
1.4.1 and still see memory leak. Would appreciate any help.
Sanjay
-Original Message-
From: ceri tandogan [mailto:[email protected]]
Sent: Wednesday, June 16, 2010 1:28 PM
To: [email protected]
Yes, definitely. I'm using axis 1.5, it works fine and no memory leak is
observed.
I think this library is replaced by axis2 transport jar.
Ceri
- Original Message
From: "FRYARS, Michael"
To: [email protected]
Cc: [email protected]
Sent: Wed, June 16, 2010 10:29:55
Hi, can anyone tell me if the problem discussed below ("BackportUtil jar
causing memory leak") was ever verified to be a genuine problem in Axis2
1.4 ?
Was this a one-off report of the problem, or is it know to be a
general/repeatable issue?
And does it definitely go away from Axis2 1.5 onwa
I have a web
service that I am trying to migrate from Axis1 to Axis2. The service
is deployed as a POJO and I throw a custom checked exception from some
of my methods. The exception shows up in the WSDL that is auto
generated by Axis:
