PM31979: CONTENT ARE NOT SYNCHRONIZED BETWEEN CLUSTER NODES

6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
7.0.0.2 Download: WebSphere Portal and WCM V7.0 fix pack 2
Fixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes

APAR status

• Closed as program error.

Error description

• WCM content is not updated on one of the cluster member. This
  makes the data inconsistent.
  
  The fix resolves this issue.
  

Local fix

Problem summary

• This APAR is concerned with Navigator components only. The
  scenario is as follows
  
  1. Set up a clsuter with two nodes. The cluster must also be the
  subscriber in a syndicator-subscriber pair. For convenience of
  testing, you can syndicate to one of the nodes (say , NodeA) in
  the cluster.
  2. Create a navigator which displays some items and syndicate it
  to the cluster. Make sure you can view it correctly by hitting
  both nodes of the cluster directly.
  3. Now clear the navigator cache on NodeA only by running the
  clearcache.jsp or by restarting the node. Make sure you do not
  render the navigator now on either nodes.
  4. Now make an update to the navigator results on the syndicator
  and let the syndication go through. So we basically want NodeA
  to process this syndication update when its navigator cache is
  empty.
  5. Wait for few minutes (to ensure the cache has been
  replicated) and render the navigator on NodeB.
  

Problem conclusion

• The cache removal messages are now sent even if the cache on
  NodeA ia empty.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R61C PSY

     UP

• R700 PSY

     UP