Clarity

Expand all | Collapse all

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

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

    Broadcom Employee
    Posted 02-11-2016 04:12 PM

    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



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

    Posted 02-12-2016 08:23 AM

    Hi Nika,

     

    Per our install, TIBCO (TM) JasperReports Server (R) 6.1.0 Release for our 14.3 upgrade, I am seeing in the file mentioned the age max value still set to 60 and NOT 15 per your note. Can you confirm please.

    Thanks,

    Allen



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

    Broadcom Employee
    Posted 02-12-2016 08:27 AM

    Hi Allen,

     

    The value remains the same in 14.3 but the query behind are optimized, so you will not need any change in 14.3. This is specific to 14.2 customers.

     

    Regards

    Suman Pramanik



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

    Posted 02-12-2016 09:22 AM

    Thanks Suman for providing clarification on this topic.



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

    Broadcom Partner
    Posted 02-12-2016 05:27 PM

    Thanks for the tip NIka!

    NIKA HADZHIKIDI wrote:

     

    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):

    1. <bean id="accessService"  
    2. class="com.jaspersoft.jasperserver.api.logging.access.service.impl.AccessServiceImpl">  
    3. <property name="sessionFactory" ref="sessionFactory"/>  
    4. <property name="hibernateRepositoryService" ref="unsecureRepositoryService"/>  
    5. <property name="persistentUserResolver" ref="${bean.internalUserAuthorityService}"/>  
    6. <property name="persistentClassFactory" ref="persistentMappings"/>  
    7. <property name="clientClassFactory" ref="mappingResourceFactory"/>  
    8. <property name="maxAccessEventAge" value="60"/>  
    9. </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