IBM Support

PH60243: SETTING THE CMGRLOG LEVEL OF LOGGING TO "FAILURES" INCORRECTLY ENABLED ALL CONNECTION MANAGER LOGGING

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

  • Setting the Logging settings of log --> cmgrlog --> level to
    "failures" in the values.yaml file, incorrectly enabled all IBM
    Transformation Extender Container Connections Manager logging.
    
    This setting in the values.yaml file:
    
    # Logging settings
      log:
        includeHostInLogNames: true
        jniLog:
          # Supported levels are "none", "failures", "info" and
    "all". Default is "none".
          level: "failures"
        cmgrLog:
          # Supported levels are "none", "failures", "info" and
    "all". Default is "none".
          level: "failures"
    
    Results in the dtx.ini file setting all the Connection Manager
    logging to be on:
    [Connections Manager]
    LogTrace=1
    LogDebug=1
    LogInfo=1
    LogWarning=1
    LogError=1
    LogFatal=1
    DebugName=/logs/node1.cmgr.log
    
    When the intent is for:[Connections Manager]
    LogTrace=0
    LogDebug=0
    LogInfo=0
    LogWarning=0
    LogError=1
    LogFatal=1
    DebugName=/logs/node1.cmgr.log
    
    This results in excessive logging resulting in a performance
    impact with map execution times.
    

Local fix

  • ITXCQ - ITX00062376
    TR / TR
    Circumvention: None
    

Problem summary

  • Users Affected:
    IBM Transformation Extender users using ITX in RedHat Openshift
    Certified container.
    
    Problem Description:
    ITX logging enabled by default with the openshift certified
    container causes a performance issue.
    
    Platforms Affected:
    Linux
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH60243

  • Reported component name

    ITX

  • Reported component ID

    5724Q2300

  • Reported release

    A11

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-03-08

  • Closed date

    2024-11-04

  • Last modified date

    2024-11-05

  • 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

    ITX

  • Fixed component ID

    5724Q2300

Applicable component levels

[{"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSVSD8","label":"Transformation Extender"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A11"}]

Document Information

Modified date:
05 November 2024