JasperReports Server (JRS) version 7.5+ Performance Issue

Since JRS version 7.5, the purge job for access events has been changed from daily at 1 AM to every hour of the day. Refer to ../WEB-INF/applicationContext-events-logging.xml

<bean id="accessEventPurgerTrigger" class="com.jaspersoft.jasperserver.api.engine.scheduling.quartz.JSCronTriggerBean">
<property name="jobDetail" ref="accessEventPurgerJob"/>
<property name="cronExpression" value="0 0 * * * ?"/>
</bean>

This hourly purge job has caused the system to pulse when conducting the jiaccessevent table clean up affecting users to perform JRS requests in their production system. The reason for such change is unknown at this time. We have filed a report to address this defect internally referenced as JS-65316. This hourly job has a huge impact on the system availability during the operating hours when many concurrent users are using the system.

To avoid this issue at the present time, we suggest users to use the JRS 7.2 version setting to avoid the impact on the system availability during the operating hours.

<bean id="accessEventPurgerTrigger" class="com.jaspersoft.jasperserver.api.engine.scheduling.quartz.JSCronTriggerBean">
<property name="jobDetail" ref="accessEventPurgerJob"/>
<property name="cronExpression" value="0 0 1 * * ?"/>
</bean>

================================

TTC-20220222-2087096