Explanation | An Exception occurs when setting QTI listener. |
Action | Report program defect to IBM. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | An Exception occurs when getting or setting DialogAux. |
Action | Report program defect to IBM. |
Explanation | An Exception occurs when setting DialogAux. |
Action | Report program defect to IBM. |
Explanation | This should not happen. |
Action | Report program defect to IBM. |
Explanation | This reports that autonomic request flow management will be applied to SIP messages coming in to this process. |
Action | No action required. |
Explanation | This reports that autonomic request flow management will NOT be applied to SIP messages coming in to this process. |
Action | No action required --- unless that management was expected, in which case check the configuration and report to IBM if there is a problem. |
Explanation | The memory protection parameter used by WLM will be set autonomically |
Action | No action required. |
Explanation | The memory protection parameter used by WLM will NOT be set autonomically |
Action | No action required. |
Explanation | Internal failure. |
Action | Report to IBM. |
Explanation | Some JVM internal call may be changed. Common memory overload protection method will be used. |
Action | No action required. |
Explanation | ODC may occur some error. No new importance threshold will be transmitted till it recovers. |
Action | Report to IBM. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently. |
Action | If the chosen interval is not good, set the explicitGcPeriod custom property on the cluster to indicate the desired interval; a value of zero disables this function. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently. |
Action | If the chosen interval is not good, set the explicitGcPeriod custom property on the cluster to indicate the desired interval; a value of zero disables this function. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently. |
Action | If the chosen interval is not good, set the explicitGcPeriod custom property on the cluster to indicate the desired interval; a value of zero disables this function. |
Explanation | This message reports the basic parameters of the memory overload protection. |
Action | Change the configuration if desired. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently; when a generational garbage collection technique is in use, a full garbage collection is detected when the memory usage drops by more than a lesser collection can free. |
Action | If the chosen value is not good, set the maxNonFullGcMemoryRelease custom property on the cluster to indicate the critical amount of freed memory; a value of zero means every collection is deemed full, and a huge value means no collection (except those explicitly initiated by the protection function) will be deemed full. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently; when a generational garbage collection technique is in use, a full garbage collection is detected when the memory usage drops by more than a lesser collection can free. |
Action | If the chosen value is not good, set the maxNonFullGcMemoryRelease custom property on the cluster to indicate the critical amount of freed memory; a value of zero means every collection is deemed full, and a huge value means no collection (except those explicitly initiated by the protection function) will be deemed full. |
Explanation | Autonomic memory overload protection will explicitly trigger a garbage collection when the memory usage is high, unless this function is disabled or a full garbage collection has been done too recently; when a generational garbage collection technique is in use, a full garbage collection is detected when the memory usage drops by more than a lesser collection can free. |
Action | If the chosen value is not good, set the maxNonFullGcMemoryRelease custom property on the cluster to indicate the critical amount of freed memory; a value of zero means every collection is deemed full, and a huge value means no collection (except those explicitly initiated by the protection function) will be deemed full. |
Explanation | The autonomic memory overload protection controller is unable to determine the nursery size limit. |
Action | Either accept the assumed value, set the maxNonFullGcMemoryRelease custom property on the cluster, or use a non-generational collector. |
Explanation | The autonomic memory overload protection controller is unable to determine the nursery size limit. |
Action | Either accept that explicit garbage collections will not be suppressed by ones initiated by the collector, set the maxNonFullGcMemoryRelease custom property on the cluster, or use a non-generational collector. |
Explanation | On-Demand Configuration is used to convey the memory overload protection control settings from the local process to the On-Demand Routers; because of this failure, the control settings will not be automatically updated. |
Action | Report to IBM. |
Explanation | When collector values throughput over minimizing stop-the-world times, it improves the accuracy of the memory usage estimate. Otherwise, it only happens under urgent condition: the admission fraction of new dialogs is too small, so that it is hard for the collector itself to trigger a full GC to release the garbage in memory. |
Action | No action required. |
Explanation | When collector values throughput over minimizing stop-the-world times, it improves the accuracy of the memory usage estimate. Otherwise, it only happens under urgent condition: the admission fraction of new dialogs is too small, so that it is hard for the collector itself to trigger a full GC to release the garbage in memory. |
Action | No action required. |
Explanation | Something suspicious happened; this may or may not indicate an error. |
Action | Debug it if you can, using the information provided, or contact IBM support. |
Explanation | Something unexpected happened. |
Action | Debug it if you can, using the information provided, or contact IBM support. |