iDash slowness and reports timeout.

book

Article ID: 210727

calendar_today

Updated On:

Products

CA Workload Automation iDash

Issue/Introduction

Every morning, when generating reports, we see EEM timeout error (attached). Recycling EEM and iDash services seem to resolve the problem but it's still a reoccurring issue.

See the following authentication message in the error log:

1-02-26 10.05.38 [ERROR] http-nio-8080-exec-8:com.ca.idash.ws.controller.exceptions.RestExceptionMapper: Invalid authentication, possible session timeout
com.ca.idash.ws.controller.exceptions.RestException: Invalid authentication, possible session timeout java.util.concurrent.TimeoutException
com.ca.idash.core.security.eem.IdashEemException: EEM timeout: it is possible that more jobs satisfy the search expression
21-02-26 10.08.15 [ERROR] http-nio-8080-exec-10:com.ca.idash.core.site.JobDigestMap: getSiteDigest:failed EEM timeout: it is possible that more jobs satisfy the search expression
com.ca.idash.core.security.eem.IdashEemException: EEM timeout: it is possible that more jobs satisfy the search expression.

Getting EEM timeout while generating Autosys reports.

Environment

Release : 12.1

Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7

Resolution

In the idash.conf file increase the following value below from 100 to 180:

idash.server.eem.report.fetch.timeout

For reports the idash.server.eem.report.fetch.timeout value supersedes idash.server.eem.fetch.timeout.