HP Global Workload Manager 7.0 User Guide

Workaround
There is no workaround; this is simply how fss groups are implemented on a system with psets.
You can continue with your fss groups inside pset 0 (leaving the other psets unmanaged), manage
using psets instead (ignoring fss groups), or remove all the psets (other than pset 0) using the
following command:
# psrset -d all
Custom metrics lost on redeploy
Custom policies use metric values that you provide via the gwlmsend command. If you redeploy
an SRD that has a custom policy, the most recent value for the policy's metric is lost. In this situation,
gWLM bases its allocations on the minimum request specified in the workload's policy. The workload
can also receive any CPU resources that remain after all the policies have been satisfied.
Workaround
Update the metric values for all your custom policies immediately after a redeploy.
Process placement using psrset is ignored
When gWLM is managing the psets on a system, every process on the system has to go in a
workload. gWLM places the processes according to application records or user records specified
when you create or edit a workload definition. If no records exist, the processes are subject to the
placement rules, which are explained in the online help topic "pset / fss group tips" in the section
"Precedence of placement techniques."
If you use the psrset command to place processes in psets, gWLM is likely to move the processes
to the default pset.
Workaround
To maintain the placement of a process, use gWLM's application records or user records when
creating or editing your workload definitions in gWLM. If using records is not practical, use the
gwlmplace command. However, you will have to use gwlmplace after each redeploy of an
SRD to put the processes back in the desired workloads.
iCAP compliance warning
gWLM might give the following warning:
Warning: gwlmagent cimserver error, icapd down, or icap out of
compliance. First restart cimserver. Make sure icapd is running. If
this error happens again, consult gwlmagent man page for steps to return
to compliance.
Workaround
Verify that no partition changes (parmodify) are pending. If partition changes are pending, please
restart the system. Then, either consult iCAP documentation or contact HP to return the iCAP system
back to compliance.
Major issues
The following are major issues for Global Workload Manager.
gWLM fails to start with certain time zone settings
gwlmcmsd and gwlmagent can fail to start with certain time zone settings. The following message
is displayed in the gwlmagent.log.0 file or the gwlmcmsd.log.0 file when you attempt to invoke
either daemon:
Unable to call method, 'main', with signature,
'([Ljava/lang/String;)V', in class, 'com/hp/gwlm/node/Node'.
Exception in thread "main"
52 Global Workload Manager A.7.0.0* Known issues