IBM Support

PM74551: CLUSTER STATE SHOWS WEBSPHERE.CLUSTER.STOPPED WHILE IT IS BEING STARTED.

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Using a jython script to start a cluster and track it's status.
    The state of the cluster starts at websphere.cluster.stopped
    then goes to websphere.cluster.partial.start as expected but
    also shows websphere.cluster.stopped even though the cluster
    is really started.  It is not correct for the cluster state to
    go to websphere.cluster.stopped if the cluster is started.
     -
    The command used to get the cluster state is:
     clusterState = AdminControl.getAttribute(clusterObject,
    'state')
                    debug(clusterState)
    

Local fix

  • None
     -
    Keywords: clustemember JMX script jacl
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  versions 7.0, 8.0 and 8.5.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: IPC JMX Connector timeout value is      *
    *                      not being used.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Restarting a server shows the wrong status.
    This FFDC entry was issued:
    FFDC Exception:java.net.SocketTimeoutException
    SourceId:com.ibm.ws.ssl.channel.impl.SSLConnectionLink
    ProbeId:540
    Reporter:com.ibm.ws.ssl.channel.impl.SSLConnectionLink@71f671f6
    java.net.SocketTimeoutException: Async operation timed out
    at
    com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.process
    SyncReadRequest(AioTCPReadRequestContextImpl.java:189)
    at
    com.ibm.ws.tcp.channel.impl.TCPReadRequestContextImpl.read(TCPRe
    adRequestContextImpl.java:111)
    at
    com.ibm.ws.ssl.channel.impl.SSLUtils.handleHandshake(SSLUtils.ja
    va:941)
    at
    com.ibm.ws.ssl.channel.impl.SSLConnectionLink.readyOutbound(SSLC
    onnectionLink.java:776)
    at
    com.ibm.ws.ssl.channel.impl.SSLConnectionLink.connect(SSLConnect
    ionLink.java:994)
    at
    com.ibm.wsspi.channel.base.OutboundProtocolLink.connect(Outbound
    ProtocolLink.java:87)
    at
    com.ibm.ws.management.connector.ipc.IPCCOutboundLink.connect(IPC
    COutboundLink.java:81)
    at
    com.ibm.ws.channel.framework.impl.OutboundVirtualConnectionImpl.
    connect(OutboundVirtualConnectionImpl.java:79)
    at
    com.ibm.ws.management.connector.ipc.ChannelConnectionPool.makeOr
    dinaryTCPConnection(ChannelConnectionPool.java:209)
    at
    com.ibm.ws.management.connector.ipc.ChannelConnectionPool.getCon
    nection(ChannelConnectionPool.java:187)
    at
    com.ibm.ws.management.connector.ipc.IPCConnectorClient.sendRecei
    ve(IPCConnectorClient.java:448)
    at
    com.ibm.ws.management.connector.ipc.IPCConnectorClient.isAlive(I
    PCConnectorClient.java:709)
    at
    com.ibm.ws.management.AdminClientImpl.isAlive(AdminClientImpl.ja
    va:99)
    at
    com.ibm.ws.management.RoutingTable$PingThread.run(RoutingTable.j
    ava:1339)
    Caused by: com.ibm.io.async.AsyncTimeoutException(Async
    operation timed out, Timeout, rc=0)
    at
    com.ibm.io.async.AbstractAsyncFuture.waitForCompletion(AbstractA
    syncFuture.java:359)
    at
    com.ibm.io.async.AsyncFuture.getByteCount(AsyncFuture.java:218)
    at
    com.ibm.ws.tcp.channel.impl.AioSocketIOChannel.readAIOSync(AioSo
    cketIOChannel.java:215)
    at
    com.ibm.ws.tcp.channel.impl.AioTCPReadRequestContextImpl.process
    SyncReadRequest(AioTCPReadRequestContextImpl.java:182)
    ... 13 more
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM74551

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-08

  • Closed date

    2012-12-12

  • Last modified date

    2012-12-12

  • 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

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM74551

Modified date: 12 December 2012