IBM Support

PK84190: APPLICATION SERVER START WITH -RECOVERY OPTION CAN HANG WHEN USING DERBY DATABASE AND MULTIPLE TRANSACTIONS TO RECOVER

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
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
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
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
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
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
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
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
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
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
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server for z/OS may experience a hang
    situation, if the following conditions are met:
    1) The WebSphere Application Server is started with the
       -recovery option.
    2) The Application Server had previously run application code,
       that used the Derby Database, AND there are transactions
       which need to be reconciled during Server Startup.
    .
      The following error message is seen in the Servant Region
    during the App Server startup:
    .
    
    
    
    BossLog: { 0026} 2009/01/20 15:32:16.610 01 SYSTEM=MVS129
     CELL=AZBASEA NODE=AZNODEA CLUSTER=AZSR01 SERVER=AZSR00B
     PID=0X000004FD TID=0X00000022 0XB1EFC24C
     c=./bbgrjtr.cpp  at line:+886 ... BBOO0221W: J2CA0061W: Error
     creating XA Connection and Resource
     com.ibm.ws.exception.WsException:
     DSRA8100E: Unable to get a XAConnection from the DataSource.
     with SQL State : XJ040 SQL Code : 40000
     at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.
         setLinkedException(DataStoreAdapterException.java:530)
     at com.ibm.ws.rsadapter.AdapterUtil.mapException
       (AdapterUtil.java:2151)
     at com.ibm.ws.rsadapter.spi.WSRdbDataSource.
       getPooledConnection(WSRdbDataSource.java:2168)
    ..
    ..
    Caused by: com.ibm.websphere.ce.cm.StaleConnectionException:
     Failed to start database '/WebSphere/V7R0M0/AppServer/
     profiles/default/PortalServer/derby/wpsdb', see the next
     exception for details.
     DSRA0010E: SQL State = XJ040, Error Code = 40,000
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0
         (Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance
         (NativeConstructorAccessorImpl.java:45)
    ..
    ..
    ---- Begin backtrace for Nested Throwables
     java.sql.SQLException: Failed to start database
       '/WebSphere/V7R0M0/
     AppServer/profiles/default/PortalServer/derby/wpsdb',
       see the next exception for details.
     DSRA0010E: SQL State = XJ040, Error Code = 40,000
     at org.apache.derby.impl.jdbc.SQLExceptionFactory40.
        getSQLException(Unk
     at org.apache.derby.impl.jdbc.Util.
        newEmbedSQLException(Unknown Source)
     at org.apache.derby.impl.jdbc.Util.
        seeNextException(Unknown Source)
     at org.apache.derby.impl.jdbc.EmbedConnection.
        bootDatabase(Unknown Sour
    .
    BossLog: { 0027} 2009/01/20 15:32:16.683 01 SYSTEM=MVS129
     CELL=AZBASEA NODE=AZNODEA CLUSTER=AZSR01 SERVER=AZSR00B
     PID=0X000004FD TID=0X00000022 0XB1EFC24C
     c=./bbgrjtr.cpp  at line:+886 ... BBOO0221W: WTRN0005W:
     The XAResource  for a transaction participant could not
     be recreated and transaction recovery may not be able
     to complete properly. The resource was J2CXAResourceInfo :
     cfName = wpdbDS
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0 for z/OS using Apache Derby     *
    *                  database.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Recovery of transactional Apache        *
    *                      Derby XA resources may not complete     *
    *                      properly.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When Websphere Application Server is started with -recovery
    option and the transaction partner logs indicate prior XA
    connections to Apache Derby databases, the following warning
    may be received:
    
    BBOO0221W: WTRN0005W: The XAResource  for a transaction
    participant could not be recreated and transaction recovery may
    not be able to complete properly. The resource was
    J2CXAResourceInfo : cfName = wpdbDS
    
    and the following exceptions may be logged:
    
    J2CA0061W: Error creating XA Connection and Resource
    com.ibm.ws.exception.WsException:
    DSRA8100E: Unable to get a XAConnection from the DataSource.
    with SQL State : XJ040 SQL Code : 40000
    at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.
    setLinkedException(DataStoreAdapterException.java:530)
    at com.ibm.ws.rsadapter.AdapterUtil.mapException
    (AdapterUtil.java:2151)
    at com.ibm.ws.rsadapter.spi.WSRdbDataSource.
    getPooledConnection(WSRdbDataSource.java:2168)
    ...
    Caused by: com.ibm.websphere.ce.cm.StaleConnectionException:
    Failed to start database '/WebSphere/V7R0M0/AppServer/
    profiles/default/PortalServer/derby/wpsdb', see the next
    exception for details.
    DSRA0010E: SQL State = XJ040, Error Code = 40,000
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0
    (Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance
    (NativeConstructorAccessorImpl.java:45)
    
    This behavior is caused by the recovery process attempting
    to start a new Derby engine for each resource, which may
    require a transaction recovery even though the engine has
    already been started for the previously processed Derby
    resource.
    

Problem conclusion

  • Recovery process will stop the Derby engine after each Derby
    resource processed for transaction recovery. If needed, the
    engine will be re-started for the next Derby resource that
    require a transaction recovery.
    
    APAR PK84190 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.5 of WebSphere Application Server for
    z/OS.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK84190

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-06

  • Closed date

    2009-05-05

  • Last modified date

    2009-08-03

  • 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

  • R700 PSY UK48200

       UP09/07/27 P F907

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

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

Document Information

Modified date:
24 October 2021