Fixes are available
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
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
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
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
Stack overflow seen when moving a JAX-WS client application from WebSphere Application Server version 7 to version 8. This condition is indicated by a callstack similar to below: ... at com.ibm.wsdl.DefinitionImpl.getAllServices(DefinitionImpl.java:8 73) at com.ibm.wsdl.DefinitionImpl.getAllServices(DefinitionImpl.java:8 73) at org.apache.axis2.wsdl.util.WSDLWrapperReloadImpl.getAllServices( WSDLWrapperReloadImpl.java:903) at org.apache.axis2.wsdl.util.WSDLDefinitionWrapper.getAllServices( WSDLDefinitionWrapper.java:478) at com.ibm.wspolicy.wsdl.internal.subject.DefinitionSubjectProcesso r.<init> (DefinitionSubjectProcessor.java:60) at com.ibm.wspolicy.wsdl.internal.WSDLProcessorImpl.buildWSDLPolicy Model(WSDLProcessorImpl.java:87) at com.ibm.ws.wspolicy.wsdl.WSDLProcessor.<init>(WSDLProcessor.java :142) at com.ibm.ws.wspolicy.policyset.WSDLHelperImpl.processWSPolicyInPa ckagedWSDL(WSDLHelperImpl.java:96) at com.ibm.ws.websvcs.deployment.WASAxis2PolicySetConfigurator.asso ciatePolicySets(WASAxis2PolicySetConfigurator.java:385) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server users of * * JAX-WS Web Services * **************************************************************** * PROBLEM DESCRIPTION: java.lang.StackOverflowError occurs * * when processing JAX-WS client * * application's packaged WSDL. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem is caused by an issue in the open source WSDL4J component which is used to parse the packaged WSDL and associated schema. WSDL4J does not process circular dependencies within the WSDL and schema correctly resulting in an infinite recursion within the WSDL4J code. The reason this occurred in version 8 and did not occur in version 7 is because additional processing of WS-Policy in the client's packaged WSDL was mandated in the later version of the JAX-WS specification supported in version 8. This now mandates that WS-Addressing WS-Policy in the WSDL is honoured as a conformance requirement, therefore processing of the client's packaged WSDL is an additional step in version 8 that was not performed in version 7.
Problem conclusion
The processing of the JAX-WS Client's packaged WSDL for WSDL and associated schema should not contain circular dependencies, though the specification does not prohibit this. It is advisable to resolve the issue by refactoring the WSDL and associated schema to avoid circular dependencies. Since the processing of WS-Addressing WS-Policy in the JAX-WS client's packaged WSDL may not be desirable (since it is a change of behaviour from previous versions), that processing can now be disabled by setting the JVM system property com.ibm.ws.wspolicy.v7migration.disableClientWSDLWSPolicyProcess ing to a value of true. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.14, 8.5.5.12 and 9.0.0.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
PI75181
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-19
Closed date
2017-04-18
Last modified date
2017-04-18
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
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022