Bug 1028639

Summary: Need to specify the need to potenially increase the allowed number of processes for user running JON on Linux and unixes
Product: [JBoss] JBoss Operations Network Reporter: Lukas Krejci <lkrejci>
Component: DocumentationAssignee: Deon Ballard <dlackey>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2   
Target Milestone: GA   
Target Release: JON 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-05 15:40:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1012435    

Description Lukas Krejci 2013-11-08 23:38:58 UTC 
Description of problem:
As part of investigation of bug 1025767, it was determined that the default number of allowed processes (to which the Java threads map under Linux) is enough for basic operation (the default is 1024).

However we've also seen that under a heavy load and if the user is running other "heavy" software like postgres, etc, that number can be too low and can cause out of memory errors.

We should document the need to increase the number of allowed process per user in addition to increasing the maximum heap size if the JON server starts to get out of memory errors.


Version-Release number of selected component (if applicable):
JON3.2.0
Comment 1 Mike Foley 2013-11-11 13:03:38 UTC 
this should be doc'd for JON 3.2.  flagging for documentation
Comment 2 Deon Ballard 2014-01-24 18:19:11 UTC 
This was added to teh new performance tuning chapter:
https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.2/html/Admin_and_Config/server-jvm.html