IBM Support

PM13911: ILLEGALSTATEEXCEPTION ATTEMPTING TO START A MESSAGING ENGINE AGAINST AN SQL SERVER 2008 DATABASE WITH A JDBC 2.0 DRIVER

Fixes are available

PM13911; 7.0.0.7: Problems using SQL Server as a data store
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.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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

  • One of the following problems are seen using
    Microsoft SQL Server as the data store for a Service
    Integration Bus messaging engine:
    
    * If an attempt is made to start a messaging engine
      against a schema that does not exist, the messaging engine
      fails to start even though the "Create tables" checkbox
      is ticked and all necessary authority to create the
      schema has been granted.
      For other databases, the schema is automatically created
      under these circumstances.
    
    * If an attempt is made to run the DDL generated by
      by the sibDDLGenerator against a schema that does not
      exist, the DDL fails to create the tables for the
      messaging engine.
      For other databases, the generated DDL contains
      DDL to create the schema if it does not exist.
    
    * The sibDDLGenerator tool fails if '2008' is specified
      as the database version.
    
    * The following exception occurs and prevents startup of the
      messaging engine, when using a JDBC Version 2.0 driver:
      CWSIS1530E: The data type, -9, was found instead of the
      expected type, 12, for column, URI, in table,
      IBMWSSIB.SSIBCLASSMAP.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server using      *
    *                  Microsoft SQL Server as the data store      *
    *                  for a Service Integration Bus messaging     *
    *                  engine                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Cannot configure Microsoft SQL Server   *
    *                      as a data store when using a JDBC 2.0   *
    *                      driver, or without manually creating    *
    *                      the schema                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The behavior of the Service Integration Bus is incorrect for
    Microsoft SQL Server in the following ways:
    * The "Create tables" tickbox does not cause the messaging
      engine to automatically create the schema if it does not exist
    * The sibDDLGenerator tool does not generate DDL to create
      the schema for the messaging engine
    * The sibDDLGenerator tool does not allow '2008' to be
      specified as a database version for Microsoft SQL Server
    * A messaging engine fails to start when a JDBC 2.0 driver
      is used to connect to the database
    

Problem conclusion

  • The fix for this APAR corrects issues as follows, when
    using Microsoft SQL Server as a data store:
    * A messaging engine will automatically create a messaging
    engine's schema during startup if:
    1) It does not exist
    2) The "Create tables" tickbox is enabled
    3) The authority to query the existing schemas is available,
    using a SELECT query against SYS.SCHEMAS
    4) The authority to issue the CREATE SCHEMA command
    is available.
    * The DDL generated by the sibDDLGenerator for Microsoft
    SQL Server includes commands to create the schema.
    * The sibDDLGenerator tool accepts '2008' as a valid version
    when combined with system 'sqlserver'
    * A messaging engine can start successfully against a
    data store hosted in Microsoft SQL Server, when using
    a JDBC 2.0 driver.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.13.  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

    PM13911

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-05-06

  • Closed date

    2010-06-21

  • Last modified date

    2010-06-21

  • 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

    PLAT MSG COM

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM13911

Modified date: 21 June 2010