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
In some cases, the server hangs during stop. A javacore shows the following threads making no progress: - Thread "SIGTERM handler" is waiting on System.exit, which is waiting on thread "WS-ShutdownHook" - Thread "WS-ShutdownHook" is waiting for the framework manager to finish. - Thread "main" waited for framework stop before signalling framework manager shutdown, and is now waiting for server command listener to close, which is waiting on a response thread - Thread "kernel-status:start-command-response" is waiting on server start to finish The following unhelpful error is printed if the server package --include=minify command fails because the server.xml configuration file contains an <include> element that refers to a nonexistent location: [WARNING ] CWWKF0009W: The server has not been configured to install any features. The following error occurs if the JVM does not recognize the version of the Microsoft Windows operating system: CWWKE0018E: An exception occurred while launching the runtime environment: java.lang.IllegalArgumentException: WebSphere-DefaultExtension-windowsnt(unknown) The server fails to start properly if the WLP_USER_DIR environment variable contains the "," (comma) character. The following unhelpful error is printed if an extension bundle contains an invalid Bundle-Version: com.ibm.ws.kernel.boot.LaunchException: Caught unexpected exception java.lang.IllegalArgumentException: invalid version "x": non-numeric "x" The following unhelpful error can occur if a feature is removed while another component is attempting to use it: Caused by: java.lang.IllegalStateException: Located service is null at com.ibm.wsspi.kernel.service.utils.ConcurrentServiceReferenceMap .getServiceWithException(ConcurrentServiceReferenceMap.java:270)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Core * **************************************************************** * PROBLEM DESCRIPTION: Kernel error scenarios should be * * improved * **************************************************************** * RECOMMENDATION: * **************************************************************** The server can hang during stop if the feature manager start and stop threads fail to communicate. The server package --include=minify command prints error messages and other diagnostics to the package.log only rather than to the standard error stream. The kernel was attempting to use the os.name system property as a key to the Manifest object. The Manifest object does not allow keys to contain parentheses. If the JVM does not recognize the version of the Microsoft Windows operation system being used, then it will use "Windows NT (unknown)" as the os.name system property. The server script by default attempts uses the WLP_USER_DIR as an argument to the -Xshareclasses:cacheDir for IBM JVMs, but the -Xshareclasses:cacheDir option does not support the "," (comma) character. Additionally, the config runtime incorrectly splits variables on the "," (comma) character and using the first value only, which causes the log directory to log server output to the wrong directory. Finally, if the FileMonitor.MONITOR_DIRECTORIES property is a String, then it will be split on the "," (comma) character, which prevents multiple directories from being monitored. The kernel uses the OSGi Version class to parse the Bundle- Version, which throws an exception on input that is not valid. The kernel does not catch the exception, so the bundle that caused the problem cannot easily be determined.
Problem conclusion
The feature manager start and stop threads have been synchronized to ensure a hang does not occur during server stop. The server command has been modified to print only diagnostics to the package.log. All other error messages are now printed to the standard error stream as expected. The kernel has been modified to filter parentheses and other unsupported characters before using the os.name system property as a key to the Manifest object. The server script has been modified to avoid specifying the - Xshareclasses option if the WLP_USER_DIR environment variable contains a "," (comma) character. Additionally, the config runtime has been modified to avoid splitting variables on the "," (comma) character only. Finally, the callers of FileMonitor.MONITOR_DIRECTORIES property have been modified to pass an array of String to avoid splitting on the "," (comma) character. The kernel has been modified to catch errors from the OSGi Version class, and a more informative error message is now reported. The ConcurrentServiceReferenceMap SPI has been modified to report the name of the service reference that could not be obtained. 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
PI26048
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-04
Last modified date
2014-11-10
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