PI15488: PLUGIN SYNCHRONIZATION NOT WORKING

8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Plugin may not be synchronized when doing scripted updates and
  auto propagate.
  

Local fix

• After the plugin auto-generate function completes, do another
  node synchronization
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.0 and V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When doing scripted updates to the      *
  *                      Dmgr, the plugin isn't always updated   *
  *                      correctly                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Scripted updates using automatic plugin generation and
  propagation can trigger multiple instances of plugin
  generation.  Due to timing issues, it's possible to find
  that the final version of the plugin on a remote nodes web
  server hasn't been updated with the latest plugin-cfg.xml file.
  

Problem conclusion

• Automatic plugin generation relies on the node sync process.
  Ultimately, the plugin will get updated, but it could be at a
  later time.  Relying on that can leave a site out of sync and
  cause failures with incoming requests.  This fix introduces a
  new custom property that will force a node sync once the
  plugin generation is completed.
  
  New property name:  pluginPropNodeSync
  Values:  (true|false)
  
  This property is set at the cell level under "System
  administration > cell > custom properties"
  
  APAR PI15488 is currently targeted for inclusion in Fix Packs
  8.0.0.10 and 8.5.5.4 of WebSphere Application Server.
  

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

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R800 PSY

     UP