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

[Casey J. <cas...@jo...>]

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!
>



-- 
--
Casey Jordan
easyDITA a product of Jorsek LLC
"CaseyDJordan" on LinkedIn, Twitter & Facebook
(585) 348 7399
easydita.com


This message is intended only for the use of the Addressee(s) and may
contain information that is privileged, confidential, and/or exempt from
disclosure under applicable law.  If you are not the intended recipient,
please be advised that any disclosure  copying, distribution, or use of
the information contained herein is prohibited.  If you have received
this communication in error, please destroy all copies of the message,
whether in electronic or hard copy format, as well as attachments, and
immediately contact the sender by replying to this e-mail or by phone.
Thank you.