PM81558: TIMING ISSUE WHILE DISABLING AUTOSYNC DURING ROLLOUT UPDATE APPLICATION DEPLOYMENT OPERATION

Fixes are available

APAR status

Closed as program error.

Error description

By default, autosync interval is 1 minute in the nodeagent
SystemOut.log:

[1/19/13 20:29:47:412 GMT+08:00] 0009abfb NodeSyncTask  A
ADMS0003I:
The configuration synchronization completed successfully.
[1/19/13 20:30:47:491 GMT+08:00] 0009ac02 NodeSyncTask  A
ADMS0003I:
The configuration synchronization completed successfully.

While updating applications using rollout update operation,the
application first gets saved to the config before the rollout
takes place. If the application is large, then it is possible to
wait for more than a minute to ensure the application is saved
to the configuration repository.

[1/19/13 20:34:19:293 GMT+08:00] 000000bb UpdateCluster 3
Waiting for applications to be saved in the config repository
...
[1/19/13 20:35:50:761 GMT+08:00] 000000bb UpdateCluster 3
Waiting for applications to be saved in the config repository
[1/19/13 20:35:51:269 GMT+08:00] 000000bb UpdateCluster 3
Applications are saved to config repository

WebSphere code disables auto sync only after the application is
saved in the configuration repository.

But that 1+ minute gap caused the application to be part of an
auto-sync before we are able to disable it.

[1/19/13 20:35:00:543 GMT+08:00] 0009ac17 FileRepositor A
ADMR0016I: User
defaultWIMFileBasedRealm/server:xxxxnodeagentmodified document
cells/XXXXCell01/applications/XXXX.ear/XXXX_war.ear.

[1/19/13 20:35:00:615 GMT+08:00] 0009ac17 FileRepositor A
ADMR0016I:User defaultWIMFileBasedRealm/server:XXXX_nodeagent
modified document
cells/XXXXCell/applications/XXXX_war.ear/deployments/XXXX_war/XX
XX.war/WEB-INF/web.xml.

[1/19/13 20:35:00:658 GMT+08:00] 0009ac17 FileRepositor A
ADMR0015I:
User defaultWIMFileBasedRealm/server:x XXX_nodeagentcreated
document
cells/XXXXCell/applications/XXXX_war.ear/deltas/XXXX_war/delta-1
358598600168.

The APAR is created to change the order of logic to narrow the
timing window for the new auto synchronization to kick off.

KEYWORDS: App Deploy updateAppOnCluster WSAS roll-out automatic

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server versions 6.1, 7.0, 8.0 and 8.5.      *
****************************************************************
* PROBLEM DESCRIPTION: If an automatic configuration           *
*                      synchronization is enabled and a        *
*                      rollout update operation has been       *
*                      initiated, an undesired configuration   *
*                      synchronization may occur and cause     *
*                      applications to be down.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
While running a rollout update after performing an application
update operation, a new configuration synchronization between
a deployment manager and all its nodes is started
automatically and includes the changes from the application
update operation. This causes an outage of the application.

Problem conclusion

The code has been corrected to reduce the timing window where
a new automatic node synchronization is started during a
rollout update.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.47, 7.0.0.29, 8.0.0.7 and the fix pack
following 8.5.0.2.  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
PM81558
Reported component name
WEBS LOAD BALAN
Reported component ID
5724H8811
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-29
Closed date
2013-03-11
Last modified date
2013-03-11

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
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":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM81558: TIMING ISSUE WHILE DISABLING AUTOSYNC DURING ROLLOUT UPDATE APPLICATION DEPLOYMENT OPERATION

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?