This documentation supports the 20.08 version of Remedy Smart Reporting, which is available only to BMC Helix subscribers (SaaS).

To view an earlier version, select the version from the Product version menu.

Data source connection logs

Consult this topic to see the logging information of data source connections. When you enable debugging for the data source connections, the related logs are captured in the source.<datasourceID>.log file located at C:\<reportinginstalldir>\Tomcatdir\logs.

Logs for volatile data source connections

The following sample shows the entries that are logged for volatile data sources:

2020-07-31 07:41:24 NOTICE: [82345] Volatile Timeout: 3000
2020-07-31 07:41:24 NOTICE: [82345] Volatile Retries: 500

The following log samples show the retry counts that are logged when the connection drops within the time configured while enabling volatile data source setting:

Volatile Source is not available on attempt 1 (of 500)
2020-07-31 07:56:59 DEBUG: [82345] Connection Error: Cannot load connection class because of underlying exception: 
'java.sql.SQLException: ERROR (90): Cannot establish a network connection to the AR System server; Connection refused: connect '.

2020-07-31 07:57:02 DEBUG: [82345] Volatile Source re-attempt: 2 (of 500)
2020-07-31 07:57:04 DEBUG: [82345] Volatile Source is not available on attempt 2 (of 500)
2020-07-31 07:57:04 DEBUG: [82345] Connection Error: Cannot load connection class because of underlying exception: 
'java.sql.SQLException: ERROR (90): Cannot establish a network connection to the AR System server; Connection refused: connect

The following log samples show the entries logged when the connection restores within the time configured while enabling volatile data source setting:

2020-07-31 08:08:25 DEBUG: [82345] Volatile Source re-attempt: 134 (of 500)
2020-07-31 08:08:26 INFO: [82345] Created Connection[0]
Was this page helpful? Yes No Submitting... Thank you

Comments