Fixes are available
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
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 one case, the user saw a stack trace like the following when there was no authority to write to the unspecified work area: java.io.IOException: Unable to create lock manager. at org.eclipse.osgi.storagemanager.StorageManager.open(StorageMana g er.java:699) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initFileManag e r(BaseStorage.java:226) at org.eclipse.osgi.internal.baseadaptor.BaseStorage.initialize(Ba s eStorage.java:160) at org.eclipse.osgi.baseadaptor.BaseAdaptor.initializeStorage(Base A daptor.java:123) In another case, the user saw a "no space" type error when the small / file system quickly filled up.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server 9.0.5.0 that use the * * managesdk command * **************************************************************** * PROBLEM DESCRIPTION: When running the managesdk command, * * unexpected errors may occur, such as * * a stack trace or unusual logging. * **************************************************************** * RECOMMENDATION: * **************************************************************** The managesdk command script passes along the USER_INSTALL_ROOT variable which is in turn used by osgi to set a logging location. There are times when USER_INSTALL_ROOT has not yet been set when entering managesdk command script, and this may cause osgi to log to locations that are not within the WebSphere directory. Some of these locations may not be suitable for osgi logging.
Problem conclusion
This APAR is correction to APAR PH09335 which was included in WebSphere 9.0.5.0. PH09335 passed USER_INSTALL_ROOT to be used by osgi to set a logging location. This APAR makes an additional change which sets USER_INSTALL_ROOT in the managesdk command script if it's not already set. This will result in osgi logging to a suitable location within the WebSphere directory structure. The fix for this APAR is currently targeted for inclusion in fix pack: - 9.0.5.1 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
PH13798
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
2019-06-26
Closed date
2019-08-15
Last modified date
2019-08-15
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
R900 PSY
UP
Document Information
Modified date:
28 April 2022