IBM Support

PI17578: CLUSTER STATUS IS PARTIAL IN THE CONSOLE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When creating a cluster with server member using log location
    with its own filesystem. if you accidently forget to define
    the filesystem, when you try to start the cluster, you see
    the following error in the deployment manager log.
    The status icon at the console is always in the partial
    start state.  If they try to remove the cluster, it won't let
    it be removed.
    Deployment manager requires re-start in order to remove the
    cluster.
    
    000010aa Cluster       E   WWLM0058E:
    Cluster
    member test_server did not start properly.  javax.management.
    MBeanException: Exception thrown in RequiredModelMBean while
    trying to invoke operation launchProcess
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    handleAdminFault(SOAPConnectorClient.java:951)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    invokeTemplateOnce(SOAPConnectorClient.java:919)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    invokeTemplate(SOAPConnectorClient.java:685)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    invokeTemplate(SOAPConnectorClient.java:675)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    invoke(SOAPConnectorClient.java:661)
    at
    com.ibm.ws.management.connector.soap.SOAPConnectorClient.
    invoke(SOAPConnectorClient.java:483)
    at com.sun.proxy.$Proxy41.invoke(Unknown Source)
    at
    com.ibm.ws.management.AdminClientImpl.invoke(AdminClientImpl.
    java:224)
    at com.ibm.ws.management.AdminServiceImpl$1.run
    (AdminServiceImpl.java:1365)
    at
    com.ibm.ws.security.util.AccessController.doPrivileged
    (AccessController.java:118)
    at com.ibm.ws.management.AdminServiceImpl.invoke
    (AdminServiceImpl.java:1228)
    at
    com.ibm.ws.management.wlm.Cluster.launchMember(Cluster.java:
    2168)
    at
    com.ibm.ws.management.wlm.Cluster$MemberStateChange.run
    (Cluster.java:2974)
    at java.lang.Thread.run(Thread.java:804)
    Caused by:
    com.ibm.websphere.management.exception.AdminException:
    Process server failed to launch:
    com.ibm.ws.process.exception.
    InvalidDirectoryException: PROC0003E: Working Directory:
    [] does not appear to be valid, or
    accessible by the process.  Process could not be created.
    

Local fix

  • Re-start dmgr to delete the cluster.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Console cluster status hangs in         *
    *                      partially started state when            *
    *                      attempting to start a single member     *
    *                      cluster.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After a synchronous cluster startup failure, the cluster
    status is not updated. The cluster status will show as
    partially started and member status will be stopped. The
    cluster status will hang on partially started state
    indefinitely. The following startup ffdc can be observed in
    Dmgr SystemOut.
    Cluster       E   WWLM0058E: Cluster member me1 did not start
    properly.  javax.management.MBeanException: Exception thrown
    in RequiredModelMBean while trying to invoke operation
    launchProcess
    at
    javax.management.modelmbean.RequiredModelMBean.invokeMethod(Requ
    iredModelMBean.java:1191)
    at
    javax.management.modelmbean.RequiredModelMBean.invoke(RequiredMo
    delMBean.java:995)
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Def
    aultMBeanServerInterceptor.java:848)
    at
    com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.jav
    a:774)
    at
    com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.ja
    va:1335)
    at
    com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon
    troller.java:118)
    at
    com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.j
    ava:1228)
    at
    com.ibm.ws.management.connector.AdminServiceDelegator.invoke(Adm
    inServiceDelegator.java:181)
    at
    com.ibm.ws.management.connector.ipc.CallRouter.route(CallRouter.
    java:247)
    at
    com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink.doWo
    rk(IPCConnectorInboundLink.java:360)
    at
    com.ibm.ws.management.connector.ipc.IPCConnectorInboundLink$IPCC
    onnectorReadCallback.complete(IPCConnectorInboundLink.java:602)
    at
    com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadComplet
    edCallback.complete(SSLReadServiceContext.java:1784)
    at
    com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureComp
    leted(AioReadCompletionListener.java:165)
    at
    com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyn
    cFuture.java:217)
    at
    com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncC
    hannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at
    com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at
    com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHand
    ler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1815)
    

Problem conclusion

  • A check was added to catch and notify of a cluster startup
    failure. If a synchronous failure is detected, the status of
    all cluster members is checked and a cluster status update is
    set accordingly.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.4.  Please 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 number

    PI17578

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-08

  • Closed date

    2014-08-25

  • Last modified date

    2014-08-25

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022