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

Fixes are available

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

[{"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.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R850 PSY

Document Information

Share your feedback

Need support?