Fixes are available
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 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
APAR status
Closed as program error.
Error description
Because a wsadmin script is used when running enablejvm in a federated environment the following message is produced. The java.version property was detected as input. This property is used as output only and has no effect on JVM initialization. Is NOT ignored and is the root cause of the DMGR not getting updated.
Local fix
Manually update DMGR Node variables.xml file to point JAVA_HOME to the proper directory. or Make the following changes to the <installroot>/bin/setupCmdLine set_conglomerates() { COMMON_JAVA_FLAGS="${JAVA_VERSION}\ ${JAVA_ENDORSED_DIRS}\ ${JAVA_ORB_PROPERTIES}\ ${OS400_DISABLE_STATIC_PGMS}\ to set_conglomerates() { COMMON_JAVA_FLAGS="${JAVA_ENDORSED_DIRS}\ ${JAVA_ORB_PROPERTIES}\ ${OS400_DISABLE_STATIC_PGMS}\
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * * on IBM i 7.1. * **************************************************************** * PROBLEM DESCRIPTION: The -Djava.version option in Websphere * * scripts on the IBM i 7.1 results in the * * a * * java message to std.err. * **************************************************************** * RECOMMENDATION: * **************************************************************** In IBM i 7.1 the Classic JDK is no longer supported. In prior OS releases the java option -Djava.version was ignored by the IBM JDK (J9). But in IBM i 7.1, J9 started issuing a message to Std.err as follows when the -Djava.version option is passed on the java invocation: The java.version property was detected as input. This property is used as output only and has no effect on JVM initialization. This is generally just a noise message and no ill effects are seen. But in certian cases, such as using the enablJVM script to update the -jvm value for a federated node, this message can cause the requested operation to fail.
Problem conclusion
Code has been modified so that we handle this case correctly. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.43, 7.0.0.21 and 8.0.0.2 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM44500
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-07-27
Closed date
2011-10-18
Last modified date
2011-10-18
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61W PSY
UP
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021