IBM Support

PI83516: USING REFERENCE-LISTENER ALONG WITH SERVICE FACTORY CAUSES TRANSACTIONMANAGER ERRORS

Fixes are available

17.0.0.3: WebSphere Application Server Liberty 17.0.0.3
17.0.0.4: WebSphere Application Server Liberty 17.0.0.4
18.0.0.1: WebSphere Application Server Liberty 18.0.0.1
18.0.0.2: WebSphere Application Server Liberty 18.0.0.2
18.0.0.3: WebSphere Application Server Liberty 18.0.0.3
18.0.0.4: WebSphere Application Server Liberty 18.0.0.4
19.0.0.1: WebSphere Application Server Liberty 19.0.0.1
19.0.0.2: WebSphere Application Server Liberty 19.0.0.2
19.0.0.3: WebSphere Application Server Liberty 19.0.0.3
19.0.0.4: WebSphere Application Server Liberty 19.0.0.4
19.0.0.5: WebSphere Application Server Liberty 19.0.0.5
19.0.0.6: WebSphere Application Server Liberty 19.0.0.6
19.0.0.7: WebSphere Application Server Liberty 19.0.0.7
19.0.0.8: WebSphere Application Server Liberty 19.0.0.8
19.0.0.9: WebSphere Application Server Liberty 19.0.0.9
19.0.0.10: WebSphere Application Server Liberty 19.0.0.10
19.0.0.11: WebSphere Application Server Liberty 19.0.0.11
19.0.0.12: WebSphere Application Server Liberty 19.0.0.12
20.0.0.1: WebSphere Application Server Liberty 20.0.0.1
20.0.0.2: WebSphere Application Server Liberty 20.0.0.2
20.0.0.3: WebSphere Application Server Liberty 20.0.0.3
20.0.0.4: WebSphere Application Server Liberty 20.0.0.4
20.0.0.5: WebSphere Application Server Liberty 20.0.0.5
20.0.0.6: WebSphere Application Server Liberty 20.0.0.6
20.0.0.7: WebSphere Application Server Liberty 20.0.0.7
20.0.0.8: WebSphere Application Server Liberty 20.0.0.8
20.0.0.9: WebSphere Application Server Liberty 20.0.0.9
20.0.0.10: WebSphere Application Server Liberty 20.0.0.10
20.0.0.11: WebSphere Application Server Liberty 20.0.0.11
20.0.0.12: WebSphere Application Server Liberty 20.0.0.12

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Using WebSphere Liberty 17.0.0.1 on Windows, we are
    experiencing a
    problem at the server shutdown. This problem arises when we
    use
    a
    reference-listener along with a service factory in an OSGi
    blueprint
    file. All the artifacts to recreate the issue are attached.
    The
    server
    directory is also provided in the archive file.
    
    [4/30/17 13:11:14:127 EET] 0000003f
    .blueprint.container.AbstractServiceReferenceRecipe$Listener
    E
    Error
    calling listener method public void
    com.isbank.consumer.impl.$ProviderListener1882512039.unbind(
    com.
    isbank.p
    rovider.TestService)
    java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
    ssor
    Impl.jav
    a:95)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
    thod
    Accessor
    Impl.java:55)
    at java.lang.reflect.Method.invoke(Method.java:508)
    at
    org.apache.aries.blueprint.utils.ReflectionUtils.invoke
    
    ***
    Caused by:
    org.osgi.service.blueprint.container.ServiceUnavailableExcep
    tion
    : The
    Blueprint container is being or has been destroyed:
    (objectClass=javax.transaction.TransactionManager)
    at
    org.apache.aries.blueprint.container.ReferenceRecipe.getServ
    ice(
    Referenc
    eRecipe.java:241)
    at
    org.apache.aries.blueprint.container.ReferenceRecipe.access$
    000(
    Referenc
    eRecipe.java:56)
    

Local fix

  • set each of your bundles start-phase directive to not use the
    defeault, but to instead use:
    start-phase:=CONTAINER_LATE "
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Liberty feature bundle developers that use  *
    *                  OSGi Blueprint components to implement      *
    *                  their feature bundles                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: An                                      *
    *                      org.osgi.service.blueprint.container.Se *
    *                      rviceUnavailableException error can     *
    *                      occur on Liberty server shutdown for    *
    *                      feature bundles that use the OSGi       *
    *                      Blueprint specification                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Liberty enhances the OSGi Blueprint implementation with
    transaction support for each blueprint component.  If an OSGi
    Blueprint component bundle is stopped after the transaction
    services have become unavailable an
    org.osgi.service.blueprint.container.ServiceUnavailableException
    may be logged on server shutdown.
    

Problem conclusion

  • The transaction support in liberty for the OSGi Blueprint
    container has been fixed to properly handle when the transaction
    services have become unavailable during the server shutdown
    process.  This prevents the
    org.osgi.service.blueprint.container.ServiceUnavailableException
    from occurring.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 17.0.0.3.  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

    PI83516

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    CD0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-22

  • Closed date

    2017-09-25

  • Last modified date

    2017-09-25

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • RCD0 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 October 2021