PI10197: DOMEXCEPTION SHOWING HIERARCHY_REQUEST_ERR DURING AN APPLICATION UPDATE.

Fixes are available

APAR status

Closed as program error.

Error description

Particular XML text can cause application updates to fail with
a DOMException showing the keyword HIERARCHY_REQUEST_ERR.  The
exception includes the text "An attempt was made to insert a
node where it is not permitted."  The exception is thrown by
class CoreDocumentImpl from class DOMUtilities.

Local fix

Uninstall the application and reinstall (the problem only
occurs on an update).

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5.                       *
****************************************************************
* PROBLEM DESCRIPTION: Application update fails with           *
*                      DOMException showing                    *
*                      HIERARCHY_REQUEST_ERR.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Particular XML text can cause application updates to fail with
a DOMException showing the keyword HIERARCHY_REQUEST_ERR.  The
exception includes the text "An attempt was made to insert a
node where it is not permitted."  The exception is thrown by
class CoreDocumentImpl from class DOMUtilities.

Problem conclusion

During application update processing, updates may be made
to XML metadata, for example, web.xml, ejb-jar.xml, and
application.xml.  Updates to XML metadata are made using
intermediate parse nodes, possibly requiring the addition
and removal of parse nodes.

The problem occurred because the code which removed parse nodes
iterated across the nodes which were to be removed while
removing those node.  That resulted in only a subset of the
necessary nodes from being removed, and leaving the hierarchy
of nodes in a non-valid state.  Later steps to add nodes
detected the non-valid hierarchy of nodes and threw a
DOMException showing the HIERARCHY_REQUEST_ERR.

The problem was fixed by an update to the node removal
code: Before removing nodes, a temporary collection of
those nodes is created.  When removing nodes, iteration
is performed on the temporary collection instead of on the
collection from which the nodes were being removed.  All
necessary nodes are removed, and the hierarchy of nodes is kept
in a valid state.

APAR PI10197 is currently targeted for inclusion in Fix Packs
8.0.0.10 and and 8.5.5.4 of 8.5.5.4 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
PI10197
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-23
Closed date
2014-07-28
Last modified date
2014-07-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

R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI10197: DOMEXCEPTION SHOWING HIERARCHY_REQUEST_ERR DURING AN APPLICATION UPDATE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?