IV64671: DISPLAYING PHYSICAL TOPOLOGY TAKES A VERY LONG TIME.

APAR status

• Closed as program error.

Error description

• The method findStorageSubSystemsInBusApp is taking a long time,
  in this case, 20 minutes. One of it's algorithms generates
  redundant getAllObjectAttributes on each Computer System
  connected to the StorageSubSystem.
  
  The algorithm has been optimized to remove those redundant
  calls.
  
  In the log when this happend you will see the call to this
  method and then a long time later the return(or not return at
  all). For example, note the time difference here;
  
  2014-08-25 15:21:20,208 ViewManager [RMI TCP
  Connection(488)-1.2.3.4]  DEBUG finder.CustomNodeFinderImpl -
  executeCustomNodeFinder(finderClassName=com.collation.proxy.view
  mgr.finder.FCSwitchStorageSubSystemFinder,
  finderMethodName=findStorageSubSystemsInBusApp,
  view=ViewDescriptor [type: Graph, view name: Application
  Physical Infrastructure Topology, version: 0, referring
  component id (option
  al):
  
  ..
  
  
  2014-08-25 15:42:10,816 ViewManager [RMI TCP
  Connection(488)-1.2.3.4]  DEBUG finder.CustomNodeFinderImpl -
  executeCustomNodeFinder() - Custom finder
  com.collation.proxy.viewmgr.finder.FCSwitchStorageSubSystemFinde
  r.findStorageSubSystemsInBusApp returned no results
  

Local fix

• NA
  

Problem summary

• The method findStorageSubSystemsInBusApp is taking a long time,
  in this case, 20 minutes. One of it's algorithms generates
  redundant getAllObjectAttributes on each Computer System
  connected to the StorageSubSystem.
  
  The algorithm has been optimized to remove those redundant
  calls.
  
  In the log when this happend you will see the call to this
  method and then a long time later the return(or not return at
  all). For example, note the time difference here;
  
  2014-08-25 15:21:20,208 ViewManager íRMI TCP
  Connection(488)-1.2.3.4ù  DEBUG finder.CustomNodeFinderImpl -
  executeCustomNodeFinder(finderClassName=com.collation.proxy.view
  mgr.finder.FCSwitchStorageSubSystemFinder,
  finderMethodName=findStorageSubSystemsInBusApp,
  view=ViewDescriptor ítype: Graph, view name: Application
  Physical Infrastructure Topology, version: 0, referring
  component id (option
  al):
  
  ..
  
  
  2014-08-25 15:42:10,816 ViewManager íRMI TCP
  Connection(488)-1.2.3.4ù  DEBUG finder.CustomNodeFinderImpl -
  executeCustomNodeFinder() - Custom finder
  com.collation.proxy.viewmgr.finder.FCSwitchStorageSubSystemFinde
  r.findStorageSubSystemsInBusApp returned no results
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  packages:
  | Fix Pack | 7.2.2-TIV-ITADDM-FP0003
  Check the IBM Software Support web site for availability of the
  above maintenance packages.
  

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

  APP DEPENDENCY

• Fixed component ID

  5724N5500

Applicable component levels

• R722 PSY

     UP