IBM Support

IT34746: LARGE NUMBER OF ERRORS IN THE SYSTEM LOGS

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

  • Customer is having a lot of errors in the system log like
    below:
    [2020-06-17 09:13:19.012] ERROR 000310040133
    UTIL.CACHE.ERR_PwdPolicyLoader_verifyKey1
    PwdPolicyLoader.verifyKey(): key is not String
    [2020-06-17
    09:13:19.012] ERROR 000310080010
    UTIL.FRAME_CACHE.ERR_CacheManager_get CacheManager.get could
    not verify the key: null . Returning null.
    
    After analysis it
    seems that they come from the SSP --> SFG communication when
    external partners connect to SI via SSP SFTP service.
    They use
    the SSP-SEAS-SI SSO configuration to authenticate their
    partners using SSH keys in SI and this is working fine.
    However
    it seems that each time an external partner connects this way,
    this creates these errors in system.log.
    
    This seems like an
    known issue that was already solved in prior version of SI that
    is now resurfacing in
    6.0.3:
    https://www.ibm.com/support/pages/apar/IT21533
    Location
    details for external files
    

Local fix

  • B2BISFG-54290
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    Customer has a series of errors, as shown below, in the system
    log:
    [2020-06-17 09:13:19.012] ERROR 000310040133
    UTIL.CACHE.ERR_PwdPolicyLoader_verifyKey1
    PwdPolicyLoader.verifyKey(): key is not String
    [2020-06-17 09:13:19.012] ERROR 000310080010
    UTIL.FRAME_CACHE.ERR_CacheManager_get CacheManager.get could not
    verify the key: null . Returning null.
    
    After analysis it seems that they come from the SSP --> SFG
    communication when external partners connect to SI via SSP SFTP
    service.
    They use the SSP-SEAS-SI SSO configuration to authenticate their
    partners using SSH keys in SI and this is working fine.
    However, it seems that each time an external partner connects
    this way, these errors are generated in the system.log.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A code fix is provided.
    Errors mentioned in the description will not be printed as
    errors but as debug statements if debug is on.
    
    Delivered in:
    6000305
    
    All future Fix Packs can be found in the Release Timeline
    Matrix:  https://www.ibm.com/support/pages/node/6194265
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34746

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    603

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-02

  • Closed date

    2021-10-05

  • Last modified date

    2021-10-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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Line of Business":{"code":"LOB02","label":"AI Applications"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"603"}]

Document Information

Modified date:
06 October 2021