IBM Support

PM64716: BBOO0220E: J2CA0026E: METHOD ADDSYNC CAUGHT ILLEGALSTATEEXCEPTIO

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Problem : Customer notices an illegal State exceptiion after
    installing provided Fix PM39702
    
    
    Message: FFDC1003I: FFDC Incident emitted on
    /PRODAPPS/WebSphere390/V70P80/AppServ80A/profiles/default/logs/f
    fdc/WPP0
    4_N80PA_WPPIS
    1A_AE80_WPPIS1AS_STC30730_0000031800000001_6c826c82_12.02.20_02.
    30.18.0
    41302991385958078271.txt com.ibm.ejs.j2c.RRSGlobalTransaction
    Wrapper.addSync 238
    Trace: 2012/02/20 02:30:18.156 01 t=9B96A8 c=UNK key=P8
    (13007002)
    ThreadId: 0000005f
    FunctionName: com.ibm.ejs.j2c.RRSGlobalTransactionWrapper
    SourceId: com.ibm.ejs.j2c.RRSGlobalTransactionWrapper
    Category: SEVERE
    ExtendedMessage: BBOO0220E: J2CA0026E: Method addSync caught
    java.lang.IllegalStateException: Transaction is inactive or
    prepared
    at
    com.ibm.tx.jta.TransactionImpl.registerSynchronization(Transacti
    onImpl.j
    ava:2638)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Environements with WebSphere Application    *
    *                  Server Adapter fix PM39702 installed.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the server is under load, an       *
    *                      IllegalStateException may be            *
    *                      encountered.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During load when a high volume of transactions are submitted,
    an IllegalStateException may occur.  A race condition may
    happen where multiple transactions compete for the same
    connection and the transaction state becomes invalid.
    

Problem conclusion

  • Code changes have been implemented to enhance the connection
    handling during high volume transaction periods. The fix will
    be available in the next fix pack release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM64716

  • Reported component name

    WEB PROC SRVR F

  • Reported component ID

    5655W0500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-15

  • Closed date

    2012-11-22

  • Last modified date

    2015-04-29

  • APAR is sysrouted FROM one or more of the following:

    JR42618

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEB PROC SRVR F

  • Fixed component ID

    5655W0500

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQH9M","label":"WebSphere Process Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 April 2015