PM82698: Work profiler fails to start due to exception

APAR status

• Closed as program error.

Error description

• The following error shows up in the logs during startup:
  
  [2/19/13 21:56:09:984 UTC] 00000021 AsyncPmiSubsc E
  ASPC0008E: Exception is: java.lang.NullPointerException
   at
  com.ibm.ws.xd.workprofiler.vm.CPUMonitor$XDNode$Server.notifyLis
  teners(CPUMonitor.java:216)
   at
  com.ibm.ws.xd.workprofiler.vm.CPUMonitor$XDNode$Server.setCPU(CP
  UMonitor.java:174)
   at
  com.ibm.ws.xd.workprofiler.impl.ProcessCPUCollector.updatedStats
  (ProcessCPUCollector.java:87)
   at
  com.ibm.ws.xd.pmi.async.client.AsyncPmiSubscriptionHandler.proce
  ssUpdateQueued(AsyncPmiSubscriptionHandler.java:756)
   at
  com.ibm.ws.xd.pmi.async.client.AsyncPmiSubscriptionHandler.run(A
  syncPmiSubscriptionHandler.java:873)
   at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of WebSphere Virtual Enterprise   *
  ****************************************************************
  * PROBLEM DESCRIPTION: The work profiler component             *
  *                      of WebSphere Virtual Enterprise fails   *
  *                      to initialize correctly.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During startup, under certain timing conditions, the work
  profiler component throws the exception below.  This error
  indicates that the work profiler did not initialize correctly
  and prevents server statistics from being reported accurately.
  [2/19/13 21:56:09:984 UTC] 00000021 AsyncPmiSubsc E
  ASPC0008E: Exception is: java.lang.NullPointerException
  at
  com.ibm.ws.xd.workprofiler.vm.CPUMonitor$XDNode$Server.notifyLis
  teners(CPUMonitor.java:216)
  at
  com.ibm.ws.xd.workprofiler.vm.CPUMonitor$XDNode$Server.setCPU(CP
  UMonitor.java:174)
  at
  com.ibm.ws.xd.workprofiler.impl.ProcessCPUCollector.updatedStats
  (ProcessCPUCollector.java:87)
  at
  com.ibm.ws.xd.pmi.async.client.AsyncPmiSubscriptionHandler.proce
  ssUpdateQueued(AsyncPmiSubscriptionHandler.java:756)
  at
  com.ibm.ws.xd.pmi.async.client.AsyncPmiSubscriptionHandler.run(A
  syncPmiSubscriptionHandler.java:873)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1690)
  

Problem conclusion

• Code changes were made to prevent the initialization error
  from occurring.
  
  This fix will be included in the next fix for WebSphere
  Application Server V.8.5 and for WebSphere Virtual Enterprise
  V.7.0.
  
  Refer to the Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

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

  WAS VIRTUAL ENT

• Fixed component ID

  5725C9203

Applicable component levels

• R700 PSY

     UP