>>>>> "MB" == Michael Bilow <[EMAIL PROTECTED]> writes:
MB> However, the system limitations applicable to heavyweight
MB> processes apply equally to lightweight processes, in particular
MB> that a single non-root user may never exceed half of the available
MB> system pids. By default when building a Linux 2.2 kernel, the
MB> system has a global limit of 512 pids. This is configurable in
MB> the linux source (include/linux/tasks.h):
MB> #define NR_TASKS 512 /* On x86 Max about 4000 */ #define
MB> MAX_TASKS_PER_USER (NR_TASKS/2) #define MIN_TASKS_LEFT_FOR_ROOT 4
Ahhhh, ooooh, Thank you for reminding me of that valued filename!
<grin>
MB> As long as jBoss is not run by the root user, which is obviously
MB> extremely dangerous and undesirable for other reasons anyway, the
MB> maximum number of pids it can own concurrently is going to be
MB> limited to 255 on a default kernel. Once this thread limit is
MB> reached, jBoss will essentially wedge to the point where it no
MB> longer even responds to SIGTERM to shut down gracefully, but
MB> requires SIGKILL to stop it. I think that jBoss sees this
MB> situation as an "out of memory" condition as reflected by the JVM,
MB> but I am not sure about this. Of course, if jBoss is run by the
MB> root user for some reason, the entire machine will be wedged at
MB> this point and the only remedy would be something as drastic as
MB> the reset switch or the watchdog.
I agree 101% with your assessment.
--
Nicolai P Guba http://www.gnu.org http://www.frontwire.com
mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
GSM: +44 (0)7909 960 751 DDI: +44 (0)20 7368 9708
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
