Nika_Hadzhikidi

Tech Tip: Clarity 14.2:  Jaspersoft 5.6.1 performance impacted overall by Recent Items (On Premise only)

Discussion created by Nika_Hadzhikidi Employee on Feb 11, 2016
Latest reply on Feb 12, 2016 by Chris_Hackett

Affecting versions: Jaspersoft 5.6.1 and Clarity 14.2

 

Hi everybody,

 

 

We have a known issue with Advanced Reporting and the Recent Items table JIACCESSEVENT getting filled in with records. The symptoms for this would be overall slowness of the Advanced Reporting, happened overtime, and eventually high CPU on the server or similar.

 

To resolve the issue, please reset the maxAccessEventAge setting in applicationContext-events-logging.xml.

 

1. Open the file:
$JSTomcat\webapps\reportservice\WEB-INF\applicationContext-events-logging.xml 

2. Look with a text editor on line 44 in the file (shown as Line 08 in the snippet below):

<bean id="accessService" 
class="com.jaspersoft.jasperserver.api.logging.access.service.impl.AccessServiceImpl"> 
<property name="sessionFactory" ref="sessionFactory"/> 
<property name="hibernateRepositoryService" ref="unsecureRepositoryService"/> 
<property name="persistentUserResolver" ref="${bean.internalUserAuthorityService}"/> 
<property name="persistentClassFactory" ref="persistentMappings"/> 
<property name="clientClassFactory" ref="mappingResourceFactory"/> 
<property name="maxAccessEventAge" value="60"/> 
</bean> 

3. Modify maxAccessEventAge from 60 to 15

Example: <property name="maxAccessEventAge" value="15"/>

4. Save and restart the Jaspersoft Tomcat service. Repeat for all servers in cluster

 

This change has already been applied to all On Demand customers, so it's only applicable for On Premise.

 

The Impact of that change is that the Recent Items will actually get purged/deleted every 15 days instead of 60.

 

This issue is fixed in Jaspersoft 6.1 and Clarity 14.3.

 

 

Kind Regards
Nika Hadzhikidi

Outcomes