Return
-
Title
Users are crashing the Stat client, causes agent not to function properly until it's get restart. -
Description
Users who either select large criteria set either on purpose or by accident are crashing the STAT agents. Is there a way to eliminate this problem from happening? I currently have the java heap seizes set fairly high, this has helped minimize the issue but for larger reporting needs it does not keep the agents from crashing. -Xms1024m -Xmx1024m -XX:MaxPermSize=1024m -
Resolution
WORKAROUND:1. Go to Maintenance | Security Settings | User Maintenance and locate the user.2. Locate a column called rpt access. If the user have rpt access set to 99 then that's mean they have access to all reports. Enter 0 if you do not want the user to have access to any report at all.3. Filter out the criteria so that the report will be smallerSTATUS:We will address this issue to 5.8.1. Unfortunately we rely on third-party tool (Jasperreports) that has a problem with generating huge report. In 5.8.1 we will introduce global parameter - max number of rows for report. If report request exceeds max number of rows the there will be user-friendly error to put additional criteria to a filter to decrease the number of retrieved rows. That should prevent Central Agent from crashing. -
Defect ID
STAT-1381