Potential performance impact after applying Image Services / Image Services Toolkit Fix Packs 4.1.2 FP17, 4.2.0 FP6 or FP7 on Unix servers

Content

Cause:

A change to the process /fnsw/bin/timeoutmonitor made in IS/ISTK 4.1.2.17 and IS/ISTK 4.2.0.6 can use more CPU depending on the usage of your system.

Solution:

This problem is corrected in 4.1.2 FP18 and 4.2.0 FP8

Workaround:

If the Fix Pack can not be immediately applied, use the GA version of timeoutmonitor released in a prior Fix Pack of the release: IS 4.1.2.16 and below or IS 4.2.0.5 and below.

For IS 4.1.2,

• Verify the stamp of the backup copy located in /fnsw/hfp/backup/fnsw/bin matches the GA version 4.1.2.69(x). The number in (x) will be different for every platform. Here is a sample stamp of timeoutmonitor on AIX.


system 4.1.2.69(1) (lib, Fri Jul 10 15:44:25 2009)
developer 4.1.2.0.0 (lib, Fri Jul 10 15:44:24 2009)
SubSys: mv, Rel_type: rel_aixos, SCR#: 351814, mode: 100755, size: 118264
• Copy the /fnsw/hfp/backup/fnsw/bin/timeoutmonitor to /fnsw/bin
• Set permissions using fn_setup

• Verify the stamp of the backup copy located in /fnsw/hfp/backup/fnsw/bin matches the GA version 4.2.0.22(x). The number in (x) will be different for every platform. Here is a sample stamp of timeoutmonitor on Solaris.


system 4.2.0.22(6) (userid 46246, Fri Mar 25 10:19:28 2011)
developer 4.2.0.0.0 (userid 46246, Fri Mar 25 10:19:25 2011)
SubSys: mv, Rel_type: rel_solaris, SCR#: 392790, mode: 100755, size: 97832

• Copy the /fnsw/hfp/backup/fnsw/bin/timeoutmonitor to /fnsw/bin
• Set permissions using fn_setup
  

Note - If you upgraded from IS 4.2.0 FP6 to FP7 the backup copy of timeoutmonitor will contain
the problem. You will need to obtain the GA version from Fix Central or a 4.2.0 system
on FP5 or below.