IBM Support

PI61635: ACTIVATION SPECIFICATION CONFIG ID'S ARE GETTING MAPPED TO THE SAME ID WHILE MAKING ANY CHANGES TO THE EXISTING APPLICATION

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Activation Specification Config ID's getting mapped to the same
    ID while making any changes to the existing application.
    
    That is, changing the virtual_host of the application under
    Application-> Enterprise Application-> Application Name.
    
    For example, if there are 3 Activation Spec classes with the
    same name, the j2cActivationSpec config Id will be changed as
    follows in the deployment.xml file.
    
    <j2cActivationSpec xmi:id="J2CActivationSpec_1459276175540"
    jndiName="eis/com.ibm.sia.agent.AgentEventListener"
    name="com.ibm.sia.agent.AgentEventListener"
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175541"
    ..............
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175542"
    ...........
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175543"
    
    This happens only when customer has the same
    activationSpecClass and hence the config seems to be mapping
    the j2cActivationSpec to just one of the config IDs ie
    activationSpec="J2CActivationSpec_1459276175543".
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Activation Specification.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Activation Specification Config ID's    *
    *                      are getting mapped to the same          *
    *                      ID while making any changes to the      *
    *                      existing application                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Changing the virtual_host of the application under
    Application-> Enterprise Application-> Application Name.
    For example, if there are 3 Activation Spec class with the same
    name, the j2cActivationSpec config Id will be changed as
    follows in the deployment.xml file.
    <j2cActivationSpec xmi:id="J2CActivationSpec_1459276175540"
    jndiName="eis/com.ibm.sia.agent.AgentEventListener"
    name="com.ibm.sia.agent.AgentEventListener"
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175541"
    ..............
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175542"
    ...........
    activationSpec="ActivationSpec_1459277137958"/>
    <j2cActivationSpec
    xmi:id="J2CActivationSpec_1459276175543"
    This happens only when customer has the same
    activationSpecClass and hence the config seems to be mapping
    the j2cActivationSpec to just one of the config IDs ie
    activationSpec="J2CActivationSpec_1459276175543"
    

Problem conclusion

  • Activation Specification Config IDs are no longer mapped to
    the same ID while making any changes to the existing
    application.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11 and 9.0.0.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

    PI61635

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-29

  • Closed date

    2016-09-14

  • Last modified date

    2016-11-10

  • 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

  • R850 PSY

       UP

  • R900 PSY

       UP

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

Document Information

Modified date:
15 October 2021