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 onwards?

Thanks in advance.


http://mail-archives.apache.org/mod_mbox/axis-java-user/201003.mbox/%[email protected]%3e


From    Andreas Veithen <[email protected]>
Subject             Re: BackportUtil jar causing memory leak
Date     Tue, 16 Mar 2010 11:49:09 GMT


On Tue, Mar 16, 2010 at 09:46, mohit sikri <[email protected]> wrote:
>
> Hi Andreas/Axis Team,
>
> It is since which version of axis2.

Since Axis2 1.5.

> We are using axis2.1.4 and there seems to be a tight coupling between the two(backport.jar and axis core(kernel)), isn't there any system parameter which can be configured or a way to configure axis2.xml so as to switch to concurrency framework provided by jdk5 rather than
using backport.jar, by still maintaining the same version of axis.

No.

> Request you to provide any workaround if possible.
>
>
> --- On Tue, 16/3/10, Andreas Veithen <[email protected]> wrote:
>
> From: Andreas Veithen <[email protected]>
> Subject: Re: BackportUtil jar causing memory leak
> To: [email protected]
> Date: Tuesday, 16 March, 2010, 12:01 AM
>
> Since we moved to Java 1.5, Axis2 no longer relies on this library.
>
> On Mon, Mar 15, 2010 at 15:05, sri ram <[email protected]> wrote:
> > Hi Axis2 Users,
> >
> > This is regarding the jar backport-util-concurrent.jar which is being used
> > in Axis2 at some
> > stage of processing the request .However the? hprof file shows a lot issues
> > with this
> > jar as? it consumes a lot of heap space and causing memory leak .Finally
> > causing the tomcat to crash .
> > Can anyone suggest the root cause of the issue or direct me to the
> > improvised jar.
> > This issue is critical.
> > I can provide more info on this if required.
> >
> > Thanks,
> > Sriram
> >









---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to