How to debug Operator Console page slowness using Jasperserver debug logging option

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

In the case where the Operator Console CABI Home page and/or other pages are loading slowly, here are instructions for enabling debug for the JasperServer to expose the backend SQL queries when the pages are trying to load.

Environment

- UIM 9.20 or higher

Resolution

As a privileged user, browse to the web page http://<hostname>:8080/cabijs/log_settings.html

Login to cabi, and go to Manage Server Settings > Log settings and change the ‘SQL query executor’ setting to DEBUG as shown below and then reproduce the slowness, for example by accessing the Home page via a fresh web page before anything is cached:

The resultant debug log file will be stored down path such as:

Nimsoft\probes\service\wasp\webapps\cabijs\WEB-INF\logs\jasperserver.log

Additional Information

If you don't see any debug information in the jaspersoft.log, please refer to this article:

CABI (Jaspersoft) debug option for logging is not working
https://knowledge.broadcom.com/external/article/206816/cabi-jaspersoft-debug-option-for-logging.html

Alternatively, if you need to set it manually:

Depending on the version of JasperServer you are using, you should find this already appears in log4j.properties:

### JasperReports loggers
#log4j.logger.net.sf.jasperreports.engine.query.JRJdbcQueryExecuter=debug

Uncomment it and you should be get what you need in the log.

Please note that this approach requires restarting the JasperReports Server.

https://community.jaspersoft.com/wiki/log4jproperties-jasperreports-server

To enable timings for the query/queries in the jasperserver.log, please refer to:

Configuring System Logs

https://community.jaspersoft.com/documentation/tibco-jasperreports-server-administrator-guide/v60/configuring-system-logs

As per the instructions for configuring the logs, check the page.

You can add the logger name to generate the query timings so you can see which query/queries is taking the longest or for instance simply longer, e.g., greater than a few seconds.

Timing for SQL queries run for reports-> JsControlledJdbcQueryExecuter

- Logs the time it takes a query run by the SQL query executer to return data to a report.