PM60978: DYNAMIC CLUSTERS IN AUTOMATIC MODE FAIL TO START WHEN APC CONTROLLER RUNS ON A DMGR.

Download WebSphere Virtual Enterprise Version 7.0 Fix Pack 3
IBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 4, also known as Version 7.0.0.4 is available for download.
IBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 5, also known as Version 7.0.0.5 is available for download.
IBM WebSphere Virtual Enterprise Version 7.0 Fix Pack 6, also known as Version 7.0.0.6 is available for download.

APAR status

• Closed as program error.

Error description

• Customer mentioned that when a health policy is reached , the
  restart server in dynamic cluster in automatic mode restart the
  sick server instead of the other member of the DC. This was
  working in the previous version 6.1 of WVE.
  
  Customer see the following exception in the ffdc:
  
  [3/12/12 14:16:14:252 EDT]     FFDC
  Exception:javax.management.JMRuntimeException
  SourceId:com.ibm.ws.management.AdminServiceImpl.invoke
  ProbeId:693
  Reporter:com.ibm.ws.management.AdminServiceImpl$1@9c322d7f
  javax.management.JMRuntimeException: ADMN0022E: Access is denied
  for the launchProcess operation on NodeAgent MBean because of
  insufficient or empty credentials.
   at
  com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImp
  l.java:2382)
   at
  com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
  va:1312)
   at
  com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
  troller.java:118)
  
  [3/12/12 14:16:14:353 EDT]     FFDC
  Exception:javax.management.MBeanException
  SourceId:com.ibm.ws.xd.middlewareserver.commands.MiddlewareServe
  rAdminUtil.getProcessStatus ProbeId:MyWorker
  javax.management.MBeanException
   at
  com.ibm.ws.xd.middlewareserver.commands.MiddlewareServerAdminUti
  ls.invoke(MiddlewareServerAdminUtils.java:1170)
   at
  com.ibm.ws.xd.middlewareserver.commands.MiddlewareServerAdminUti
  ls.startMiddlewareServer(MiddlewareServerAdminUtils.java:1281)
   at
  com.ibm.ws.xd.middlewareserver.commands.MiddlewareServerAdminUti
  ls$1.doWork(MiddlewareServerAdminUtils.java:1185)
   at
  com.ibm.ws.xd.middlewareserver.commands.MiddlewareServerAdminUti
  ls$MyWorker.run(MiddlewareServerAdminUtils.java:1934)
  Caused by: javax.management.JMRuntimeException: ADMN0022E:
  Access is denied for the launchProcess operation on NodeAgent
  MBean because of insufficient or empty credentials.
   at
  com.ibm.ws.management.AdminServiceImpl.preInvoke(AdminServiceImp
  l.java:2382)
   at
  com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
  va:1312)
   at
  com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
  troller.java:118
  
  [3/12/12 14:16:14:364 EDT]     FFDC
  Exception:java.lang.Exception
  SourceId:com.ibm.apc.xd.execer.sequencer.exec.APCXDExecDC.run
  ProbeId:272
  java.lang.Exception: Error with launchProcess for
  edgeaphid10Cell06/edgeaphid10Node09/dyndc1_edgeaphid10Node09
   at
  com.ibm.apc.xd.execer.sequencer.exec.APCXDExecDC.performAction(A
  PCXDExecDC.java:410)
   at
  com.ibm.apc.xd.execer.sequencer.exec.APCXDExecDC.performAction(A
  PCXDExecDC.java:298)
   at
  com.ibm.apc.xd.execer.sequencer.exec.APCXDExecDC.access$300(APCX
  DExecDC.java:51)
   at
  com.ibm.apc.xd.execer.sequencer.exec.APCXDExecDC$APCXDExecDCHelp
  .run(APCXDExecDC.java:263)
   at java.lang.Thread.run(Thread.java:770)
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All WebSphere Virtual Enterprise users of   *
  *                  7.0.0.2                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Application placement controller is     *
  *                      unable to start or stop servers.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Application placement controller is
  unable to start or stop servers when
  controller runs on deployment manager.
  

Problem conclusion

• The application placement controller was fixed so that a
  deployment manager can start or stop servers.
  
  This fix will be included in the next available fix pack for
  WebSphere Virtual Enterprise.
  

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