IBM IDS ENTRP E / 5724L2304 / B15 - IDS 11.50

With multiple connection managers running in a cluster, if the 
primary node is bounced and failover does not occur, then the 
active failover arbitrator within that connection manager can 
detect when the original primary is active again. However, the 
inactive failover arbitrators running on the remaining 
connection managers are not able to detect when the original 
primary is active. 
. 
The cm log continue to display the following error message: 
Arbitrator = xxx_cm not active, waiting to detect primary 
[cmsm_arb.c:938]

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using the connection manager oncmsm.                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* With multiple connection managers running in a cluster, if   * 
* the primary node is bounced and failover does not occur,     * 
* then the active failover arbitrator within that connection   * 
* manager can detect when the original primary is active       * 
* again. The inactive failover arbitrators running on the      * 
* remaining connection managers are not able to detect when    * 
* the original primary is active.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to ClientSDK 3.50.xC6 and above.              * 
****************************************************************

Bounce the connection manager.

Problem fixed in ClientSDK 3.50xC5.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

26.06.2009
22.01.2010
22.01.2010

3.50.xC5,
3.50.xC6