PH54077: PLUGIN PROPAGATION DOESN'T WAIT LONG ENOUGH FOR NODE SYNCHRONIZATION IN SOME CASES

APAR status

• Closed as program error.

Error description

• When propagating a plugin-cfg.xml, the plugin repository code
  may fail to correctly update the node side plugin-cfg.xml file
  due to not waiting long enough for node synchronization to
  complete.  A trace will show messages like this one:
  
  [03/04/23 16.38.59:601 CEST] 00000570 PluginReposit 3
  PluginRepositoryWorker  Node sync did not allow plugin to
  complete the change processing.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Plugin listener doesn't wait long       *
  *                      enough for node sync to complete        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer's with large environments running node sync to remote
  nodes may see a situation where the plugin reports
  "PluginRepositoryWorker  Node sync did not allow plugin to
  complete the change processing".
  This happens because the plugin's listener is set with a 20
  second wait cycle for the node sync to complete.
  

Problem conclusion

• A new property "plgNodeSyncWaitTime" has been added to give
  customer's more flexibility.  This property will tell the
  listener how many seconds it needs to wait for the node symc
  processing to complete.  If not set, the listener will wait
  the default 20 seconds.
  
  This property is set at the node level (System Admin > Node
  agents > your-nodeagent > (Java & Process Mgt)Process
  definition > Java Virtual Machine > Custom properties).
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.24 & 9.0.5.17. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

Comments

APAR Information

• 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