Errors in logs due to data source not on Node
SummaryUser’s single application is split across nodes serving a variety of purposes.
They have a set of Real Time nodes, a Set of Background nodes and a set of Batch Nodes.
Some of these nodes use different data sources, at the Application Server level not all data sources will be on all nodes.
So if the background nodes need to make specific calls to an external DB then that Data source is only configured in Websphere for those nodes.
In Pega 7.2 version, Pega have introduced a new agent on Pega-RULESEngine. This agent is PersistSystemInfo.
This runs daily, when it runs, it cycles through all datasources and on nodes where the matching Datasource is not present it reports an Error.
This error is then picked up by Tivoli Directory Server and reported on.
They need to be able to configure this to prevent such errors being reported.
- If this agent be safely switched off? what is it exactly doing its purpose is not documented.
- If it is recording state internally then can its message not be set as a warning?
Error MessagesError - Unable to get Driver details for DB [CMISDataSource] due to exception
Steps to ReproduceDefine a datasource that is only available on some Application server nodes.
ResolutionThe solution is to log the error as "WarnForced" with error message.
To get the full stacktrace, enable debug on DatabaseInfoHandler.java. For that apply HFix-30234.
Published November 2, 2016 - Updated January 4, 2017