It's all about the answers!

Ask a question

How can one tell if ifix7 has been effectively installed into CLM 5.0.2 Windows/Tomcat ?


long TRUONG (363490129) | asked Aug 07 '15, 4:12 a.m.
edited Aug 07 '15, 4:15 a.m.
Trying to fix the funny appearance of the question, but can't 

We installed ifix7 (first time ever patching RTC) into our CLM (only RTC/RRC) 5.0.2 (1 Windows host for all apps/Tomcat/SQLserver 2012) on TST env, anticipating same implementation in PRD today. This was recommended by IBM support against our infrequent hangs of the RTC, hoping for a cure against the Lucerne indexing issues.

We have a hard time to find out if the ifix7 was effectively installed:

It does not look right: there is an ifix7 showed up " JIT - r9_20130920_46510ifx7" in App VM, but the status page on TST (with ifix7 zip in ...\server\patch) is exactly same as that on PRD (where ifix7 has not been applied, where there is no ...\server\patch folder)

 

TST

Status Summary

Application Status

Database Status Connected

Uptime  14 hours, 25 minutes

Public URI            https://rtc-web1.ent.rt.csaa.com/ccm

Diagnostics        

WARNING1 warning

VM Memory Usage

Maximum Memory Allocation      6144 MB

Current Memory Allocation          6144 MB

Free Memory      76%

Application Information

Jazz Team Server Location            Connected to: https://rtc-web1.ent.rt.csaa.com/jts

Version 5.0.2

Build Information

Change and Configuration Management - Core Libraries   5.0.2 (RTC-I20141031-0926)

Jazz Foundation - Core Libraries  5.0.2 (RJF-I20141028-1603)

Application VM

Version 1.6.0

Vendor  IBM Corporation

Name    IBM J9 VM

Details  

JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr16-20140626_204542 (JIT enabled, AOT enabled)

J9VM - 20140626_204542

JIT - r9_20130920_46510ifx7

GC - GA24_Java6_SR16_20140626_1848_B204542

 

PRD

Status Summary

Application Status

Database Status Connected

Uptime  6 days, 15 hours

Public URI            https://rtc-web1.ent.rt.csaa.com/ccm

Diagnostics        

OKOK

VM Memory Usage

Maximum Memory Allocation      8192 MB

Current Memory Allocation          8192 MB

Free Memory      37%

Application Information

Jazz Team Server Location            Connected to: https://rtc-web1.ent.rt.csaa.com/jts

Version 5.0.2

Build Information

Change and Configuration Management - Core Libraries   5.0.2 (RTC-I20141031-0926)

Jazz Foundation - Core Libraries  5.0.2 (RJF-I20141028-1603)

Application VM

Version 1.6.0

Vendor  IBM Corporation

Name    IBM J9 VM

Details  

JRE 1.6.0 IBM J9 2.4 Windows Server 2008 R2 amd64-64 jvmwa6460sr16-20140626_204542 (JIT enabled, AOT enabled)

J9VM - 20140626_204542

JIT - r9_20130920_46510ifx7

GC - GA24_Java6_SR16_20140626_1848_B204542

 

Did we read the ifix7 readme wrong, executing:

·        stop CLM (with server_shutdown.bat)

·        create ….\server\patch

·        Copy the server patch file CLM_server_patch_5.0.2.0-CALM502M-I20150704-0040.zip into the ...\server\patch directory.

·        NO unzip

·        Clean application server cache (empty …\tomcat\temp & …\tomcat\work)

·        Start Tomcat Service

 

from the below instructions:

a. Stop the CLM server.

b. Verify whether the following directory exists: <server_installation_directory>/server/patch.

               -If the directory exists, back up and remove its contents.

               -If the directory does not exist, create it.

c. Copy the server patch file CLM_server_patch_5.0.2.0-CALM502M-I20150704-0040.zip into the /server/patch directory.

d. Clean the application server cache. Follow your application server's documentation on cache cleaning. Use "To clean the application cache in WebSphere" and "To clean the application cache in Tomcat" below as a reference.

e. Start the CLM server.

 

 

To clean the application cache in Tomcat:

Remove contents from these directories under the tomcat root: temp,work.

For example, "rm -rf <server_installation_directory>/server/tomcat/{temp,work}/*" on linux.

3 answers



permanent link
long TRUONG (363490129) | answered Aug 07 '15, 4:35 a.m.
 Oops! Found the answer, couldn't be any more stupid... :)

Need to unzip the ifix7 zip to find the file CLM_server_patch_5.0.2.0-CALM502M-I20150704-0040.zip (doubled zip!) to copy into patch

Comments
long TRUONG commented Aug 07 '15, 4:53 p.m.

 Thus patched, one will find on status pages, for each app, a Build line similar to below:


The patch is active for Jazz Foundation - Core Libraries. For details about the patch, see the readme.txt file. 5.0.2 (iFix007)

Unfortunately:
  • Patched at 08:49
  • (Java)cores and (heap)dumps at 10:40
  • RTC/RRC hung (Tomcat service still running), not accessible, before 13:30 with last entries into the verbosegc.log at 13:21


permanent link
Taki Nakajo (1.1k1945) | answered Aug 07 '15, 4:29 a.m.
edited Aug 07 '15, 4:33 a.m.
It looks like the similar symtom https://jazz.net/forum/questions/204098/with-the-new-ifix007-patch-is-it-necessary-to-redeploy-the-enclosed-war-files.
Have you checked <CLM installation>/server/logs/<app>_patch.log files to see if the patch was found to install?

Comments
long TRUONG commented Aug 07 '15, 4:32 a.m.

 Thx Taki...Found own answer, see next... my own stupidity


Taki Nakajo commented Aug 07 '15, 4:34 a.m.

 oh, ok. what was wrong?


permanent link
Arun K Sriramaiah (3.2k1941) | answered Aug 07 '15, 4:31 a.m.
Hi Iong,

I would recommend you to follow the readme.txt

Please find the details below.
1. SERVER PATCH

Note: Before you install the server patch file CLM_server_patch_5.0.2.0-CALM502M-I20150704-0040.zip, verify that no other test fixes or hot fixes are installed. If other fixes are installed, contact IBM Software Support.

For a CLM deployment on a single server, complete the following steps once. For a distributed CLM deployment, complete the same steps on each server.

To install the server patch:

a. Stop the CLM server.
b. Verify whether the following directory exists: <server_installation_directory>/server/patch.
-If the directory exists, back up and remove its contents. 
-If the directory does not exist, create it.
c. Copy the server patch file CLM_server_patch_5.0.2.0-CALM502M-I20150704-0040.zip into the /server/patch directory.
d. Clean the application server cache. Follow your application server's documentation on cache cleaning. Use "To clean the application cache in WebSphere" and "To clean the application cache in Tomcat" below as a reference.
e. Start the CLM server. 
Note: For a distributed CLM deployment, complete the same steps on each server.

Regards,
Arun.

Your answer


Register or to post your answer.