Fixes are available
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
A user adds a DOM Node to a SOAPElement and then later removes the DOM Node. An exception occurs during the removal of the DOM Node. Here is sample code: SOAPHeader header = .. Node node = ... header.appendChild(node); ... header.removeChild(node); <- Exception occurs. Here is the exception that occurs. Exception in thread "main" org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does exist. at org.apache.xerces.dom.ParentNode.internalRemoveChild(Unkno at org.apache.xerces.dom.ParentNode.removeChild(Unknown Sourc at com.ibm.ws.webservices.engine.xmlsoap.SOAPElement.removeChild t.java:1552) The user's code is actually incorrect. According to the DOM specification, the user's code should capture the appended child and then use that Node in the subsequent removal. Here is the modified sample code that complies with the specification: SOAPHeader header = .. Node node = ... Node nodeAdded = header.appendChild(node); ... header.removeChild(nodeAdded); <- Success
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server V7.0 users * * of JAX-WS, JAX-RPC, or SAAJ * **************************************************************** * PROBLEM DESCRIPTION: An DOMException "NOT_FOUND" error * * occurs while using the SAAJ * * SOAPElement.removeChild method. * **************************************************************** * RECOMMENDATION: Install a fix pack containing this APAR * **************************************************************** A user adds a DOM Node to a SOAPElement and then later removes the DOM Node. An exception occurs during the removal of the DOM Node. Here is sample code: SOAPHeader header = .. Node node = ... header.appendChild(node); ... header.removeChild(node); <- Exception occurs. Here is the exception that occurs. Exception in thread "main" org.w3c.dom.DOMException: NOT_FOUND_ERR: An attempt is made to reference a node in a context where it does exist. at org.apache.xerces.dom.ParentNode.internalRemoveChild(Unkno at org.apache.xerces.dom.ParentNode.removeChild(Unknown Sourc at com.ibm.ws.webservices.engine.xmlsoap.SOAPElement.removeChild t.java:1552) The user's code is actually incorrect. According to the DOM specification, the user's code should capture the appended child and then use that Node in the subsequent removal. Here is the modified sample code that complies with the specification: SOAPHeader header = .. Node node = ... Node nodeAdded = header.appendChild(node); ... header.removeChild(nodeAdded); <- Success
Problem conclusion
The sample code supplied by the user is incorrect according to the DOM specification. However, since this is a subtle error, the SAAJ runtime is changed. The removeChild method will now inspect the child Nodes and remove a matching Node. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.15. 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
PM24330
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-10-12
Closed date
2010-10-22
Last modified date
2010-10-22
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 APP S
Fixed component ID
5724J0800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021