PK85713: DOCUMENT ERROR RECEIVED WHEN PERFORMING NODE SYNC AFTER APPLICATION UNINSTALL

Fixes are available

APAR status

Closed as program error.

Error description

We are receiving a DocumentIOException when performing a node
sync after uninstalling an application.

Here is a segment of the error that we see:
----------------------------------------------------------------

[3/3/09 11:37:11:206 CST]     FFDC
Exception:com.ibm.websphere. management.exception.
DocumentIOException SourceId:
com.ibm.ws.management.repository.
FileRepository.deleteInternal ProbeId:852 Reporter:com.ibm.ws.
management.repository. FileRepository@18d018d0
com.ibm.websphere.management.exception. DocumentIOException:
cells/rssregr/applications/ jwpr.wsdltypes.ear/deployments
/jwpr.wsdltypes
/jwpr.wsdltypes.war/WEB-INF/wsdl/proxy_wsdltypes1.xsd
at com.ibm.ws.management.repository. FileDocument.delete
(FileDocument.java:167)
at com.ibm.ws.management.repository. FileDocument.delete
(FileDocument.java:132)
at com.ibm.ws.management.repository.
FileRepository.deleteInternal (FileRepository.java:955)
at com.ibm.ws.management.repository.
FileRepository.updateInternal (FileRepository.java:1491)
at com.ibm.ws.management.repository. FileRepository.update
(FileRepository.java:1403)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:872)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:852)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:862)
at com.ibm.ws.management.sync. NodeSyncTask.deleteFolder
(NodeSyncTask.java:406)
at com.ibm.ws.management.sync.
NodeSyncTask.createFolderSyncRequest (NodeSyncTask.java:394)
at com.ibm.ws.management.sync. NodeSyncTask.doSync
(NodeSyncTask.java:262)
at com.ibm.ws.management.sync. NodeSyncTask.run
(NodeSyncTask.java:157)
at java.lang.Thread.run (Thread.java:735)


The application we use has a wsdl which imports several xsd
files:

Example:
<!--
WSDL to test wsdl type support when starting from a wsdl
-->
<wsdl:types>
<xsd:schema>
<xsd:import namespace= "http://
wsdltypes1.wsfvt.wsdltypes. proxy.jaxws"
schemaLocation= "proxy_wsdltypes1.xsd"/>
<xsd:import namespace= "http:// wsdltypes2.wsfvt.
wsdltypes.proxy.jaxws"
schemaLocation= "proxy_wsdltypes2.xsd"/>
<xsd:import namespace= "http:// wsdltypes3.wsfvt.
wsdltypes.proxy.jaxws"
schemaLocation= "proxy_wsdltypes3.xsd"/>

</xsd:schema>
</wsdl:types>

After installing the app, starting it, then uninstalling it,
the node sync fails on Microsoft Windows. We noticed that the
uninstall did not remove one of the files, proxy_wsdltypes1.xsd.
However, if the servers are stopped and node sync is run, then
the file is successfully deleted.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V7.0                                         *
****************************************************************
* PROBLEM DESCRIPTION: After uninstalling an application, a    *
*                      Node Sync may fail with a               *
*                      DocumentIOException                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The uninstall of an application receives warnings about WSDL
or XSD files not being deleted.  A subsequent Node Sync fails
with a DocumentIOException due to the files that were not
deleted by the uninstall.  This has only been seen on Microsoft
Windows operating systems.  Here is the callstack:
[3/3/09
11:37:11:206 CST]     FFDC
Exception:com.ibm.websphere. management.exception.
DocumentIOException SourceId:
com.ibm.ws.management.repository.
FileRepository.deleteInternal ProbeId:852 Reporter:com.ibm.ws.
management.repository. FileRepository@18d018d0
com.ibm.websphere.management.exception. DocumentIOException:
cells/rssregr/applications/ jwpr.wsdltypes.ear/deployments
/jwpr.wsdltypes
/jwpr.wsdltypes.war/WEB-INF/wsdl/proxy_wsdltypes1.xsd
at com.ibm.ws.management.repository. FileDocument.delete
(FileDocument.java:167)
at com.ibm.ws.management.repository. FileDocument.delete
(FileDocument.java:132)
at com.ibm.ws.management.repository.
FileRepository.deleteInternal (FileRepository.java:955)
at com.ibm.ws.management.repository.
FileRepository.updateInternal (FileRepository.java:1491)
at com.ibm.ws.management.repository. FileRepository.update
(FileRepository.java:1403)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:872)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:852)
at com.ibm.ws.management.repository. FileRepository.delete
(FileRepository.java:862)
at com.ibm.ws.management.sync. NodeSyncTask.deleteFolder
(NodeSyncTask.java:406)
at com.ibm.ws.management.sync.
NodeSyncTask.createFolderSyncRequest (NodeSyncTask.java:394)
at com.ibm.ws.management.sync. NodeSyncTask.doSync
(NodeSyncTask.java:262)
at com.ibm.ws.management.sync. NodeSyncTask.run
(NodeSyncTask.java:157)
at java.lang.Thread.run (Thread.java:735)

This is an example of the wsdl which imports several xsd's:
Example:
<!--
WSDL to test wsdl type support when starting from a wsdl
-->
<wsdl:types>
<xsd:schema>
<xsd:import namespace= "http://
wsdltypes1.wsfvt.wsdltypes. proxy.jaxws"
schemaLocation= "proxy_wsdltypes1.xsd"/>
<xsd:import namespace= "http:// wsdltypes2.wsfvt.
wsdltypes.proxy.jaxws"
schemaLocation= "proxy_wsdltypes2.xsd"/>
<xsd:import namespace= "http:// wsdltypes3.wsfvt.
wsdltypes.proxy.jaxws"
schemaLocation= "proxy_wsdltypes3.xsd"/>

</xsd:schema>
</wsdl:types>

After installing the app, starting it, then uninstalling it,
the node sync may fail. The uninstall did
not remove one of the files, proxy_wsdltypes1.xsd.
However, if the servers are stopped and node sync is run, then
the file is successfully deleted.

Problem conclusion

PROBLEM CONCLUSION
The file deletion fails due to open InputStreams held by the
WSDLLocator.  The fix is to implement the close() method of
the WSDLLocator interface to explicitly close all wsdl and xsd
open InputStreams.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK85713
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
2009-04-30
Closed date
2009-05-28
Last modified date
2009-05-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 APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK85713: DOCUMENT ERROR RECEIVED WHEN PERFORMING NODE SYNC AFTER APPLICATION UNINSTALL

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

R700 PSY

Document Information

Share your feedback

Need support?