Hello there,
I've experienced something like that. In my case, there are two DB in the end, and a Balancer that load to them.
Speaking of the error, sometimes it came up "TimeOut" in the end-user's browser.
Because of the WebGui is an application loaded by IBM WebSphere Application Server Embedded, I went through JVM's JavaCore related to the Server Instance, and saw interesting points. Following below some of those:
- Process ID : 3778 (from file name)
- Operating System : Linux 2.6.32-642.13.1.el6.x86_64
- Processor Architecture : amd64
- Number of Processors : 16
- Java version : JRE 1.6.0 Linux amd64-64 build jvmxa6460sr16-20140626_204542 (pxa6460sr16fp1ifix-20140908_01(SR16 FP1+IV64658+IV64659))
- Virtual machine version : VM build 20140626_204542
- Just-In-Time(JIT) compiler switch, Ahead-Of-Time (AOT) compiler switch, Compiler version : r9_20130920_46510ifx7
- Garbage collector version : GC - GA24_Java6_SR16_20140626_1848_B204542_CMPRSS
- Java Heap Information
- -Xmx (Maximum Java heap size) : 256m
- -Xms (Initial Java heap size) : 50m
- -Xscmx (Java class data sharing cache size) : 50M
- Free Java heap size: 6,7 MB
- Allocated Java heap size: 256 MB
- Memory Segment Analysis
- Object(reserved) Free Memory(bytes) = 0
That's not all. Wanted to point out that this -Xmx are the same on both Servers.
Additionally, in respect of Memory Allocation, I have noticed that WebGui comes as standard in it's installation, such as Maximum, Minimum, GC and others related to.
To conclude, since the -Xmx was increased to 1024 there wasn't neither complaints or errors like before. We're still watching, but try out this approach that might be useful to you.
Thanks