IBM Support

PI94171: ILLEGALSTATEEXCEPTION: THE JTA TRANSACTION IS NOT STARTED OR INVALID

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • The failing application is hitting the problems with
    both the v6.1 and v8.5.5 EJB container behaviors, so nether
    behavior is adequate to allow the application to work properly.
    
    In order to allow this application to start, the complete
    solution
    provided in v9.0 and Liberty is required. The odd state of
    2 UOWs active on the thread will not interfere with called
    EJB methods, and calling EJB methods will leave the 2 UOWs
    active without interference.
    
    First
    time it failed to start @ 11/29/17 2:22:43:097 EST, same
    application
    started second attempt @ 11/29/17 2:24:56:246 EST
    
    
    [11/29/17 2:22:42:278 EST] 0000009a ApplicationMg W
    WSVR0101W: An
    error occurred starting, AppEAR
    [11/29/17 2:22:42:281 EST] 0000009a ApplicationMg A   WSVR0217I:
    Stopping application: AppEAR
    
    
    [11/29/17 2:22:43:097 EST] 0000009a CompositionUn E   WSVR0194E:
    Composition unit WebSphere:cuname=AppEAR in BLA
    WebSphere:blaname=AppEAR failed to start.
    
    [11/29/17 2:23:53:575 EST] 0000012e CompositionUn A   WSVR0190I:
    Starting composition unit WebSphere:cuname=AppEAR in BLA
    WebSphere:blaname=AppEAR.
    
    [11/29/17 2:24:56:246 EST] 0000012e CompositionUn A   WSVR0191I:
    Composition unit WebSphere:cuname=AppEAR in BLA
    WebSphere:blaname=AppEAR started.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server with EJB applications using the      *
    *                  javax.transaction.TransactionManager        *
    *                  interface.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: EJB applications using the              *
    *                      javax.transaction.TransactionManager    *
    *                      interface may experience rollbacks or   *
    *                      IllegalStateExceptions.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    EJB applications using the javax.transaction.TransactionManager
    interface to begin, suspend, and resume transactions may
    experience unexpected transaction rollbacks or the following
    exception when calling an EJB method:
    java.lang.IllegalStateException: Cannot begin a
    LocalTransactionContainment. A LocalTransactionContainment
    is already active.
    

Problem conclusion

  • Use of the javax.transaction.TransactionManager API by an
    application may interfere with transaction management
    performed by the application server containers (EJB and/or Web),
    resulting in various failures, such as transactions being
    rolled back or an IllegalStateException when calling an EJB
    method.
    
    A change will be provided with this APAR, which may be
    enabled with the JVM custom property setting:
    com.ibm.websphere.ejbcontainer.PI94171=true.
    
    When enabled, the transaction management behavior of the EJB
    container will be upgraded to v9.0 behavior, which provides
    better toleration of an application using the
    javax.transaction.TransactionManager API. If use of the
    TransactionManager API results in multiple units of work
    concurrently active on a thread, the new EJB container
    behavior will ensure all units of work will be suspended
    prior to an EJB method call, and then all suspended
    units of work resumed after the EJB method call.
    
    This new behavior is an improvement over the default
    v8.5 behavior, which does not suspend all units of
    work. Also, use of the com.ibm.websphere.ejbcontainer.PI94171
    property is preferred over the
    com.ibm.websphere.ejbcontainer.PI10351=true
    property since the earlier PI10351 change does not ensure all
    suspended units of work are resumed after an EJB method
    completes.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.14.  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

    PI94171

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-22

  • Closed date

    2018-03-12

  • Last modified date

    2018-03-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI94171

Modified date: 12 March 2018


Translate this page: