IZ56255: TEP CLIENT FREEZE WHEN EXPANDING NAVIGATOR ITEMS

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• Please open an apar with the following severity and information:
  Severity: 2
  Approver:BS
  Compid:  5724C04EP Tivoli Enterprise Portal
  Abstract:TEP client freeze when expanding navigator items
  
  Environment:
    ITM 6.2.1 IF1 on Red Hat Linux - TEPS
    Client is using TEP browser client in Citrix metaframe env
  
    Do you think the latest patch applied is involved? No
  Problem Description:
    Client launches the TEP browser and as it is initializing they
    click on a navigator item - in this case a Linux agent and the
    TEP hangs indefinitely.  This only occurs if there is a
    workspace being updated when the click occurs - in our tests
    the Event Console is updating when the click is done.  The
    clinet has a lot of events that have not yet been handled.
  
  
    Explain what activity was taken that caused the observed
    action
    Click on a navigator item while the event console is updating
  
  Detailed Recreation Procedure:
    Provide a detailed step-by-step recreation procedure.
    -  Open the TEP client (happens in all clients - just using
       browser here)
    -  While the event console is loading click on a navigator
       item
    -  TEP should hang
    -  This has been recreated in the Tiv Perf lab
  
  Related Files and Output:
    Indicate log location, trace levels used, command output,
    configuration files, coredumps, etc.
    -  Logs have been provided to L3 (BS) and we have also
       recreate inhouse
  

Local fix

• It helps to remove the Situation Event Console from the main
  workspace - but not in all cases we tested.
  

Problem summary

• When opening the Tivoli Portal client and rendering the default
  enterprise workspace if there are many active events (1000+) the
  client can freeze if you attempt to expand the navigator tree
  before the initial 100 events populate in the situation event
  console.
  

Problem conclusion

• A thread race condition occurs in the portal client when we try
  to populate the initial 100 events in the situation event
  console and at the same time we try to process the events that
  augment the navigator.  Removed some code that was left behind
  from a previous release that was attempting to improve the
  performance of the initial burst of events the portal client
  receives.
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | fix pack | 6.2.1-TIV-ITM-FP0001
  

Temporary fix

• Let the Situation event console populate with the first 100
  events before attempting to expannd the navigator tree in the
  default enterprise workspace.
  

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

  TEP

• Fixed component ID

  5724C04EP

Applicable component levels

• R621 PSY

     UP