Deployed a sybase agent and the agent seems to be cycling every 10 mins or so. Looks like when it tries to collect its crashing on a null object?
From Management server log:
YYYY-MM-DD HH:MM:SS.SSS WARN [http-0.0.0.0-8080-6] com.quest.wcf.portal.viewcomponents.BaseViewComponent - Error evaluating runtime value in context entry with key DBNames
com.quest.wcf.core.module.runtimevalue.RuntimeValueException: com.quest.wcf.publicapi.code.FunctionInvocationException: Error executing script id=system:sybasemda.616 name="'getDBNames For Dropdown' from the System module SybaseMDA"
message: com.quest.nitro.service.sl.interfaces.scripting.ScriptingException: com.quest.nitro.service.sl.interfaces.scripting.ScriptAbortException: java.lang.NullPointerException: Cannot get property 'Sybase_MDA_TopSQL' on null object
From Agent Log:
YYYY-MM-DD HH:MM:SS.SSS ECHO <SybaseCartridge/5.5.8.28/Sybase_MDA-agent> INFO [TEST2 Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: Sybase_MDA - New Binary Version=5.5.8.28, compiled=Oct 2 2011, 10:54:37
YYYY-MM-DD HH:MM:SS.SSS ECHO <SybaseCartridge/5.5.8.28/Sybase_MDA-agent> WARN [TEST2 Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: ASE Error Log file is not specified.
YYYY-MM-DD HH:MM:SS.SSS ECHO <SybaseCartridge/5.5.8.28/Sybase_MDA-agent> WARN [TEST2 Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: Backup Error Log filename is not specified.
YYYY-MM-DD HH:MM:SS.SSS ECHO <SybaseCartridge/5.5.8.28/Sybase_MDA-agent> INFO [TEST2 Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - Agent log: Agent started successfully.
YYYY-MM-DD HH:MM:SS.SSS ECHO <SybaseCartridge/5.5.8.28/Sybase_MDA-agent> WARN [TEST2 Socket Listener] com.quest.glue.core.jfogbank.JFogbankAgentImpl - There are no frequency settings for the table AgentError
The Foglight Agent Manager was out of memory; this was due to configuration of the Sybase agent to monitor all the table spaces of all the DB's.
This was fixed by reducing the DB's number and increasing the thresholds of the tablespaces, this collection is meant to monitor only the most significant table spaces per each DB.
