IBM Support

PH39586: ADAPTER CODE REPORTS JAVA.SQL.SQLEXCEPTION: UNSUPPORTED FEATURE FOR THE OPTIONAL METHOD WHEN THE JDBC DRIVER DOESN'T IMPLEMENT T

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

  • We can find adapter code reported:
    [21. 8. 3 9:42:44:110 KST] 000000b1 MCWrapper E J2CA0081E:
    cleanup ???? DS_SELECT ??? ManagedConnection
    WSRdbManagedConnectionImpl@d4d08c0a?? cleanup ???? ????? ???? ??
    ??????. ??? ??: com.ibm.ws.exception.WsException: DSRA0080E: An
    exception was received by the Data Store Adapter. See original
    exception message: Unsupported feature: User defined type. with
    SQL State : 0A000 SQL Code : 334371
    at Altibase7_1.jdbc.driver.ex.Error.throwSQLExceptionInternal(E
    rror.java:188)
    at Altibase7_1.jdbc.driver.ex.Error.throwSQLException(Error.jav
    a:128)
    at Altibase7_1.jdbc.driver.AltibaseConnection.setTypeMap(Altiba
    seConnection.java:1542)
    at Altibase7_1.jdbc.driver.AltibaseLogicalConnection.setTypeMap
    (AltibaseLogicalConnection.java:184)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
    ssorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
    thodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at com.ibm.ws.rsadapter.jdbc.WSJdbcTracer.invoke(WSJdbcTracer.j
    ava:186)
    at com.sun.proxy.$Proxy63.setTypeMap(Unknown Source)
    at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTypeM
    ap(WSRdbManagedConnectionImpl.java:5813)
    at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupS
    tates(WSRdbManagedConnectionImpl.java:4498)
    at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup(
    WSRdbManagedConnectionImpl.java:4191)
    at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1819)
    at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:541)
    at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:2893)
    at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.jav
    a:2608)
    at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion(Loca
    lTransactionWrapper.java:1295)
    at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.driveSynchron
    ization(LocalTranCoordImpl.java:583)
    at com.ibm.tx.ltc.embeddable.impl.EmbeddableLocalTranCoordImpl.
    informSynchronizations(EmbeddableLocalTranCoordImpl.java:220)
    at com.ibm.tx.ltc.impl.LocalTranCoordImpl.cleanup(LocalTranCoor
    dImpl.java:1063)
    at com.ibm.tx.ltc.impl.LocalTranCoordImpl.end(LocalTranCoordImp
    l.java:1195)
    at com.ibm.ws.webcontainer.collaborator.WebAppTransactionCollab
    oratorImpl.postInvoke(WebAppTransactionCollaboratorImpl.java:33
    9)
    at com.ibm.wsspi.webcontainer.collaborator.CollaboratorHelper.p
    ostInvokeCollaborators(CollaboratorHelper.java:574)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFil
    ters(WebAppFilterManager.java:1267)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.j
    ava:4028)
    at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGro
    up.java:304)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContai
    ner.java:1016)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebCo
    ntainer.java:1817)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChanne
    lLink.java:200)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleD
    iscrimination(HttpInboundLink.java:463)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleN
    ewRequest(HttpInboundLink.java:530)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.process
    Request(HttpInboundLink.java:316)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.com
    plete(HttpICLReadCallback.java:88)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.future
    Completed(AioReadCompletionListener.java:175)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(Abstract
    AsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(As
    yncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at
    com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(Result
    Handler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    Caused by: java.sql.SQLException: Unsupported feature: User
    defined type DSRA0010E: SQL ?? = 0A000, ?? ?? = 334,371
    ... 42 more
    
    Need to change adapter code to catch the java.sql.SQLException:
    Unsupported feature when the method is optional and continue
    it's work without report "java.sql.SQLException: Unsupported
    feature"?
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using datasources                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: JDBC providers may not support          *
    *                      setTypeMay and getTypeMap               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    May receive the following error, 000000b1 MCWrapper E
    J2CA0081E:
    cleanup ???? DS_SELECT ??? ManagedConnection
    WSRdbManagedConnectionImpl@d4d08c0a?? cleanup ???? ????? ????
    ??
    ??????. ??? ??: com.ibm.ws.exception.WsException: DSRA0080E: An
    exception was received by the Data Store Adapter. See original
    exception message: Unsupported feature: User defined type. with
    SQL State : 0A000 SQL Code : 334371
    

Problem conclusion

  • Instead of throwing an exception, the code will only log trace
    for the unsupported setTypeMap and getTypeMap, allowing JDBC
    driver providers to not support the methods.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.22 and 9.0.5.13. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH39586

  • 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

    2021-08-04

  • Closed date

    2022-04-25

  • Last modified date

    2022-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

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

Document Information

Modified date:
26 April 2022