PM85288: FILENOTFOUNDEXCEPTION FROM LOADSTRATEGY DURING APPLICATION UPDATE

Fixes are available

APAR status

Closed as program error.

Error description

When performing an update to an application which is enabled to
JavaEE5, a step of processing the application which is
performed by LoadStrategyImpl fails with a
FileNotFoundException.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Node synchronization after              *
*                      application update may trigger a        *
*                      FileNotFoundException.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
An update to an application deployed to a cell topology may
fail with a FileNotFoundException when the application
contains annotations derived metadata.
The exception will display the following error message from
trace component "annotations" from class
ArchiveInputStreamData.  The exception stack will show calls
through types AnnotativeMetadataManagerImpl and TreeBuilder.
For example:
[13/02/05 14:27:11:088 JST] 00000010 annotations   E
ArchiveInputStreamData iterate unable to open file iterator
java.io.FileNotFoundException:
WAS_HOME\profiles\PROFILE_NAME\installedApps\CELL_NAME\APPLICATI
ON_NAME.ear\MODULE_NAME.war\WEB-
INF\classes\PACKAGE_PATH\CLASS_N
AME.class
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:123)
at java.io.FileInputStream.<init>(FileInputStream.java:83)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
ryLoadStrategyImpl.basicGetInputStream(DirectoryLoadStrategyImpl
.java:932)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.Directo
ryLoadStrategyImpl.getInputStream(DirectoryLoadStrategyImpl.java
:830)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ContainerIm
pl.primGetInputStream(ContainerImpl.java:599)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl
.primGetInputStream(ArchiveImpl.java:2021)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.FileImpl.ge
tInputStream(FileImpl.java:179)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.helpers.FileIter
atorImpl.getInputStream(FileIteratorImpl.java:77)
at
com.ibm.wsspi.amm.scan.context.ArchiveInputStreamData.iterate(Ar
chiveInputStreamData.java:208)
at
com.ibm.ws.amm.AnnotativeMetadataManagerImpl.scan(AnnotativeMeta
dataManagerImpl.java:261)
at
com.ibm.ws.amm.AnnotativeMetadataManagerImpl.scan(AnnotativeMeta
dataManagerImpl.java:222)
at
com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(Anno
tationsProcessorImpl.java:108)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl
.processAnnotations(WARFileImpl.java:302)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl
.getDeploymentDescriptor(WARFileImpl.java:248)
at
org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl
.getDeploymentDescriptor(WARFileImpl.java:178)
at
com.ibm.etools.commonarchive.impl.WARFileImpl.getBindings(WARFil
eImpl.java:760)
at
com.ibm.etools.commonarchive.impl.WARFileImpl.getStandardBinding
s(WARFileImpl.java:820)
at
com.ibm.etools.commonarchive.impl.EARFileImpl.getBindings(EARFil
eImpl.java:690)
at
com.ibm.ws.odc.cell.TreeBuilder.processWebModule(TreeBuilder.jav
a:2287)
at
com.ibm.ws.odc.cell.TreeBuilder.readApplication(TreeBuilder.java
:1972)
at
com.ibm.ws.odc.cell.TreeBuilder.readApplication(TreeBuilder.java
:1824)
at
com.ibm.ws.odc.cell.TreeBuilder.doConfigChangePostProcessing(Tre
eBuilder.java:3205)
at
com.ibm.ws.odc.cell.TreeBuilder.handleConfigChange(TreeBuilder.j
ava:3058)
at
com.ibm.ws.odc.cell.TreeBuilder.configChanged(TreeBuilder.java:3
002)
The error occurs because the processing of the application
update has two steps, with a notification occurring after the
first step and before the second step.  The first step is an
update to application resource type files (various XML files
and archive manifest files).  The second step is an update to
application binaries files (which includes classes and static
content).  Code which reacted to the update notification could
attempt to access application files before the binaries update
had been completed.  In particular, such an access is
triggered when the application contains annotations derived
metadata.

Problem conclusion

The problem was fixed by changing code that accesses
application files to use a location which reliably contains
all of the updated files of the application.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.7, and 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

Comments

APAR Information

APAR number
PM85288
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
2013-03-21
Closed date
2013-06-05
Last modified date
2013-06-05

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
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"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:
12 January 2022

Tips

PM85288: FILENOTFOUNDEXCEPTION FROM LOADSTRATEGY DURING 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

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?