IZ78373: VIEWMANAGER OUTOFMEMORY BUILDING VIEWS

APAR status

• Closed as program error.

Error description

• When building views too much data is pulled into memory which
  both takes a long time and can cause OutOfMemory conditions.
  
  The following error will be present in the ViewManager.log (the
  key string to seach for is getNextWithCursor):
  
  
  
  
  
  2010-06-25 05:57:11,288 ViewManager [ViewBuilderThread for view
  View:
  [name: DefnTreeApplications]]  DEBUG
  topomgr.TopologyManagerFactory -
  Reconnecting to TopologyManager -
  Proxy[TopologyManagerServiceInterface,RemoteObjectInvocationHand
  ler[Unic
  astRef2 [liveRef:
  [endpoint:[10.208.253.72:9550,com.collation.platform.jini.Custom
  SocketFa
  ctory@2a](remote),objID:[-50e03588:1296cb0e21b:-8000, 0]]]]]
  java.rmi.ServerError: Error occurred in server thread; nested
  exception
  is:
          java.lang.OutOfMemoryError
          at
  sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:3
  37)
          at sun.rmi.transport.Transport$1.run(Transport.java:168)
          at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:279)
          at
  sun.rmi.transport.Transport.serviceCall(Transport.java:164)
          at
  sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.j
  ava:506)
          at
  sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleReque
  st(TCPTr
  ansport.java:838)
          at
  sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTran
  sport.ja
  va:912)
          at java.lang.Thread.run(Thread.java:810)
          at
  sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(S
  treamRem
  oteCall.java:263)
          at
  sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.
  java:239
  )
          at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
          at
  java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod
  (RemoteO
  bjectInvocationHandler.java:194)
          at
  java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjec
  tInvocat
  ionHandler.java:147)
          at $Proxy14.getNextWithCursor(Unknown Source)
          at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown
  Source)
          at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  Accessor
  Impl.java:43)
          at java.lang.reflect.Method.invoke(Method.java:618)
          at
  com.collation.topomgr.TopologyManagerFactory.invoke(TopologyMana
  gerFacto
  ry.java:313)
          at $Proxy22.getNextWithCursor(Unknown Source)
          at
  

Local fix

Problem summary

• When building views too much data is pulled into memory which
  takes a long time and can cause OutOfMemory to occur. The
  following error will be present in the ViewManager.log (the key
  string to seach for is getNextWithCursor):
  ViewManager [ViewBuilderThread for view View:
  [name:DefnTreeApplications]]
  DEBUG topomgr.TopologyManagerFactory - Reconnecting
  toTopologyManager -Proxy[TopologyManagerServiceInterface,
  RemoteObjectInvocationHandler[UnicstRef2[liveRef:[endpoint:[10.2
  08.253.72:9550,com.collation.platform.jini.CustomSocketFactory@2
  a](remote),objID:[-50e03588:1296cb0e21b:-8000,
  0]]]]]java.rmi.ServerError: Error occurred in server thread;
  nested exception is:java.lang.OutOfMemoryError
  at
  sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:3
  37)
  at sun.rmi.transport.Transport$1.run(Transport.java:168)
  at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:279)
  at sun.rmi.transport.Transport.serviceCall(Transport.java:164)
  at
  sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.j
  ava:506)
  at
  sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.handleReque
  st(TCPTransport.java:838)
  at
  sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTran
  sport.ja va:912)
  at java.lang.Thread.run(Thread.java:810)
  at
  sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(S
  treamRemoteCall.java:263)
  at
  sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.
  java:239 )
  at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:141)
  at
  java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod
  (RemoteObjectInvocationHandler.java:194)
  at
  java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjec
  tInvocationHandler.java:147)
  at $Proxy14.getNextWithCursor(Unknown Source)
  at sun.reflect.GeneratedMethodAccessor224.invoke(UnknownSource)
  at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:618)
  atcom.collation.topomgr.TopologyManagerFactory.invoke(TopologyMa
  nagerFactory.java:313)
  at $Proxy22.getNextWithCursor(Unknown Source)
  

Problem conclusion

• The fix for this APAR is contained in the following
  maintenance packages:
  | Fix Pack | 7.2.0.0-TIV-ITADDM-FP0002
  

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

• R720 PSY

     UP