IBM Support

PM45480: PROBLEMS WHEN TRYING TO LOOK UP SERVICE EXPORTED FROM A CBA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem has several symptoms:
    1. Failure to import a CBA that contains a bundle that exports a
    service (used a workaround instead).
    2. Application failed to lookup a service exported by a CBA.
    3. An exception is thrown when application is restarted
    
    The problem is that the CompositeBundleArchive (.CBA) must
    define a
    CompositeBundle-ExportService: within it's COMPOSITEBUNDLE.MF
    file and
    the 'Feature Pack for OSGi Applications and
    Java Persistence API 2.0
    Version 1.0.0.3' errors when you try and install a CBA with a
    defined CompositeBundle-ExportService and then inject and use as
    part of
    a bundle within an EBA that uses the CBA as defined in the
    APPLICATION.MF.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with the Feature Pack for OSGi       *
    *                  Applications and Java Persistence API 2.0   *
    *                  installed.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Failure to inject and use an exported   *
    *                      service from a Composite Bundle         *
    *                      Archive (CBA).                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The exported service from the Composite Bundle Archive (CBA)
    wouldn't be injected and available for use as a Null
    Pointer Exception was being thrown upon discovering the
    service as no Filters were defined by the discovering bundle.
    

Problem conclusion

  • This APAR solves the above described problem.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 1.0.0.7 of the Feature Pack for OSGi
    Applications and Java Persistence API 2.0.  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

    PM45480

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-10

  • Closed date

    2012-04-19

  • Last modified date

    2012-04-19

  • 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

    JPA OSGI FEATUR

  • Fixed component ID

    5724J0857

Applicable component levels

  • R700 PSY

       UP

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

Document Information

Modified date:
29 September 2020