IBM Support

IT32608: AUTO CONNECTION RECYCLING OF ACTIVE DATABASE CONNECTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as requirement.

Error description

  • This is a new function apar to address following :
    
    1) Add a
    new database manager setting to control automatic recycling of
    ODBC connection after a certain number of transactions as
    counted in terms of commit/rollback.
    2) Report the number of transactions
    on each connection and also connection age via
    mqsireportproperties.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and App Connect Enterprise
    V11 using ODBC connections to databases.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    This is a new function apar to address following enhancement to
    DatabaseConnectionManager object.
    
    1) Provide  a new database manager object setting to control
    automatic recycling of  ODBC connection after a configured
    number of transactions
    2) Report the number of transactions  on each datasource
    connection
    3) Report connection age for each datasource connection.
    

Problem conclusion

  • The product has been enhanced to provide a new configurable
    property on DatabaseConnectionManager object -
    'maxConnectionUseCount'.
    
    To activate this feature,  set maxConnectionUseCount > 0  using
    mqsichangeproperties command.
    
    For example,
    Use following command to reset ODBC connection after every 100
    transactions (which includes commits and rollbacks) for each
    Datasource connection on a thread.
    
    mqsichangeproperties  <Int Node>  -e <Int Server>  -o
    ComIbmDatabaseConnectionManager -n maxConnectionUseCount -v 100
    
    Use mqsireportproperties  command to know the current number of
    transactions and connection age in seconds on each datasource
    connection.
    These values are represented by transactionCount and
    connectionAge fields respectively  in the output as shown below.
    
    mqsireportproperties <Int Node>  -e <Int Server> -o
    ComIbmDatabaseConnectionManager -r
    
    ComIbmDatabaseConnectionManager
      uuid='ComIbmDatabaseConnectionManager'
      userTraceLevel='none'
      traceLevel='none'
      userTraceFilter='none'
      traceFilter='debugTrace'
      statementCacheSize='40'
      maxStatementAge='600'
      maxConnectionUseCount='100'
      maxConnectionAge='60'
      useDefaultSchemaForStoredProcedures='true'
      enableODBCTraceBridge='true'
      expireXAConnections='false'
    DatabaseContext
      threadNumber='3819'
      ODBC_Version_3
        envHandle='139961038995136'
    DatabaseContext
      threadNumber='3824'
      ODBC_Version_3
        envHandle='139961240340928'
        DataSource
          name='TESTDB1'
          timeoutEnabled='true'
          coordinated='false'
          state='2'
          transactionCount='1'
          connectionAge='3'
          ManagedStatement
            text='INSERT INTO TEST VALUES (?)'
            createTime='2020-07-14 07:30:23.280630 (1594711823)'
            lastExecuteTime='2020-07-14 07:30:23.282599
    (1594711823)'
            executeCount='1'
        DataSource
          name='TESTDB2'
          timeoutEnabled='true'
          coordinated='false'
          state='2'
          transactionCount='1'
          connectionAge='3'
          ManagedStatement
            text='INSERT INTO TEST VALUES (?)'
            createTime='2020-07-14 07:30:23.369659 (1594711823)'
            lastExecuteTime='2020-07-14 07:30:23.372099
    (1594711823)'
            executeCount='1'
    

Temporary fix

Comments

  • AUTO CONNECTION RECYCLING OF ACTIVE DATABASE CONNECTIONS
    

APAR Information

  • APAR number

    IT32608

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED REQ

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-20

  • Closed date

    2020-08-27

  • Last modified date

    2021-04-28

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

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

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
29 April 2021