Fixes are available
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
In 7.0.0.9 the .pf files in the java/lib/cmm or java64/lib/cmm cannot be accessed via a call that does not supply the absolute path. However, there are several functions that can use these .pf files which do not take a file name parameter. Also, these files can be called under the covers by several different functions. This behavior was introduced in 7.0.0.9 due to a security fix added to Java (Sun bug 6631533). Some of the errors seen could be are: java.io.IOException: Cannot open file sRGB.pf at java.awt.color.ICC_Profile.getInstance(ICC_Profile.java:970) or java.lang.IllegalArgumentException: Can't load standard profile: GRAY.pf at java.awt.color.ICC_Profile$2.run(ICC_Profile.java:926) or java.lang.NullPointerException at java.awt.color.ICC_Profile.intFromBigEndian(ICC_Profile.java) at java.awt.color.ICC_Profile.getProfileClass(ICC_Profile.java:1169
Local fix
1. If the application directly calls a .pf file using the file name use the absolute path of the .pf file for the call. 2. If the application calls the .pf files indirectly please do the following: a. cd to /WAS_HOME/AppServer/java64/lib/cmm or WAS_HOME/AppServer/java/lib/cmm directory depending on if you are running in 64 bit mode or not. b. Issue the ls -E command c. The display above should show the symlinks and the actual file they reference d. The path given after the -> should be where the actual .pf file is located. However, you should check this by issuing the ls -E in the directory given for the symlink reference. e. Remove the symlink using the rm command. f. From the WAS_HOME/AppServer/java64/lib/cmm or WAS_HOME/AppServer/java/lib/cmm directory copy the real .pf file using the cp command.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: In WebSphere Application Server for * * z/OS Service Level (Fix Pack) 7.0.0.9 * * the .pf files in the java/lib/cmm or * * java64/lib/cmm path cannot be * * accessed via a call that does not * * supply the absolute path. * **************************************************************** * RECOMMENDATION: * **************************************************************** Some of the errors that could be seen are: java.io.IOException: Cannot open file sRGB.pf at java.awt.color.ICC_Profile.getInstance(ICC_Profile.java:970) or java.lang.IllegalArgumentException: Can't load standard profile: GRAY.pf at java.awt.color.ICC_Profile$2.run(ICC_Profile.java:926) or java.lang.NullPointerException at java.awt.color.ICC_Profile.intFromBigEndian(ICC_Profile.java) at java.awt.color.ICC_Profile.getProfileClass(ICC_Profile.java:1169 This is due to the .pf files at the java/lib/cmm and java64/lib/cmm locations being symbolic links pointing to files in the read-only file system.
Problem conclusion
The WebSphere configuration script which creates the symbolic links for the file system has been updated to no longer create links for the files at the java/lib/cmm and java64/lib/cmm locations. Instead, these files are copied into the configuration file system to prevent the aforementioned errors. APAR PM17433 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.13 of WebSphere Application Server for z/OS Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM17433
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-29
Closed date
2010-08-30
Last modified date
2010-11-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK61146
UP10/10/21 P F010
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
25 October 2021