IBM Support

PI16455: The WebSphere J2C resource workload routing mbean operation failOverToAlternateResource fails with IllegalStateException

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The default value for InactiveConnectionSupport has been set to
    true for WebSphere built-in Relational resource adapter causing
    the following exception on failOverToAlternateResource
    operation.
    
    [3/17/14 20:38:29:914 EDT] 000000b1 ConnectionFac W   J2CA0688W:
    The FailOverToAlternateResource operation issued for the
    resource with a JNDI name of ..... failed. Cause:
    java.lang.IllegalStateException: Request to failover to
    alternate cannot be executed on a resource that is not failover
    support configured.
    No-op.
    at
    com.ibm.ejs.j2c.PoolManager.failOverToAlternateResource(PoolMana
    ger.java
    :10189)
    at
    com.ibm.ejs.j2c.mbeans.ConnectionFactoryMbeanImpl.failOverToAlte
    rnateResource(ConnectionFactoryMbeanImpl.java:1640)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: The WebSphere J2C resource workload     *
    *                      routing mbean operation                 *
    *                      failOverToAlternateResource fails       *
    *                      with IllegalStateException              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the ConnectionFactory Mbean operation
    failOverToAlternateResource to manually failover to an
    alternate server, the following exception might occur for a
    cell scoped datasource even if the alternate resource has been
    configured using the custom property alternateResourceJNDIName.
    java.lang.IllegalStateException: Request to failover to
    alternate cannot be executed on a resource that is not
    failover support configured.No-op.
    Another symptom is that when a cell scoped datasource is
    configured for automatic failover using the properties
    alternateResourceJNDIName and failureThreshold, the failover
    does not happen.
    This issue happens because during the PoolManager
    initialization the  failover support(ie resource workload
    routing) is not being enabled because the property
    InactiveConnectionSupport is incorrectly read and used for the
    cell scoped WebSphere built-in relational resource adapter.
    

Problem conclusion

  • The WebSphere J2C component has been corrected to properly
    initialize the resource workload routing capability.
    
    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

    PI16455

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-04-21

  • Closed date

    2014-07-30

  • Last modified date

    2014-10-15

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

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