Fixes are available
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
Error description
During the migration from v8 to v9, WASPostUpgrade for managed node failed with the following message. ------------------ MIGR0464E: Failed to stop prior release nodeagent. ------------------ In the log, we see the following error stack. ------------------ 00000001 DisableOldEnv 1 Could not stop old Server: java.lang.NullPointerExceptionat at java.util.Hashtable.putAll(Hashtable.java:579) at com.ibm.ws.migration.utility.Connection.retrieveSecurityInformat ion(Connection.java:210) at com.ibm.ws.migration.utility.Connection.retrieveConnectionInform ation(Connection.java:153) at com.ibm.ws.migration.utility.Connection.retrieveAdminClient(Conn ection.java:59) ------------------ In the source env, FIPS was enabled with SP800-131. Thus, the useFIPS and protocol was changed and FIPSLevel was added in ssl.client.props like the follows. com.ibm.security.useFIPS=true com.ibm.websphere.security.FIPSLevel=SP800-131 com.ibm.ssl.protocol=TLSv1.2 After the failure, we noticed the following wrong line was generated in the ssl.client.props in the target profiles. ------------------ #MIGR0371I: The name-value pairs that existed in the old file are not found in the new file. com.ibm.websphere.security.FIPSLevel=SP800-131com.ibm.ssl.alias= DefaultS SLSettings ------------------
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Configuration Migration Toolkit * **************************************************************** * PROBLEM DESCRIPTION: ssl.client.props has multiple * * properties on one line after migration * **************************************************************** * RECOMMENDATION: * **************************************************************** After migrating a profile from an older release of WebSphere to one of the affected releases, two lines in the ssl.client.props file are sometimes concatenated. In most cases, this is harmless, with only a blank line being lost. However, problems can arise of two properties are placed on one line. Possible errors are too various to attempt to list, but would likely revolve around ssl.client.props in some way. In particular, a reliable way to encounter this issue in a damaging form is to enable the useFIPS parameter and specify the FIPS property. This will usually result in two actual parameters in the file becoming concatenated. This problem occurs because the migration code related to ssl.client.props emits the new file in sections, but does not leave a trailing newline character at the end of sections.
Problem conclusion
Migration was adjusted to always ensure sections of ssl.client.props are separated by a newline character, ensuring lines are not concatenated. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.14 and 9.0.0.8. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Manually edit the file to separate the concatenated lines.
Comments
APAR Information
APAR number
PI95217
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-03-14
Closed date
2018-05-03
Last modified date
2018-05-03
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
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022