Currently, the product is not certified to run the 1.4.x version of the JVM. This is in the release docs.
I have several clients who are running 6.01. One client had the IBM JRE 1.3.0 installed (have no idea how or why.) I ramped the system over to the Sun JDK 1.3.1_07 for Windows.
In addition to the switch of JVMs as noted in previous posts, there are a couple of tuning tips that you should try out:
- Make the memory settings the same:
This will allocate all the available memory upfront and in the long run, you will be happier with the performance.
- Set a “-server” switch in the server.bat file as well:
set JAVA_RUN=%JAVA_EXE% -server %JAVA_MEMSET%
This is further down in the server.bat file. THIS WILL NOT WORK FOR THE IBM JRE and may not work with any JRE. I always use the JDK so cannot note if it will run correctly.
A quick way to test which JVM you are using, is to click on the “ABOUT” link in the Admin console. It will provide you with the path to the JRE/JDK along with your entire path with all jars, etc.
In the line noted above, set JAVA_RUN=%JAVA_EXE% -server %JAVA_MEMSET%
if you replace the “-server” switch with “-version” and then run the server.bat at console (WINDOWS), it will display the version of the JVM and then exit. You will type:
server.bat -log none -debug 6
The window will display the Java Virtual Machine info. Hope this helps.
- Create a java service called “runGarbage”. Make it in a package/interface that you plan to keep around for some time.
In the Java service, type in this line:
That’s it. After you save it, create a scheduler to run repeatedly every 2 - 5 minutes. Look at the memory meter, it will flatten out over time. This has a higher priority then the gcMins setting in the server.cnf file.