IBM Support

PI23342: DEPLOYING APPLICATION WITH JSP PRECOMPILE OPTION ISSUES ERROR "GETZIPFILE FILE NOT FOUND".

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When deploying an Enterprise Application when the option
    "Precompile JavaServer Pages files" enabled the following
    errors are seen in the Deployment Manager's (DMGR)
    systemout.log:
    [8/6/14 8:45:07:264 EDT] 000000a0 wtp           E
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipFile
    LoadStrategyImpl getZipFile File not found.
     -
    [8/6/14 8:45:07:265 EDT] 000000a0 wtp           E
    org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipFile
    LoadStrategyImpl describeFile Describing file associated with
    ZipFileLoadStrategy
    [ Error case - getZipFile() file not found ]
     -
    The deploy completes but the errors are seen in the log.
    

Local fix

  • Without enabling "Precompile JavaServer Pages files" the errors
    are not seen.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All JAX-WS Web Services users of IBM        *
    *                  WebSphere Application Server                *
    ****************************************************************
    * PROBLEM DESCRIPTION: "File is null" exception reported       *
    *                      during ear installation if              *
    *                      "Precompile Java Server Pages" is       *
    *                      enabled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CompileJSP task closed EAR which was opened during
    validateAppTask, that meant it deleted related temp files. When
    ServicesIndexServerTask started to run and tried to
    "getWsdlLocator", it found the files did not exist there and
    the exception was thrown.
    

Problem conclusion

  • To fix the issue, buildEndpoint event was moved from
    ServicesIndexServerTask to validateAppTask. During
    ServicesIndexServerTask running, it would not buildEndpoint
    anymore and no "getWsdlLocator" would be invoked. To use this,
    users should set com.ibm.ws.websvcs.prebuildendpoints=true as
    jvm property.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.10 and 8.5.5.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

    PI23342

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-06

  • Closed date

    2014-10-15

  • Last modified date

    2014-10-15

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022