Any bad experience with CLM 5.0.2 ifix7 ... or ifix6 ?
![]() 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:
For example in JTS teamserver.oproperties:
Line 18: com.ibm.team.fulltext.indexLocation=conf/jts/indices/workitemindex
Line 61: com.ibm.team.jfs.index.root.directory=indices
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
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.