Re: [Wrapper-user] Advice on stopping wrapper from triggering JVM restarts

[Leif M. <lei...@ta...>]

Casey,
Rather than patching the Wrapper, I would suggest the released version with
the fix.  There have been a number of other important improvements as well.
We usually wait a couple weeks after a release before deciding to raise a
version to stable.  This is done to make sure that there are no unexpected
errors reported from the user base.
So far 3.5.26 has been quite stable.

Cheers,
Leif


On Sun, Dec 21, 2014 at 9:52 AM, Casey Jordan <cas...@jo...>
wrote:
>
> Hi Tim & Community,
>
> Sorry I had to go back and review your previous comments before I realized
> you had posted those patches and also provided me with instructions.
>
> I am currently running wrapper version 3.5.17. I also saw that 3.5.26
> appears to have the memory leak fixes in it (Based on reading the release
> notes).
>
> Which of the following would be the best option?
>
> Patch v3.5.17
> Upgrade to v3.5.25 and patch
> Use v3.5.26 (Which I believe contains the fix I need)
>
> Obviously using 3.5.26 seems the simplest approach here, but I just wanted
> to double check with the community.
>
> Thanks, your help is much appreciated.
>
> On Sat, Dec 20, 2014 at 6:46 PM, Casey Jordan <cas...@jo...>
> wrote:
>
>> Ok, so I have been monitoring for a bit now and I can definitely say that
>> I have this memory leak and it is causing the issues I am experiencing.
>>
>> Now the issue remains that I do not believe that I can upgrade glibc on
>> my system, given that all the threads I read say that will cause major
>> problems. Also, I need to use CentOS 7 if at all possible.
>>
>> I noticed in the previously referenced thread that someone created a
>> patch directly in the wrapper to also fix this issue, does anyone know if
>> this fix made it into a release that I could use?
>>
>> Thanks!
>>
>
>