IBM Support

PK90747: SQLSERVERDICTIONARY EXCEPTION IS THROWN WHEN USING MICROSOFT SQL SERVER JDBC DRIVER V1.2 OR 2.0.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the Microsoft SQL Server JDBC Driver v1.2 or 2.0 is used
    instead of the jTDS driver, then the SQLServerDictionary will
    throw an exception while trying to parse the driverName
    "Microsoft SQL Server JDBC Driver" to determine the server
    version.
    
    Example stack :
    java.lang.NumberFormatException: For input string: "JDBC"
    at
    java.lang.NumberFormatException.forInputString(NumberFormatExcep
    tion.java:48)
    at java.lang.Integer.parseInt(Integer.java:447)
    at java.lang.Integer.parseInt(Integer.java:497)
    at
    org.apache.openjpa.jdbc.sql.SQLServerDictionary.connectedConfigu
    ration(SQLServerDictionary.java:92)
    

Local fix

  • candidate to be fixed in next release
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Feature Pack for EJB 3.0             *
    ****************************************************************
    * PROBLEM DESCRIPTION: NumberFormatException: For input        *
    *                      string: "JDBC" is encountered when      *
    *                      using Microsoft JDBC Driver v1.2 or     *
    *                      2.0 with JPA.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the Microsoft SQL Server JDBC Driver v1.2 or 2.0
    with JPA, the following Exception can occur:
    
    ava.lang.NumberFormatException: For input string: "JDBC"
    at
    java.lang.NumberFormatException.forInputString(NumberFormatExcep
    tion.java:48)
    at java.lang.Integer.parseInt(Integer.java:447)
    at java.lang.Integer.parseInt(Integer.java:497)
    at
    org.apache.openjpa.jdbc.sql.SQLServerDictionary.connectedConfigu
    ration(SQLServerDictionary.java:92)
    at
    org.apache.openjpa.jdbc.sql.DBDictionaryFactory.newDBDictionary(
    DBDictionaryFactory.java:190)
    at
    org.apache.openjpa.jdbc.sql.DBDictionaryFactory.newDBDictionary(
    DBDictionaryFactory.java:100)
    at
    org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDBDictiona
    ryInstance(JDBCConfigurationImpl.java:584)
    

Problem conclusion

  • The SQLServerDictionary was updated to properly handle the
    driverName that the Microsoft SQL Server JDBC Driver v1.2 and
    v2.0 reports when queried.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.29.  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

    PK90747

  • Reported component name

    WAS EJB3 FEATUR

  • Reported component ID

    5724J0851

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-07

  • Closed date

    2009-08-04

  • Last modified date

    2009-08-04

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

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

    PK92906

Fix information

  • Fixed component name

    WAS EJB3 FEATUR

  • Fixed component ID

    5724J0851

Applicable component levels

  • R610 PSY

       UP

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

Document Information

Modified date:
10 February 2022