IBM Support

PH03710: ANNOTATION SCANNING INCLUDE-FILTERS NOT WORKING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PI25329: ADD INCLUDE OPTIONS FOR ANNOTATION FILTERING.
    https://www-01.ibm.com/support/docview.wss?uid=swg1PI25329
    
    added an option to allow you to specify which Java archives and
    Java packages are to be scanned for annotations.  This no
    longer works as of 8.5.5.14.   For example, suppose your
    application contains JARs A, B and C, and you specify an
    include filter of just A. Only A should be scanned.  However,
    in 8.5.5.14, A, B and C will be scanned.   Similarly, the
    include-filter for Java packages isn't working.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5 and V9.0 who use                *
    *                  include-filters to reduce annotation        *
    *                  scanning                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Packages that are not specified in an   *
    *                      include-filter are still being          *
    *                      scanned for annotations.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server traditional performs multiple
    annotation scans during application start.  These scans are
    performed by multiple components.  It was found that one
    component does not properly honor the include-filter for
    packages which causes it to scan packages that should not be
    scanned.
    The include filter is described here:
    https://www-01.ibm.com/support/docview.wss?uid=swg1PI25329
    There are multiple ways to specify the include filter.  The
    filter is only not working when it is specified in the
    MANIFEST.MF file of an archive.
    It is difficult to detect the problem is happening without
    trace, since the only symptom is that the application takes
    longer to start than it should. How much longer, depends on the
    application and the filter specified.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH03710

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-05

  • Closed date

    2018-10-15

  • Last modified date

    2018-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

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

Document Information

Modified date:
28 April 2022