About error messages when executing Spectrum

[MARUBUN SUPPORT]

Hi Support Team,

We have received some questions from our customers, so please answer them.

Product
Spectrum 22.2.6
CABI 7.9.2.1

The customer's environment uses Spectrum 22.2.6 and CABI 7.9.2.1.
When the user selected "Library" -> "TOP N Most Common Alarms-ALL" in CABI,
the following message was displayed and the report was not output.
* Similar messages are also output for other reports.

-----
Error Message
jsexception.error.creating.connection
Error Trace
com.jaspersoft.jasperserver.api.ErrorDescriptorException: jsexception.error.creating.connection at com.jaspersoft.jasperserver.remote.services.ReportExecution.getFinalReportUnitResult(ReportExecution.java:173) at com.jaspersoft.jasperserver.remote.services.impl.RunReportServiceImpl$2.run(RunReportServiceImpl.java:491) at com.jaspersoft.jasperserver.api.logging.util.LoggableExecutorService$1.run(LoggableExecutorService.java:84) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:750)
-----

By going to "Administrator" -> "Report Manager" -> "Jasper Integration" -> "Re-deploy" in the OneClick web administration screen,
the reports are now displayed correctly, but what could be the cause of the above error?
*The reports were displayed correctly before, and no particular configuration or environment changes have been made.
 Therefore, there is concern that the problem may recur, and the customer has asked us to identify the cause.

Also, when the problem occurs, is it okay to just go to "Re-deploy" as mentioned above as a solution?

Thanks,

[Sanyasirao Chillarige]

Hi Team,

Mostly the jar file might have corrupted hence you are getting an error

re deploying will replace the jar files which resolved the issue.

Regards

Sunny

[MARUBUN SUPPORT]

Hi Sunny-san,

 

Thank you for your reply.

If possible, please let me ask you a question.

 

>Mostly the jar file might have corrupted hence you are getting an error

 

Do you know the jar file might have corrupted in any circumstances?

Do you have any reliable information?

 

Best regrads,

Marubun