Hi,
Since the upgrade from 5.0.11 to 6.51 we have experienced a big problem with one of your application (export of statistical data from a Domino app to SQL Server using the opensource jTDS driver). What we do is to export field information from Domino once every night and the volume is around 700 documents per run. This has been working flawlessly for more than 6 month, but the problems started when we migrated to 6.51 this weekend. The actual output from the export routine looks like this (it’s an AIX box running AIX 5.2):
FATAL ERROR in native method: Out of memory when expanding local ref table beyoÉ
nd capacity
at lotus.domino.local.NotesReferenceQueue.NRelease50Sessions(Native Method)
at lotus.domino.local.NotesReferenceQueue.run(NotesReferenceQueue.java:141)
at java.lang.Thread.run(Thread.java:512)
Stack base = 0x34cad714, Stack size = -900 bytes
Fatal Error signal = 0x00000006 PID/TID/K-TID = 41260/2571/312395
Domino Halted. Type ‘quit’ to Terminate/Cleanup /opt/lotus/bin/java[1044]: 4126É
0 Killed
Do anyone of you guys recognize this cryptical error? Is this a new memory issue with the java implementation?
Kind regards
Daniel
Subject: Java Memory issue on 6.51/AIX 5.2
Hello Daniel,
try to check which process is running with the ID at the domino chrash.
Monitor your running processes. Don’t ask me how to do on AIX. We are running solaris.
Check the running processes before the crash and after.
In this case it was PID 41260.
Fatal Error signal = 0x00000006 PID/TID/K-TID = 41260/2571/312395 Domino Halted.
Regards Rico
Subject: RE: Java Memory issue on 6.51/AIX 5.2
Hi Rico,
Will definitely pass this pointer on to our unix guys so that they are prepared when (i dare not say “if”) it happens again. I personally don’t think that AIX is an optimal environment for Domino, but then again that is what we use (Intel boxes are not prioritized).
Thanks again
kind regards
Daniel
Subject: Java Memory issue on 6.51/AIX 5.2
Java is running out of memory while conversing with GC. An unusual stack, since Domino is attempting to clean up when it happens. Haven’t seen that stack before, so not sure if it’s a platform specific situation or not. The 6.x implementation is very different than R5, so memory management characteristics can vary. If you haven’t already done it, I’d recommend boosting calls to Document.recycle(), Database.recycle(), and View.recycle() in attempt to alleviate the problem.
Subject: RE: Java Memory issue on 6.51/AIX 5.2
Hi James,
It could actually be a GC issue? I have been trying to clean up every now and then (doing various recycle on objects in loops, etc) and finally issue a System.gc() call. I will try to do even more recycling and see where it leads.
Thanks
kind regards
Daniel
Subject: Java Memory issue on 6.51/AIX 5.2/Update
It sure looks lika a memory problem, but not the kind that is caused by the lack of recycle. I followed the advice from Bob B. on LooseLeaf and did instead initiaize a “remote” session on the same machine and the problems did seem to go away. Only problem is that the execution is a LOT slower this way. Will report an NSD on Monday and see where it leads.
Kind regards
Daniel