IBM Support

PM85288: FILENOTFOUNDEXCEPTION FROM LOADSTRATEGY DURING APPLICATION UPDATE

Fixes are available

8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM85288

Modified date: 05 June 2013