IBM Support

IT23475: SSP LOG MESSAGES IN DEBUG LEVEL LOGGING INSTEAD OF ALWAYS. CAUSED MISMATCH OF LOG LEVELS OF LOG4J2 (SSP)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Perimeter Services Messages ALWAYS getting logged only under
    DEBUG.
    There are 2 logging messages that changed from INFO to DEBUG in
    the SSP/PS logs.
    
    MemoryManager (SingleBar strategy) current allocated bytes: n,
    current count: n, high water mark: n, h.w.m. count: n, denied
    preallocations: n - (This message comes out every 10 minutes by
    default)
    
    PhysicalConnectionManager connections: active: n, listening: n,
    loopback: n - (This message comes out every 2 minutes by
    default)
    
    Background:
    We noticed that the upgrade from PS4660 to PS4662 moved these
    messages from ALWAYS to DEBUG.  The messages are still produced
    every 2 minutes or 10 minutes, but only in DEBUG mode.  Here is
    an example from SSP 3.4.2.0, Fix 11+, Build 397:
    
    % egrep "Memory|connections" perimeter.log
    07 Sep 2017 10:14:08,464 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - MemoryManager (SingleBar
    strategy) current allocated bytes: 299, current count: 3, high
    water mark: 131,944, h.w.m. count: 5, denied preallocations: 0
    07 Sep 2017 10:14:46,655 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    07 Sep 2017 10:16:46,690 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    07 Sep 2017 10:18:46,718 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    07 Sep 2017 10:20:46,754 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    07 Sep 2017 10:22:46,788 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    07 Sep 2017 10:24:08,466 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - MemoryManager (SingleBar
    strategy) current allocated bytes: 299, current count: 3, high
    water mark: 131,944, h.w.m. count: 5, denied preallocations: 0
    07 Sep 2017 10:24:46,809 DEBUG [Dispatcher]
    com.sterlingcommerce.perimeter - PhysicalConnectionManager
    connections: active: 3, listening: 2, loopback: 2
    etc..
    

Local fix

  • STRRTC : 550295
    SF/SF
    Circumvention: None
    

Problem summary

  • Customer noticed that after SSP upgraded the PS from PS4660 to
    PS4662 these periodic 'ALWAYS' log messages were only getting
    logged as DEBUG messages. The messages have value, but not at
    the expense of running the PS in DEBUG mode:
           MemoryManager (SingleBar strategy) current allocated
    bytes: n, current count: n, high water mark: n, h.w.m. count:
    n, denied preallocations: n - (This message comes out every 10
    minutes by default)
           PhysicalConnectionManager connections: active: n,
    listening: n, loopback: n - (This message comes out every 2
    minutes by default)
    

Problem conclusion

  • Added the 'ALWAYS' log level in SSP to match the one in PS.
    

Temporary fix

  • SSP3430 iFix 5 Plus Build 194
    

Comments

APAR Information

  • APAR number

    IT23475

  • Reported component name

    STR SECURE PROX

  • Reported component ID

    5725D0300

  • Reported release

    343

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-12-12

  • Closed date

    2017-12-21

  • Last modified date

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

    STR SECURE PROX

  • Fixed component ID

    5725D0300

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PNW","label":"Sterling Secure Proxy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"343","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
22 May 2025