Re: [Wrapper-user] Disable OOM killer for process?

[Dannes W. <da...@ex...>]

Hi,

over committing memory sounds like a bad thing to do? You should make sure
anyway that the JVM will not be swapped out due to memory restrictions.

regards

Dannes


On Sun, Sep 27, 2015 at 12:32 AM, Casey Jordan <cas...@jo...>
wrote:

> Hi all,
>
> We are having an issue where the out of memory killer is killing out
> process due to the out of the box overcommit memory settings on CentOS.
>
> After researching this quite a bit, I think the best thing to do is to
> tell the OOM killer to never kill the process, as described here:
> http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html
>
> To do this, we need to execute the following command after startup:
>
> echo -17 > /proc/{pid}/oom_adj
>
>
> I was thinking this could be done as part of the *.sh script that gets
> executed via the java service wrapper, but I am not sure exactly how to do
> this (mainly where in this script I can put the valid logic). I am hoping
> someone might have done this before that could help.
>
> Thanks!
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>


-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624