Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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
The server package --include=usr command creates an archive that contains files in the wlp/lib/ directory even though it should only contain files in the wlp/usr/ directory. The server help command prints the help action without any description. The server command prints poor error messages if the jvm.options file contains an invalid line. The server start command prints an empty process ID on the IBM i platform. The server create command does not print a clear error message when a server name is specified that is not valid. The performance of the server start command is too sensitive to the version of the IBM JVM.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Core * **************************************************************** * PROBLEM DESCRIPTION: The server command needs to be * * improved * **************************************************************** * RECOMMENDATION: * **************************************************************** The following server command problems are being addressed: The server package command creates an archive that contains some files in wlp/lib/ even if the --include=usr option is specified. The server help command prints the help action without any description. The server script must process the jvm.options file without launching a JVM for advanced processing, so the error reporting is limited, but it should still be possible to diagnose basic errors. The server script internally passes a process ID or empty string to the server start logic. This empty string should be specially handled, but it is not. The server command did not print clear messages for options and server names that are not valid. Additionally, the help text did not clearly explain what characters can be used in a valid server name. Finally, the server command unnecessarily printed an exception stack trace in some cases. The server script uses two JVMs to start a server: the background server processes, and a foreground process that monitors the background server process until it has fully started. Both processes were launched with the -Xshareclasses option on IBM JVMs, but this causes contention in the shared class cache, which results in unpreditable performance.
Problem conclusion
The following changes have been made: The server package command has been modified to avoid including any files in wlp/lib/ when the --include=usr option is specified. The server help command has been modified to print a description for the help action. The server script has been modified to diagnose lines in the jvm.options file that do not begin with the "-" (hyphen) character. The server command has been modified to handle an empty process ID string that is passed internally from the server script. The server command has been modified to print clearer error messages if an option or server name that is not valid is specified. Additionally, the help text has been modified to more clearly explain what characters can be used in a valid server name. Finally, the server command has been modified to no longer print unnecessary stack traces in some cases. The server script has been modified to avoid launching the foreground process with the -Xshareclasses option with IBM JVMs. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.4. 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
PI26065
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
2014-09-19
Closed date
2014-10-14
Last modified date
2014-10-14
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:
28 April 2022