InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
Impact of AdvDbg attribute on existing functionality of the entry point
You must clearly understand and consider the following impact while configuring the AdvDbg attribute:
Processing of other resources may get delayed as one thread is occupied in capturing the debug information.
System resources are consumed by extra activities like core generation, process stack and process tree generation.
Agent may stop responding due to low system resources.
Considering the above impact, the default action can be set for rarely occurring or one-time occurring events like open, close, offline, online, or clean. For other entry points, like monitor, if you face timeout issues, AdvDbg must be configured dynamically by overriding this attribute to the resource level for that resource which faces entry point timeout. As soon as the data is captured, AdvDbg attribute must be cleared for these entry points. If multiple resources of the same entry point are timing out, then choose only one resource to configure the AdvDbg attribute.
See Recommended steps for configuring AdvDbg attribute for monitor entry points.