Known Issues

The HP-UX 11.0 default value for maximum threads per process is 64, which may be too low for WebLogic Server and many Java server applications in general. When the value is too low, WebLogic Server may have problems starting up.

BEA recommends that you use the maximum kernel setting for the max_thread_proc and maxusers parameters. Setting maxusers to a higher value increases other machine-wide limits, such as nkthread (the maximum number of kernel threads). The following table provides some examples.

Parameter

Old Value

New Value

Description

max_thread_proc

64

1024

Maximum threads per process

maxfiles

60

256

Soft file limit per process

maxusers

32

256

Influences other parameters

nkthread

499

3635

Number of threads total on the system

nproc

276

2068

Maximum number of processes

ncallout

292

2084

Number of pending timeouts

When you start a server the following entry appears in the server log file:

This message is not critical; it is a known issue with the HP-UX SDK that should be fixed in HP-UX SDK 1.4.1.02.

The cacerts file under ${BEA_HOME}/jdk141_01/jre/lib/security is corrupt. For a new version, visit HP's developer site. For demonstration purposes use the following file: ${WL_HOME}/server/lib/cacerts.

To avoid OutOfMemory exceptions or JVM crashes, increase the values of three Java options: -Xms, -Xmx, and -XX:MaxPermSize.

The following values are suggested: -Xms200m, -Xmx512m, and -XX:MaxPermSize=128m.

For more information about known issues with this release, see the WebLogic Server 8.1 Release Notes, available at: