-
Title
SAP ASE (Sybase) RS agent connection pool is closed after data collection blackout -
Description
When Sybase RS agents are placed in a data collection blackout for maintenance, and then taken out of blackout, then fail with the following error
ERROR [AGENTNAME-highPriorityPool-1] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - 2Failed to run RsCheckConnectionProcessor processor of SybaseStartUp collection. 3java.lang.RuntimeException: Failed to execute collection [SybaseStartUp], 4reason=Pool "SybaseConnectionProfile{username='USERNAME', host='HOSTNAME', port='PORT', charset='null', passw$$dencryption='true', 6retryWhitPassw$$dNoEncryption='false', JCEEncryption='true', 7enableSSL='false' }" is closed. please open a new pool -
Cause
Our agents seem to maintain a connection pool in order to avoid opening new connections each time a collection run. Once a collection ends its work it return the connection it used to the pool and this connection stays idle until a new collection will require it.
It looks like the open idle connections are being disconnected (by the server of by the firewall) . The agent 'thinks' that these connections are still open when it try to use them again.
-
Resolution
WORKAROUND
Use an alarm blackout to allow the data collections to continue in the background.
STATUS
Defect FOG-4820 has been logged for this issue and has been fixed in the 7.1 release of the Sybase SAP ASE cartridge. -
Defect ID
FOG-4820