Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
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.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
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.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
A NoClassDefFoundError on the com/ibm/ws/runtime/util/utilHanderClass was logged in the Thin Client launched via Java Web Start (using .jnlp file) WSWS3400I: Info: unexpected exception. Throwable occurred: java.lang.NoClassDefFoundError: com/ibm/ws/runtime/util/utilHandlerClass at com.ibm.ws.runtime.util.URLHandlerFactory.createURLStreamHandler (URLHandlerFactory.java:139) at java.net.URL.getURLStreamHandler(URL.java:1119) at java.net.URL.<init>(URL.java:584) at java.net.URL.<init>(URL.java:476) at java.net.URL.<init>(URL.java:425) at com.sun.deploy.util.URLUtil.checkTargetURL(URLUtil.java:645)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server who launch client from Java * * Web Start * **************************************************************** * PROBLEM DESCRIPTION: java.lang.NoClassDefFoundError is * * thrown for * * com/ibm/ws/runtime/util/utilHandlerClas * * s * **************************************************************** * RECOMMENDATION: * **************************************************************** Provide a switch using Java system property to skip creating WebSphere Application Server's own https URL Stream Handler. There was a change with IBM SDK SP9 FP1, the Java code was updated to increase security. When WebSphere tries to create its own https stream handler, a URL stream handler is loaded from specified URL location which now requires another URL stream handler again. This results in recursive call and cause stack overflow. This issue has been seen only when the Application Server client is launched using Java Web Start. Earlier, the Application Server needed to create https stream handler. Now that Java provides default https Stream Handler, the Application Server can provide option not to create its own handler to keep from this NoClassDefFoundError. To skip creating the https stream handler, following Java System property needs to be set to "false". Java System property: com.ibm.websphere.ssl.provider.create.https.handler Default value : true
Problem conclusion
The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.31, 8.0.0.7, 8.5.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
Inside application code, load the class explicitly in the code prior to the error. Class.forName("com.ibm.ws.runtime.util.utilHandlerClass");
Comments
APAR Information
APAR number
PM85252
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-03-20
Closed date
2013-06-25
Last modified date
2013-06-25
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
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
12 January 2022