DJH
Active Member
Hello List
We have EnterpriseOne 8.10, 8.98.1.3 on Windows 2003, SQL 2005
We have recently rolled out to Web client and I have a Websphere Cluster which consists of 2 x virtual servers with 2 HTML Servers on each. We roll the client out to the user via a Windows 2008 R2 Remote App.
The Web servers each have 4GB Ram, and each JVM has a min heap size of 512 and a max heap size of 1024.
All was OK apart from the odd CPU issue where the CPU would spike for about 5 - 10 minutes on one of the Java.exe processes. I put this down to a large find somewhere on a poorly written app. As the web servers are virtual with only 1 Processor assigned our I.T Guy agreed to add an additional CPU to see if this would help with the CPU spiking issues (until we found and fixed all the problem apps).
Since we have added an additional CPU the HTML Servers CPU still spike, only now the JVM restarts itself and anyone logged into that JVM has to logout and back in again. In the SystemErr.log we see a lot of java.lang.OutOfMemoryError messages.
Tonight I plan to remove the extra processor that was added, however does anyone have any ideas as to why this would happen? Does Websphere need any setting changes to make it aware of the extra processor?
Thanks in advance
Dave
We have EnterpriseOne 8.10, 8.98.1.3 on Windows 2003, SQL 2005
We have recently rolled out to Web client and I have a Websphere Cluster which consists of 2 x virtual servers with 2 HTML Servers on each. We roll the client out to the user via a Windows 2008 R2 Remote App.
The Web servers each have 4GB Ram, and each JVM has a min heap size of 512 and a max heap size of 1024.
All was OK apart from the odd CPU issue where the CPU would spike for about 5 - 10 minutes on one of the Java.exe processes. I put this down to a large find somewhere on a poorly written app. As the web servers are virtual with only 1 Processor assigned our I.T Guy agreed to add an additional CPU to see if this would help with the CPU spiking issues (until we found and fixed all the problem apps).
Since we have added an additional CPU the HTML Servers CPU still spike, only now the JVM restarts itself and anyone logged into that JVM has to logout and back in again. In the SystemErr.log we see a lot of java.lang.OutOfMemoryError messages.
Tonight I plan to remove the extra processor that was added, however does anyone have any ideas as to why this would happen? Does Websphere need any setting changes to make it aware of the extra processor?
Thanks in advance
Dave