IBM Support

PI89405: APP SERVER CONTROLLER TERMINATES WITH C9C21A44 FOLLOWED BY C9C21A30.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • App server controller terminates unexpectedly with these
    errors
    
    C9C21A44
    org.omg.CORBA.INTERNAL: Invalid state (3) on 2PC  vmcid:
    0xc9c21000  minor code: A44  completed: No
    .at com.ibm.ws390.tx.ControllerTransactionManagerImpl.commit(Con
    trollerTransactionManagerImpl.java:2776)
    .at com.ibm.ws390.tx.WorkRequestDispatcher.dispatchTMPC(WorkRequ
    estDispatcher.java:204)
    .at com.ibm.ws390.tx.WorkRequestDispatcher.dispatch(WorkRequestD
    ispatcher.java:144)
    
    BBOO0222I: WTRN0108I: contextDisassociation. Unexpected state: 3
    TransactionControlRep: Xid = {XidImpl: formatId(c3c20186),
    gtrid_length(36), bqual_length(40),
    data(xxxxxxxxxxxx)}, TxState = 3, Cascaded = false,
    Root = true, Normal = true, isTransactionTimedout = false,
    TransactionType = 2, TransactionExecutionType = 5,
    IsContextPinned = false,
    isNativeContextAssociationFailed = false,
    IsContextDisassociated = true, NeedsManualOutcome = false,
    IsJCA = false, InJcaFormatId = 0, InJcaBqual = ,
    IsWsat = false, ServantToken = 00000ebc00000001,
    parentURToken = null.
    TransactionalUnitOfWork: URId = xyz, ContextToken = abc,
    parentURToken = 24dc, IsHeuristic = true,
    IsURForgotten = false, IsXAEnlisted = true,
    FailedXAResources = true, RetryCommitOnFailedXA = false,
    IsForgetPending = false, RestartTxState = 0, RestartLocalId =
    0, resourceInterestCount = 0, PendingRollbackOnly = false,
    IsRRSLastAgentOnCommit = false.
    
    BBOO0035W TERMINATING THE CURRENT PROCESS, REASON=C9C21A30.
    
    After server started terminating due to C9C21A30, these errors
    were issued as well:
    
    BBOO0056E CONTEXT SERVICE 'CTXBEGC' FAILED WITH RETURN CODE=301.
    BBOT0004E: RRS SERVICE ATRAFGT FAILED WITH RETURN CODE=370.
    BBOO0222I: WTRN0108I: ATRAFGT. Invalid RRS return code: 370
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of JTA   *
    *                  transactions                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: WTRN0108I: ATRAFGT. Invalid RRS         *
    *                      return code: 370 after control region   *
    *                      starts to terminate with reason         *
    *                      C9C21A30                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The transaction service issued an ATRAFGT which failed with
    return code 370 while the control region was already
    terminating due to an earlier error condition.  The fix for
    the initial error is provided under APAR PI93971.  The
    existing processing of the 370 return code would also request
    termination of the control region and obfuscate diagnostic
    information required to resolve the initial issue.
    

Problem conclusion

  • The transaction service was modified so that in this
    particular case the error handling for the 370 return code
    from ATRAFGT provided existing diagnostic information and did
    not re-initiate control region termination.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.15, 8.5.5.14 and 9.0.0.8.  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

    PI89405

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-27

  • Closed date

    2018-04-25

  • Last modified date

    2018-04-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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"800","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 October 2021