Problem with JVM and Domino 7 and SLES 10

HCL Domino Domino Forum
1

I just managed to install our new production server to Suse Linux Enterprise Server 10 / Domino 7.0.2 environment.

There is still one major problem to solve: CPU Utilization rate is 100%, the process “runjava” is consuming all the CPU-time.

The same codebase worked perfectly in Domino 6.5.5 / SLES 8 environment but the Domino 7 / SLES 10 has fatal problems.

Also there is a problem shutting down the server with domino stop-script. It is halting when the HTTP-server should be stopped.

Any idea? Any wise guesses? Any place to get support?

Thanks for you valuable help,

Petja

2

Subject: Problem with JVM and Domino 7 and SLES 10

Hello Petja,

If the problem truly lies with Java garbage collection, then I won't be able to offer any assistance with that.  But I may be able to help isolate if it is truly the problem or not.

Does Runjava consume 100% of the CPU right after the process starts or does it happen after some period of time? One thing that I would check is to see how many probes Runjava/ISpy is running. Do do that look in your events4.nsf. There a couple of places to check. The first is the older style probes under Event Generators\ TCP Server or Mail Routing. The other place would be under DDM Configuration \ DDM Probes \ By Type. Look for things like Messaging \ SMTP Port Health or NRPC Routing State or Message Retrieval TCP Port Health or Directory \ LDAP TCP Port Health. If you have an unusually large number of probes configured, it might be causing an issue. One idea would be to disable all of those probes and then just turn 1 on and see what happens. If changing the number of probes that ISpy runs doesn’t affect anything, then it would indicate that the problem really is with the Java garbage collection.

Regards,

                   Mark
3

Subject: Problem with JVM and Domino 7 and SLES 10

I debugged the server with setting DEBUG_ISPY=2 in notes.ini

The CPU-load goes to 100% when following task is started:

13.11.2006 03:54:45 PM RunJava JVM: Mon Nov 13 15:54:45 EET 2006 ISpy: Running garbage collector.

So there seems to be problem with Java garbage collector. Any ideas how to fix this problem?