Troubleshooting
Problem
A minimum/maximum instance violation due to APC's inability to meet the configured minimum or maximum number of defined instances of an application server for a Dynamic Cluster.
Symptom
The log excerpts below from apc.log having apc must gather traces enabled illustrates instance FRMI2-1VerCluster_dev-ap731Node01 being stopped with reason 'LID_CAPACITY' (load independednt capacity) thus indicating insufficient available memory.
FRMI2-1VerCluster_dev-ap731Node01 instance stops suddenly with LID_CAPACITY also another instance on different node also does not start showing similar behavior in such cases min/max is disturbed.
[14/09/22 10:24:01:583 JST] 000002f5 APCXDServerMo 2 statusChangedREAL underLock call() L_0330 xdServerInstance={APCXDServerImpl name=FRMI2-1VerCluster_dev-ap731Node01,node=dev-ap731Node01,cell=DevNetwork,currSize=571.0,maxHeapSize=512.0
[14/09/22 10:24:09:155 JST] 00000488 APCXDTaskProg > changeComplete ENTRY {APCXDChangeDCAbstract:1776176991 server={APCXDServerImpl name=FRMI2-1VerCluster_dev-ap731Node01,node=dev-ap731Node01,cell=DevNetwork,currSize=571.0,maxHeapSize=512.0,maxDemand=-1.0,cluster=FRMI2-1VerCluster,ut={UtilityFunctionAlwaysOne},maint=false,admin=false,disposable=false,startTime=0,state=STOPPED,change=STOP,pretext={PretextCntrInstImpl id=6 reason=LID_CAPACITY thing=P:dev-ap731 changes(2)=[
{StopApplInstChangeImpl id=8, name=FRMI2-1VerCluster, inst=DevNetwork/dev-ap731Node01/FRMI2-1VerCluster_dev-ap731Node01, inside=DevNetwork/dev-ap731Node01/FRMI2-1VerCluster_dev-ap731Node01},
{StopCntrInstChangeImpl id=9, name=FRMI2-1VerCluster, inst=DevNetwork/dev-ap731Node01/FRMI2-1VerCluster_dev-ap731Node01, inside=DevNetwork/dev-ap731Node01}]
}} SUCCESS
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
03 March 2025
UID
swg21965051