IBM Support

PM34365: JAVA.LANG.ABSTRACTMETHODERROR: JAVA/SQL/WRAPPER.ISWRAPPERFOR ON ORACLE DATA SOURCE AFTER UPGRADE TO FIX PACK V7.0.0.15/PM20797

Fixes are available

PM34365; 7.0.0.15: java.lang.abstractmethoderror: java/sql/wrapper.iswrapperfor
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

  • After upgrading WebSphere Application Server V7.0 to Fix Pack
    V7.0.0.15, the following errors may be generated in the
    SystemOut.log if an Oracle JDBC driver that is not meant for
    Java 1.6 is used.  This includes the Oracle 11g ojdbc5.jar
    (meant for Java 1.5) or the Oracle 10g ojdbc14.jar (meant for
    Java 1.4 or 1.5).  If the Oracle 11g ojdbc6.jar is used, the
    problem that is addressed by this APAR will not occur.
    
    
    [3/9/11 11:29:30:054 CET] 00000011 RemoteExcepti E   CNTR0020E:
    EJB threw an unexpected (non-declared) exception during
    invocation of method "start" on bean
    "BeanId(TestBeanmethod#TestBean.jar#TestBean, null)". Exception
    data: java.lang.AbstractMethodError:
    java/sql/Wrapper.isWrapperFor(Ljava/lang/Class;)Z
    at
    com.ibm.websphere.rsadapter.OracleDataStoreHelper.doConnectionCl
    eanup(OracleDataStoreHelper.java:358)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.preTestConne
    ction(WSRdbManagedConnectionImpl.java:5825)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.preTestConne
    ction(WSRdbManagedConnectionImpl.java:5719)
    at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2593)
    at
    com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionMa
    nager.java:1059)
    at
    com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionM
    anager.java:696)
    at
    com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
    ataSource.java:668)
    at
    com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcD
    ataSource.java:635)
    
    Or:
    
    [3/24/11 15:53:02:269 GST] 00000026 RegisteredSyn E   WTRN0074E:
    Exception caught from after_completion synchronization
    operation:
    java.lang.AbstractMethodError:
    java/sql/Wrapper.isWrapperFor(Ljava/lang/Class;)Z
    at
    com.ibm.websphere.rsadapter.OracleDataStoreHelper.doConnectionCl
    eanup(OracleDataStoreHelper.java:358)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupState
    s(WSRdbManagedConnectionImpl.java:4218)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRd
    bManagedConnectionImpl.java:4038)
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1531)
    
    Or:
    
    [3/24/11 21:18:52:218 EDT] 0000001a LocalTranCoor 3   An Error
    occurred in afterCompletion.
    java.lang.AbstractMethodError:
    java/sql/Wrapper.isWrapperFor(Ljava/lang/Class;)Z
    at
    com.ibm.websphere.rsadapter.OracleDataStoreHelper.doConnectionCl
    eanup(OracleDataStoreHelper.java:358)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupState
    s(WSRdbManagedConnectionImpl.java:4218)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRd
    bManagedConnectionImpl.java:4038)
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1531)
    
    Since the error is happening in the connection cleanup, the
    cleanup of connections may not complete, resulting in J2CA0045E
    errors and ConnectionWaitTimeoutExceptions:
    
    J2CA0045E: Connection not available while invoking method
    createOrWaitForConnection for resource jdbc/testds
    
    com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException:
    Connection not available, Timed out waiting for 180033
     at
    com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java
    :1664)
     at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2471)
    ...
    
    
    In addition, if connection pool tracing is enabled
    (WAS.j2c=all:RRA=all), the trace will show incorrect
    connection pool statistics.  That is, the connection pool is
    shown to have no shared, unshared, or free connections, while
    the total number of connections indicates that there are
    connections in the pool.  This makes it very difficult to
    determine the cause of the J2CA0045E error and
    ConnectionWaitTimeoutException.
    

Local fix

  • Use the Oracle 11g ojdbc6.jar, which is supported for use with
    Java 1.6.  This driver can be used to connect to Oracle 11g or
    Oracle 10g databases.  Reverting back to WebSphere Application
    Server V7.0 Fix Pack V7.0.0.13 or earlier will also prevent the
    problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application Server
    ****************************************************************
    * PROBLEM DESCRIPTION: java.lang.AbstractMethodError:          *
    *                      java/sql/Wrapper.isWrapperFor on        *
    *                      Oracle data source                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1) The method java.sql.Wrapper.isWrapper() was added in java
    SDK 6 and when passing an argument, that is a class compiled
    using older java versions to this method causes the
    AbstractMethodError. WebSphere RRA code internally used this
    method and with the JDBC Provider classpath configured with
    the Oracle JDBC Driver ojdbc15.jar or ojdbc14.jar(compiled
    using SDK 5 and SDK 1.4.2 respectively) can result in
    AbstractMethodError.
    
    java.lang.AbstractMethodError:
    java/sql/Wrapper.isWrapperFor(Ljava/lang/Class;)Z
    at
    com.ibm.websphere.rsadapter.OracleDataStoreHelper.doConnectionCl
    eanup(OracleDataStoreHelper.java:358)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupState
    s(WSRdbManagedConnectionImpl.java:4218)
    at
    com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(WSRd
    bManagedConnectionImpl.java:4038)
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1531)
    at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:508)
    at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1846)
    at
    com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java:23
    78)
    
    2)When the AbstractMethodError is encountered in
    the connection cleanup path, connection cleanup may not
    be complete and can lead to J2CA0045E and
    ConnectionWaitTimeoutException
    
    FreePool      E   J2CA0045E: Connection not available while
    invoking method createOrWaitForConnection for resource
    jdbc/testds
    
    com.ibm.websphere.ce.j2c.ConnectionWaitTimeoutException:
    Connection not available, Timed out waiting for 180033
     at
    com.ibm.ejs.j2c.FreePool.createOrWaitForConnection(FreePool.java
    :1664)
     at com.ibm.ejs.j2c.PoolManager.reserve(PoolManager.java:2471)
    
    
    3) Also there may be traces showing incorrect pool statistics.
    The connection pool is shown to have no shared, unshared,
    or free connections, but the total number of connections
    indicates that there are connections in the pool.
    
    For example:
    
    Total number of connections: 26 (max/min 50/1,
    reap/unused/aged 180/1800/0, connectiontimeout/purge
    180/EntirePool)
    
    (testConnection/inteval
    false/0, stuck timer/time/threshold 0/0/0, surge
    time/connections 0/-1)
    Shared Connection information (shared partitions 200)
      No shared connections
    
    Free Connection information (free distribution
    table/partitions 25/1)
    
      No free connections
    
    UnShared Connection information
      No unshared connections
    

Problem conclusion

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM34365

  • Reported component name

    WAS EXPRESS

  • Reported component ID

    5724I6300

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-09

  • Closed date

    2011-03-29

  • Last modified date

    2011-04-22

  • 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

    WAS EXPRESS

  • Fixed component ID

    5724I6300

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7JFU","label":"WebSphere Application Server - Express"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 October 2021