IBM Support

PK79133: JCA ADAPTER STOPS POLLING WHEN HIGH AVAILABILITY IS ENABLED BECAUSE MESSAGING ENDPOINT IS NOT ACTIVATED

Fixes are available

7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
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

  • When using a JCA 1.5 adapter, if the High Availability feature
    is activated, the messaging endpoint of the adapter is not
    activated.  This results in the polling feature of the JCA
    adapter to stop, which causes the flow of data to/from the data
    source to stop.
    .
       The message endpoint is an endpoint used to receive a polling
    message from the data source.
    .
       The problem that was reported was using the IBM J2CA Adapter.
    .
       A trace of the Application Server with these events
    Current trace specification =
    *=info:EJBContainer=all:WebContainer=all:WAS.j2c=all:com.ibm.j2c
    a.flatfile.*=all:RRA=finest
    shows the following events.
    .
     [1/20/09 15:29:14:640 EST] 00000029 RAWrapperImpl >
    createAndConfigureRA() Entry
    .
    cells/uumwps01Cell01/applications/MapperModuleApp.ear/deployment
    s/MapperModuleApp/deployment.xml#J2CResourceAdapter_123246416179
    6
    .
    [1/20/09 15:29:14:695 EST] 00000029 RAWrapperImpl 3
    createAndConfigureRA():  setting up for HA, isEnabled=true
    [1/20/09 15:29:14:695 EST] 00000029 RAWrapperImpl >
    setupForHA() Entry
    [1/20/09 15:29:14:695 EST] 00000029 RAWrapperImpl 3
    setupForHA(): returnHACapability returned: 1
    [1/20/09 15:29:14:695 EST] 00000029 RAWrapperImpl 3
    setupForHA(): Setting up for HA: 1 Enabling HA
    [1/20/09 15:29:14:695 EST] 00000029 RAWrapperImpl 3
    setupForHA(): Settings for groupname: raName:
    MapperModuleApp.IBM WebSphere Adapter for Flat Files raKey:
    cells/uumwps01Cell01/applications/MapperModuleApp.ear/deployment
    s/MapperModuleApp/deployment.xml#J2CResourceAdapter_123246416179
    6
    [1/20/09 15:29:14:696 EST] 00000029 RAWrapperImpl <
    setupForHA() Exit
    [1/20/09 15:29:14:696 EST] 00000029 RAWrapperImpl <
    createAndConfigureRA() Exit
    .
       In the RA trace for a working scenario, the following events
    show the polling being enabled with the WBI adapter.
    [5/5/09 15:16:55:650 EDT] 0000003e ResourceAdapt 2
    com.ibm.j2ca.extension.eventmanagement.internal.EventManager
    pollForEvents(int) No events found
    .
    [5/5/09 15:16:55:651 EDT] 0000003e ResourceAdapt <
    com.ibm.j2ca.extension.eventmanagement.internal.EventManager
    pollForEvents(int) Exiting method.
    .
    Also in the WORKING scenario, you will see a J2CA0523I message
    that indicates that the message endpoint is active.
    [5/21/09 14:59:57:337 EDT] 00000028 ActivationSpe I   J2CA0523I:
    The Message Endpoint for ActivationSpec
    IBM/EmailInboundInterface_AS
    (com.ibm.j2ca.email.EmailActivationSpec) and MDB Application
    IBMApp#IBMEJB.jar#export.EmailInboundInterface EIS is activated
    .
    [5/21/09 14:59:57:340 EDT] 00000028 ActivationSpe <
    activateEndpoint,
    current state is: 2 deactivationKey:
    cells/IBM_sy02381Cell01/applications/IBMApp.ear
    /deployments/IBMApp/deployment.xml#J2CResourceAdapter_1
    228846506898:ASTag#4 Exit
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Process Server       *
    *                  with WebSphere Adapters resource            *
    *                  adapters configured for                     *
    *                  inbound High Availability within a          *
    *                  clustered environment.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message endpoints of a resource         *
    *                      adapter configured for inbound High     *
    *                      Availabilty fail to activate.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Message endpoints defined over the ActivationSpecs of a
    resource adapter configured for inbound High
    Availabilty fail to activate when the resource adapter is
    activated within a cluster.  The problem occurs because the
    WebSphere Application Server connection manager fails to
    activate the endpoints when the High Availability manager
    activates the member adapter within the cluster.  The
    problem manifests within WebSphere Adapters as a symptom where
    a adapter stops polling for events -- for example, the
    WebSphere Adapter for flat files stops polling for file
    system events, like the creation of a file.
    

Problem conclusion

  • Apply APAR PK79133 to enable the connection manager to
    activate the message endpoints of a resource adapter,
    configured for high availability within a cluster, when the
    High Availability manager activates the member adapter within
    the High Availability Group.
    
    To enable the fix behavior, define and set the following JVM
    system property within the configuration of each server in the
    cluster:
    
    -Dcom.ibm.ejs.j2c.RAWrapper.changeMemberStateOnActivating=true
    
    The fix for this APAR is currently targeted for inclusion in
    fixpacks 6.0.2.25, 6.1.0.25, and 7.0.0.5.  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

    PK79133

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-01-21

  • Closed date

    2009-03-02

  • Last modified date

    2009-07-31

  • 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

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 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":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021