It's all about the answers!

Ask a question

Any bad experience with CLM 5.0.2 ifix7 ... or ifix6 ?

long TRUONG (3654116146) | asked Aug 13 '15, 8:41 p.m.

Have been having infrequent crashes & hangs  of our RTC/RRC (Tomcat/Window/SQLserver) 5.0.2. One of the advice from IBM support&SWAT is to patch with ifix6 or ifix7 to fix Lucerne indexing issues.

We installed ifix7 on TST, an env cloned from PRD though almost idle, but for the (Java) ETL jobs: RTC/RRC kept hanging after only hours, when started with Tomcat Service, even after ifix7 got uninstalled (was running fine prior to ifix7 applied). SWAT had diagnosed as out of heapspace hence memory: However when starting by the server.startup.bat RTC/RRC stayed up till we manually stop at over 24 hrs.

This morning we were provided with a very sound and logical explanation:

  • We have relative paths to indices locations, and on jts and ccm we have two relative paths each, starting from different point, which would cause full-reindexing whenever the apps are started.

For example in JTS teamserver.oproperties:

               Line 18:

               Line 61:

  • -Xcompressedrefs, found in the startup script, but is missing from the Tomcat Service Java options. This would allow indexing to be compressed and to live within its means of heapspace.

However, when -Xcompressedrefs is added to Tomcat Java options, the service would not start.   It looks like APAR IV71190 may be related.

Without the option -Xcompressedrefs, Tomcat service continue coring, heap dumping, and hanging.

Any ideas? A later version of Tomcat ?


One answer

permanent link
Donald Nong (14.5k414) | answered Aug 14 '15, 12:22 a.m.
edited Aug 14 '15, 12:23 a.m.
I don't think APAR IV71190 is related, as it appears to affect IBM Java 7 and 8 only. CLM 5.0.2 does not support these two versions of IBM Java anyway.
Also, -Xcompressedrefs should be the default setting for IBM Java 6 on Windows with -Xmx smaller than 25GB. In other words, it should not matter whether you add it or not in the Java options.
I'm not so sure about the relative paths of the indices location, although I would change them to absolute paths whenever possible (it is required for configuring Tomcat service). You can check the jts.log file and see if the paths being reported when JTS started changed at all - if you see a different path for each startup, the theory of reindexing should stand true.

long TRUONG commented Aug 14 '15, 1:59 p.m.

Thx Don,

It looks like we are back to square one ... Just when we thought we got  sound, solid, and make-sense findings towards a fix. :( 

Your answer

Register or to post your answer.