|
From: Leif M. <le...@ta...> - 2007-03-21 01:18:58
|
Todd,
Does your application make use of any of the WrapperManager API
calls? Or are
you simply using Method #1 or #2 to wrap your application?
I ask because a memory leak in the WrapperManager.listServices()
method was
recently reported. It has been fixed for the upcoming 3.2.4 release.
That leak was in
the native library and showed up as a leak in the java process but I had
not verified that
there was not also a leak in the OS.
I have not noticed any such leak in the past, but that doesn't mean
it is not there.
How significant is the leak you are seeing? How is its growth releated
to the Wrapper's
lifecycle? Basically you have told me there is a leak in the Wrapper, I
am looking for
how I can reproduce your tests and see this myself.
Cheers,
Leif
Todd Wilson wrote:
> Hi,
>
> We've had a terrible time tracking down what was a bizarre type of
> memory leak where, when running on Windows, the java.exe process would
> not increase dramatically in size, but the page file used by the OS
> would. I finally narrowed the issue down to Java Service Wrapper. If I
> run our application without using Java Service Wrapper, everything works
> great. When I start it up with Java Service Wrapper, however, and start
> using it as it's normally used, the page file size starts to increase
> significantly. I've tried upgrading to the latest version of Java
> Service Wrapper, but, unfortunately, it didn't help. There's probably
> something simply I'm missing. Has anyone else encountered this? Thanks
> in advance for any help you might be able to offer.
>
> Kind regards,
>
> Todd Wilson
>
|