Can you try this on the nightly build please. There was a memory leak that
was fixed on the trunk and it was post 1.4.1.

Thanks,
Keith.

On Sat, Dec 6, 2008 at 12:42 AM, Satyanarayana Murthy Godavarti (JIRA) <
[EMAIL PROTECTED]> wrote:

>
>    [
> https://issues.apache.org/jira/browse/AXIS2-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653895#action_12653895]
>
> Satyanarayana Murthy Godavarti commented on AXIS2-3870:
> -------------------------------------------------------
>
> Hi Amila,
>
> I tested my code with latest Axis2 1.4.1 version. I did not see any
> improvement in the memory leaks. Application is consuming huge amount of
> memory and getting terminated after few iterations. Can you please advise
>
>
>
>
>
> > Memory Leak using ServiceClient
> > -------------------------------
> >
> >                 Key: AXIS2-3870
> >                 URL: https://issues.apache.org/jira/browse/AXIS2-3870
> >             Project: Axis 2.0 (Axis2)
> >          Issue Type: Bug
> >          Components: kernel
> >    Affects Versions: 1.4
> >            Reporter: Hans G Knudsen
> >             Fix For: 1.4.1
> >
> >         Attachments: ClientLeak.java
> >
> >
> > Hi!
> > I think I see a leak when using ServiceClient.
> > In my client I intialize the ConfigurationContext once and resuse it to
> initialize the ServiceClient :
> >             ServiceClient sender = new ServiceClient(configContext,null);
> > Calling 'cleanup()' on the ServiceClinet explicitly after the service
> call does not help..
> > I will supply a small testcase.
> > /hans
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Reply via email to