IBM Support

PM83177: BLA STOPPED ON ALL APPLICATION SERVERS WHEN MAPPING IS CHANGED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the mapping of a Business Level Application's EBA is
    changed the application is stopped on app servers thet were not
    part of the mapping change.
     -
    The problem is seen following these steps:
     1. The EBA of the BLA is mapped to server1 and server2
     2. Select Business-level applications > blabber >
         com.ibm.samples.websphere.osgi.blabber.app_0001.eba
     3. Click Modify Targets and moved server2 from the selected box
     4. Clicked OK and save.
     5. The application is stop on server2 as expected and server1
        not as expected.
     -
    The application should not be stopped on an application that
    isn't part of the application mapping change.
    

Local fix

  • None
     -
    Keywords: app CU blas deploy module mapping business-level
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of WebSphere Application Server V8.0  *
    *                  or V8.5 that use business-level             *
    *                  applications to deploy OSGi or SCA          *
    *                  applications or to deploy shared            *
    *                  libraries.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Adding a target to or removing a        *
    *                      target from a composition unit causes   *
    *                      the composition unit to be restarted    *
    *                      on existing, unaffected targets.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Adding a target to or removing a target from a composition
    unit causes the composition unit to be restarted on existing,
    unaffected targets. This problem applies to composition units
    not backed by Java EE applications. A similar problem with
    Java EE applications was fixed with APAR PM61221.
    

Problem conclusion

  • The composition unit restart logic was enhanced to not restart
    an updated composition unit when it is reasonably possible to
    make such a determination. In particular, if changes to a
    composition unit's targets do not affect the composition unit
    running on a given server process, there is no reason to
    restart the composition unit on that server process.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 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

    PM83177

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-19

  • Closed date

    2013-04-23

  • Last modified date

    2013-07-22

  • 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:
12 January 2022