Java Out Of Box seems to lower kernel Parameters

[V.Prakash]

Hello Everybody,
I am a CSC engineer supporting the Performance producrts.I had suggested one of my customers to install JOOB as OVPM( a performance product) uses Java.After installation of Java Out Of Box it seems to have lowered some of the original Kernel parameters values which made the server unusable for quiet some time.
In the Usage Documentation of JOOB which can be accessed at http://www.hp.com/products1/unix/java/java2/outofbox/infolibrary/release_notes_java_oob.html#usage , it says that => JavaOOB will not lower the values of any kernel parameters or system tunables. If the system has already been configured with values the same as or larger than those defined in JavaOOB, they will be left alone.

The following parameters values were lowered by JOOB : nfile, nproc, ncallout and nkthread

Can any one please help on this issue.

Thanks in advance

[Alex Lavrov.]

Just, an idea. Are you sure that the lover values were not pending and after reboot they were applied?


Alex.

[renarios]

Hi,

Can you change the kernel parameters to the default values using SAM?

Cheerio,

Renarios

[Steven E. Protter]

Well, I don't think software depots should be lowering kernel configuration values.

nfile, nproc, ncallout and nkthread may need to be higher to handle busy machines.

It is quite possible for a kernel patch to do this however. If you have kernel parameters set by formula (something I do less and less) then changes to other kernel values can cause this.

Solution: Report the problem to hp (this post does not really do that), and raise the values back up, compile and post a new kernel to production followed by a boot.

While you are at it, make sure maxuprc is 200 or above.

It won't hurt JOOB.

SEP

[harry d brown jr]

These are the formula's I have:

nfile: ((16*(NPROC+16+MAXUSERS)/10)+32+2*(NPTY+NSTRPTY+NSTRTEL)

nproc: 20+(8 * maxusers)

ncallout: 16+nproc

nkthread: (nproc*2)+16

If "maxusers" changes, then "nproc" changes, which causes "nfile", then "ncallout" and "nkthread" changes - plus probably some other value changes.

Check to see if "maxusers" changed, thus causing the ripple effect.


live free or die
harry d brown jr

[V.Prakash]

Renarios,
Customer couldnot raise the values using SAM.