VMware Cloud Community
inforhunter
Enthusiast
Enthusiast

Tomcat.exe cause CPU Usage Spiking to 100%

about 100 Thinclients connect to VMs via VirtualCenter(U3) WebAccess.all the VMs reside on ESX 3.5(U3) host and VC on a VM.

The VC VM's CPU usage happended to spike to 100%.Tomcat.exe is the reason cause the problem.the tomcat log file increased rapidly,and be full filled with entries:"permissionDeniedException:the session is not authenticated".I noticed that,tomcat config file defined a paramater "Maxthread=150",and

I found "http-8080-processor150" in log, which means tomcat spawns up to 150 thread.reach the limitation.

I want to know is it sure that CPU usage will spike to 100% when tomcat thread reach its upper limit?

Reply
0 Kudos
5 Replies
Troy_Clavell
Immortal
Immortal

I see a lot of things going on here... My first suggestion would be to find another method of connecting to your VM's other than through the WebUI.  This is, in my opinion, why your vCenter CPU is spiking.

Secondly, you are running a very old version of both vCenter and ESX.  I would also suggest getting up  to a the minimum, U6 for vCenter and U5 for ESX.

Finally, take a look a VMware View, it may offer up a better solution that the current on you are using.

AndreTheGiant
Immortal
Immortal

As written by Troy the webAccess is not designed for this task.

There is a thread limitation, but also memory limitation.

You can try to change those parameters, but I do not think that the architecture could be much scalable.

For this purpose there are some connection broker (VMware View has its own broker).

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
godra
Enthusiast
Enthusiast

Message was edited by: Troy Clavell

Removed Comments as they were all related to vSphere Beta.  Public Forums are not  meant for beta content.  Also, due to profanity, these comments were edited as well.

Reply
0 Kudos
AndreTheGiant
Immortal
Immortal

The beta must not be used in production.

Install the 4.1 version, I suggest on a Windows Server 2008 R2.

Be sure to meet the minimum requirements: 3GB RAM and 2 cores.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
godra
Enthusiast
Enthusiast

Hi,

Thanks mate.

I ll keep that in mind. I allocated 4 GB and i saw the diff between how it worked previously

Thanks again

Reply
0 Kudos