Tomcat crashed by "out of Memory" under the lowest loadlevel period
Submitted by corel123 on Tue, 12/04/2005 - 08:00.
java
I usually update the worksystem on the morning of Monday, then go for routine weekly meeting. Update on Morning, means usually lowest SOHO partner working online, either the lowest audience in normal view. However, as long as I did the second or the third time, I always got the machine crashed after I update the server before I complete my meeting at office.
The lastime sounds some unknown clearly bugs in the loop tags, yes! loops'bug can did worst for the system, and, I cost one week for stress test on the system, ensure the system can be work fine. And howabout this time? I just updated the apache rewrite, almost nothing did on the jsp/tags/java coding, it failed! furthermore, even I reboot the system pass through tend times of the stress rather than morning had, the system just stand strong? who can explain the situation for me? I just explain that, We are live in matrix!
I check the logs at night, and found it seems cause by "Run out of Memory" Exception, then set xms/xmx opts to env, I thought the jsp sever as tomcat could work more robust than before. In the update, I also bugged one empty source error from the pages, which alwasy cause doubht download from the websites. I have counted several times accessed to the worksystem every day, but I did not know exactly how much it caused by this bug. The monday counts decreased by the crash, I can traced the new counts for days. Now that it seems almost one third, or one fourth, almost that.
However, why the tomcat crash under the lowest access level by "out of memory", still under cover.
A
The lastime sounds some unknown clearly bugs in the loop tags, yes! loops'bug can did worst for the system, and, I cost one week for stress test on the system, ensure the system can be work fine. And howabout this time? I just updated the apache rewrite, almost nothing did on the jsp/tags/java coding, it failed! furthermore, even I reboot the system pass through tend times of the stress rather than morning had, the system just stand strong? who can explain the situation for me? I just explain that, We are live in matrix!
I check the logs at night, and found it seems cause by "Run out of Memory" Exception, then set xms/xmx opts to env, I thought the jsp sever as tomcat could work more robust than before. In the update, I also bugged one empty source error from the pages, which alwasy cause doubht download from the websites. I have counted several times accessed to the worksystem every day, but I did not know exactly how much it caused by this bug. The monday counts decreased by the crash, I can traced the new counts for days. Now that it seems almost one third, or one fourth, almost that.
However, why the tomcat crash under the lowest access level by "out of memory", still under cover.
A