I am working on a Billing module of an Application and My client runs a 24/7 Outlet . Over a period of time (1 Week 3 days ), the tomcat Application crashes and a crash log is generated.
Need to understand how to address the issues ,since we run the same application to even Higher Billing hour clients and no crash were observed.
Our Client Runs a 16 GB RAM PC with HDD disk of 256 GB with i3 3.3GHz processor.
Fixes Tried Over by Me
set heap size for JVM in tomcat inside a setenv file (minimum 2 GB and Maximum 8 GB)
Reduced long_query_time to 3 and Increased key_buffer_size to 128M
Crash did not occur at peak billing hours
Memory Reaching limit during mysqlFTP Backup, This was causing memory Overload during peak time. So Shifted the backup time to non Peak Hour
Reduced Buffer time to 4GB (which is default), it was set to 7 GB which Caused CPU utilization to peak which has caused tomcat Crash in previous Instance
Tested Same Application In Local Instance in a Comparitively low spec PC and Pushed Same load of orders.No crash was Observed
Every Crash Occured at the interval of/between (1 week 2 days). Time Difference between last crash and the recent one .(2 Weeks). this Restart was skipped to observe changes in mySQL , when crash occures On Scheduled Restarts Improvements can be seen Steps Taken Now
Scheduled Tomcat restart before business Hours and monitor
I am working on a Billing module of an Application and My client runs a 24/7 Outlet . Over a period of time (1 Week 3 days ), the tomcat Application crashes and a crash log is generated.
Need to understand how to address the issues ,since we run the same application to even Higher Billing hour clients and no crash were observed.
Our Client Runs a 16 GB RAM PC with HDD disk of 256 GB with i3 3.3GHz processor.
Fixes Tried Over by Me [list] [*] set heap size for JVM in tomcat inside a setenv file (minimum 2 GB and Maximum 8 GB) [*] Reduced long_query_time to 3 and Increased key_buffer_size to 128M [*] Crash did not occur at peak billing hours [*] Memory Reaching limit during mysqlFTP Backup, This was causing memory Overload during peak time. So Shifted the backup time to non Peak Hour [*] Reduced Buffer time to 4GB (which is default), it was set to 7 GB which Caused CPU utilization to peak which has caused tomcat Crash in previous Instance [*] Tested Same Application In Local Instance in a Comparitively low spec PC and Pushed Same load of orders.No crash was Observed [*] Every Crash Occured at the interval of/between (1 week 2 days). Time Difference between last crash and the recent one .(2 Weeks). this Restart was skipped to observe changes in mySQL , when crash occures On Scheduled Restarts Improvements can be seen Steps Taken Now [*] Scheduled Tomcat restart before business Hours and monitor [/list]
Мобильная версия