You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by bharath thippireddy <bh...@oracle.com> on 2009/06/04 23:32:36 UTC

Memory Issues With CXF Client

As a part of our webservices test automation we see that the CXF client runs out of JAVA Heap Space after running  a good number of testcases.Sometimes it uses up close to 1GB of memory. Is this as know issues and are there any workarounds?.

 

Thanks,

bharath


RE: Memory Issues With CXF Client

Posted by bharath thippireddy <bh...@oracle.com>.
Thanks Dan.Will try that(running automation) sometime next week as we will be migrating to  CXF 2.2.2.Just to let you know ,I have tried cxf 2.2.2 recently to see if ws-addressing  works for the provider based implementations and it does(Bug Fixed thanks).

Thanks and regards,
Bharath

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: Thursday, June 04, 2009 9:12 PM
To: users@cxf.apache.org
Cc: bharath thippireddy
Subject: Re: Memory Issues With CXF Client

On Thu June 4 2009 5:32:36 pm bharath thippireddy wrote:
> As a part of our webservices test automation we see that the CXF client
> runs out of JAVA Heap Space after running  a good number of
> testcases.Sometimes it uses up close to 1GB of memory. Is this as know
> issues and are there any workarounds?.

Any chance you could test this with 2.2.2?   We did some changes to the
request contexts in 2.2.2 that MAY have been the cause of this in prior
versions.

an


>
>
>
> Thanks,
>
> bharath

--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog


Re: Memory Issues With CXF Client

Posted by Daniel Kulp <dk...@apache.org>.
On Thu June 4 2009 5:32:36 pm bharath thippireddy wrote:
> As a part of our webservices test automation we see that the CXF client
> runs out of JAVA Heap Space after running  a good number of
> testcases.Sometimes it uses up close to 1GB of memory. Is this as know
> issues and are there any workarounds?.

Any chance you could test this with 2.2.2?   We did some changes to the 
request contexts in 2.2.2 that MAY have been the cause of this in prior 
versions.

an


>
>
>
> Thanks,
>
> bharath

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog