Had an issue over the weekend trying to deploy a few new war files on a tomcat server. The server is set to run with a max heap space of 1G and does not even get close to this while running. Also, said server, on amazon cloud, has the following stats:
Java 6
Tomcat 6
7.5 GB memory
4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units each)
850 GB instance storage (2×420 GB plus 10 GB root partition)
64-bit platform
I/O Performance: High
API name: m1.large
When starting the tomcat service all the WARs would be autodeployed and exploded just fine. After humming along for a few minutes the entire server would freeze and had to be hard restarted from the EC2 admin console.
So to fix this I just disabled auto-deploy in the server.xml file for tomcat. I'm wondering what the true cause of this issue was. I'll have to play around and find out.
No comments:
Post a Comment