We have blank page in Incident view while Assets and other parts are working just fine. After several minutes, Incidents view is working again. This repeats several times a day every day.
Anyone ideas about what could be wrong? No CPU usage at any time (40-60%), disk/memory ok. Moved to another DataCenter (vmware) and still the same.
Best answer by nikolai.kleiman
Hello,
Justo to update you with the status. So far so good. Seems that changes we made have fixed the issue since nobody is reporting anything π
Thank you for your assistance, you can close this thread.
Here are the inctructions from SysAid:
From ..\\SysAidServer\conf - wrapper.conf - modify Maximum Java Heap Size - wrapper.java.maxmemory= from 768*currently to 2048 ( wrapper.java.maxmemory=2048) *please create a copy of the file and the save the changes.
From ..\\SysAidServer\root\WEB-INF\conf - serverConf.xml modify <maxThreadsInPool> to 30 instead of 90.
From the same file *serverConf.xml - modify dbCPType from TomcatCP in HikariCP
From same folder, open HikariCP.proprietes and modify maximumPoolSize to 60.
After saving this changes, please restart the SysAid Server from Services.msc.
Thanks for your reply. I have contacted SysAid support via chat and they recommended to increase Maximum Java Heap size and changing dbCPType from TomcatCP in HikariCP.
I will check what can be seen on Developer tools panel when this issue happens again. This happens to all kind of users who use Incidents view (different roles, from admin to viewer).
Justo to update you with the status. So far so good. Seems that changes we made have fixed the issue since nobody is reporting anything π
Thank you for your assistance, you can close this thread.
Here are the inctructions from SysAid:
From ..\\SysAidServer\conf - wrapper.conf - modify Maximum Java Heap Size - wrapper.java.maxmemory= from 768*currently to 2048 ( wrapper.java.maxmemory=2048) *please create a copy of the file and the save the changes.
From ..\\SysAidServer\root\WEB-INF\conf - serverConf.xml modify <maxThreadsInPool> to 30 instead of 90.
From the same file *serverConf.xml - modify dbCPType from TomcatCP in HikariCP
From same folder, open HikariCP.proprietes and modify maximumPoolSize to 60.
After saving this changes, please restart the SysAid Server from Services.msc.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Love what you're seeing?? Sign in to see exclusive content and contribute to the community!