Fixes are available
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
This issue affects servers that are collective members. An incorrect error response, "Server <servername> does not exist." is received on certain operation like start/stop server. This occurs when a collective member server has been configured with useHostCredentials set to true in its hostAuthInfo stanza, but authorization credentials have not yet been set for the servers's host.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - Systems Management * * Collectives * **************************************************************** * PROBLEM DESCRIPTION: Fix incorrect error message when host * * authentication credentials cannot be * * retrieved by collective controller. * **************************************************************** * RECOMMENDATION: * **************************************************************** This issue affects servers that are collective members. An incorrect error response, "Server <servername> does not exist." is received on certain operation like start/stop server when issued from a collective controller. This occurs when a collective member server has been configured with useHostCredentials set to true in its hostAuthInfo stanza, but authorization credentials have not yet been set for the servers's host.
Problem conclusion
The code was changed to correctly report the underlying error, that host level authentication information was not found. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.7. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
To resolve the failure, disable useHostCredentials for the server or run the updateHost command to set valid credentials for the host.
Comments
APAR Information
APAR number
PI43401
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-22
Closed date
2015-08-05
Last modified date
2015-08-05
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
27 April 2022