Fixes are available
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
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
After enabling HPEL for a server, while at the same time disabling (unchecking) text logging under "Configure HPEL text log", the server reported the following exception when restarted: java.lang.IllegalArgumentException: Specified location can't be used as a log repository: /tmp/xyz at com.ibm.ws.runtime.mbean.HPELControlServiceMBean.verifyOwners hip(HP ELControlServiceMBean.java:113) at com.ibm.ws.runtime.component.RASImpl.boot(RASImpl.java:379) at com.ibm.ws.runtime.WsServerImpl.bootLoggingServices(WsServerI mpl.java:391) ... Where /tmp/xyz is a directory specified on the "Configured HPEL text log" panel. The path /tmp/xyz does not exist and have not been yet created because text log was never enabled. However, the code is still looking at this path even though it is not needed.
Local fix
1 - manually create the HFS path that text logging needs/expects OR 2 - a. In the admin console, enable text logging under "Configure HPEL text log", b. Save, synchronize and restart the server. This will cause the path to be created. c. Go back to admin console to disable the text logging. d. Save, synchronize and restart the server.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V8.5 and V9.0 * **************************************************************** * PROBLEM DESCRIPTION: Fail to start server after enbaling * * HPEL text log * **************************************************************** * RECOMMENDATION: * **************************************************************** Server fails to start after switched to HPEL logging mode with HPEL Text logging disabled but configured the text log directory to an non-exist directory An IllegalArgumentException is logged in the server native log for invalid text log directory. For example, java.lang.IllegalArgumentException: Specified location can't be used as a log repository: /tmp/xyz at com.ibm.ws.runtime.mbean.HPELControlServiceMBean.verifyOwners hip(HP ELControlServiceMBean.java:113) at com.ibm.ws.runtime.component.RASImpl.boot(RASImpl.java:379) at com.ibm.ws.runtime.WsServerImpl.bootLoggingServices(WsServerI mpl.java:391)
Problem conclusion
We have added a condition check to see whether the HPEL Text logging is enabled before verifing the ownership of the test log directory to aviod the IllegalArgumentException. If the HPEL Text logging is enabled and the text log directory doesn't exist, it will be automatic created. APAR PI66291 is currently targeted for inclusion in Fix Packs 8.5.5.12 and 9.0.0.3 of WebSphere Application Server. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 In addition, please refer to URL: http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack PTF information.
Temporary fix
Comments
APAR Information
APAR number
PI66291
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-07-21
Closed date
2016-11-28
Last modified date
2016-11-28
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
04 May 2022