IBM Support

IT17990: JDBC CONNECTION FAILURE IF SERVICE TRACE IS ENABLED AND PASSWORDHAS REGULAR EXPRESSION METACHARACTERS

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

  • If Integration Server service trace is enabled and the server is
    deployed with message flows which create JDBC connections then
    connection creation can fail if the configured password has
    special characters, which are metacharacters in regular
    expression. The error shows the following exception stack.
    
    'java.util.regex.PatternSyntaxException: Dangling meta character
    * near index 0
    at java.util.regex.Pattern.error(Pattern.java:1936)
    at java.util.regex.Pattern.sequence(Pattern.java:2102)
    at java.util.regex.Pattern.expr(Pattern.java:1976)
    at java.util.regex.Pattern.compile(Pattern.java:1677)
    at java.util.regex.Pattern.<init>(Pattern.java:1349)
    at java.util.regex.Pattern.compile(Pattern.java:1034)
    at java.lang.String.replaceAll(String.java:1731)
    at
    com.ibm.broker.jdbctype4.connpool.ConnectionPoolManager.getConne
    ction(Unknown Source)
    at
    com.ibm.broker.jdbctype4.jdbcdbasemgr.JDBCType4Connection.create
    NonXAConnection(Unknown Source)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0 using JDBC Connections.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If Integration Server service trace is enabled and the server is
    deployed with message flows which create JDBC connections then
    connection creation can fail if the configured password has
    special characters, which are metacharacters in regular
    expression. The error shows the following exception stack.
    
    'java.util.regex.PatternSyntaxException: Dangling meta character
    * near index 0
    at java.util.regex.Pattern.error(Pattern.java:1936)
    at java.util.regex.Pattern.sequence(Pattern.java:2102)
    at java.util.regex.Pattern.expr(Pattern.java:1976)
    at java.util.regex.Pattern.compile(Pattern.java:1677)
    at java.util.regex.Pattern.<init>(Pattern.java:1349)
    at java.util.regex.Pattern.compile(Pattern.java:1034)
    at java.lang.String.replaceAll(String.java:1731)
    at
    com.ibm.broker.jdbctype4.connpool.ConnectionPoolManager.getConne
    ction(Unknown Source)
    at
    com.ibm.broker.jdbctype4.jdbcdbasemgr.JDBCType4Connection.create
    NonXAConnection(Unknown Source)
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

  • The product can now create JDBC Connections with regular
    expression's metacharacters in the configured password while
    service trace is active.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.9
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT17990

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-16

  • Closed date

    2017-05-25

  • Last modified date

    2017-05-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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

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

Document Information

Modified date:
23 March 2020