Unknown Status on Overloaded Servers

HP Output Server 3.5 1
Technical Note
Unknown Status on Overloaded Servers
This technical note addresses the issue of some servers shutting down when overloaded. It also provides a
workaround for resolving the problem.
Servers affected
• Job Queue Manager (JQM) server
• Destination Manager (DSM) server
• Configuration Manager (CM) server
Problem
When a user attempts to execute an HP Output Server command on a batch of jobs, the JQM, CM and DSM servers
go into an ‘unknown’ state, or they generate a core dump. Executing an HP Output Server command on a batch of
jobs forces the servers to attempt to allocate more memory than allowed by the specified data segment stack size.
Solution
You can avoid this problem by using one of the following methods:
• Increasing the data segment stack size
• Using indexed attributes for HP Output Server commands
• Using arenas and extensionpages to allocate memory (HP-UX)
Increasing the data segment stack size
Increase the data segment stack size by using the ulimit command. Each operating system uses a separate data
segment stack size. Find the current data segment stack size by using the following command:
ulimit -a
Example
Output for ulimit -a command on the Solaris platform:
$ulimit -a
time (seconds) - unlimited
file (blocks) - unlimited
data (kbytes) - 96000