If you don't have access to this KB article let me know and I can print it
out for you. Looks to be a kernel bug.  A quick cut and paste of the
workaround section:

 This issue is resolved in kernel-2.6.32.358.16.1.el6 and later.

Please update the kernel package with yum update kernel.
Workaround

Run the following command as the root user:

echo 1 > /proc/sys/vm/unmap_area_factor

If this resolves the issue, then add the following line to
/etc/sysctl.confto persist the change across reboots:

vm.unmap_area_factor = 1




On Thu, Mar 13, 2014 at 9:15 AM, Wesley Duffee-Braun <[email protected]>wrote:

> What version of CentOS are you running?
>
> I found this https://access.redhat.com/site/solutions/409353 that may be
> related.
>
>
> On Thu, Mar 13, 2014 at 10:08 AM, Howard White <[email protected]> wrote:
>
>> On 03/13/2014 09:01 AM, Kent Perrier wrote:
>>
>>> The first thing that jumps to my mind is the ulimit on memory size for
>>> the user that is running the JVM.
>>>
>>> Kent
>>>
>>>
>> $ ulimit -a
>> core file size          (blocks, -c)    0
>> data seg size           (kbytes, -d)    unlimited
>> scheduling priority     (-e)            0
>> file size               (blocks, -f)    unlimited
>> pending signals         (-i)            96303
>> max locked memory       (kbytes, -l)    64
>> max memory size         (kbytes, -m)    unlimited
>> open files              (-n)            1024
>> pipe size               (512 bytes, -p) 8
>> POSIX message queues    (bytes, -q)     819200
>> real-time priority      (-r)            0
>> stack size              (kbytes, -s)    10240
>> cpu time                (seconds, -t)   unlimited
>> max user processes      (-u)            1024
>> virtual memory          (kbytes, -v)    unlimited
>> file locks              (-x)            unlimited
>>
>>
>> Howard
>>
>> --
>> --
>> You received this message because you are subscribed to the Google Groups
>> "NLUG" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to nlug-talk+unsubscribe@
>> googlegroups.com
>> For more options, visit this group at http://groups.google.com/
>> group/nlug-talk?hl=en
>>
>> --- You received this message because you are subscribed to the Google
>> Groups "NLUG" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> http://www.wesleyduffeebraun.com
> <http://www.ashevillephotobooth.com>
>
> --
> --
> You received this message because you are subscribed to the Google Groups
> "NLUG" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nlug-talk?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "NLUG" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nlug-talk?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"NLUG" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to