IBM Support

PI99552: RIT ENGINE LOGFILE DOES NOT CONTAIN INSTANCE NUMBER AFTER ROLLOVER

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The RIT 9.2 engine logfile does not always show for which
    instance the engine logfile is logging. This situation occurs
    when the engine logfile is rolled-over due to the set limit.
    
    E.g when the instance is started a new engine logfile is
    generated which will contain the following loglines for example:
    INFO: instanceName: instance3
    Jun 21, 2018 3:24:49 PM
    com.ghc.ghTester.commandline.CmdLineRunTests
    commandLineArgumentsLogging
    INFO: instanceUUID: cc72b097-ccd8-4d18-95ee-7df707033dc5
    Jun 21, 2018 3:24:49 PM
    com.ghc.ghTester.commandline.CmdLineRunTests
    commandLineArgumentsLogging
    INFO: agentId: bd7cc8c0-34bc-4437-aa0d-585c3d80052b
    
    
    But when the file is rollover (due to setting
    engine.java.util.logging.FileHandler.limit) it's no longer
    possible to determine for which instance the engine logfile is
    logging.
    
    In RIT 9.2 the VirtualAppInstance number is always shown in
    front of the logentry. Is this still possible or did I
    reconfigure the logile settings not to show it?
    e.g.
    
    INFO: VirtualAppinstance147 (149): at
    com.ghc.ghTester.stub.messageswitch.FilterCaseAction.execute(Fil
    terCaseAction.java:156)
    Jun 21, 2018 3:18:02 PM
    com.ghc.appfactory.WaitForExit$MyCallBack onLine
    INFO: VirtualAppinstance147 (149): at
    com.ghc.ghTester.runtime.actions.GHTesterAction.execute(GHTester
    Action.java:107)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of Rational Integration Tester Agents with Log files.  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When agents and engine log files roll over, useful           *
    * information such as the engine instance name is no longer    *
    * available in the new file.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 9.2.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI99552

  • Reported component name

    RATL INTEGRA TE

  • Reported component ID

    5725G79IT

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-26

  • Closed date

    2018-10-03

  • Last modified date

    2018-10-03

  • 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

    RATL INTEGRA TE

  • Fixed component ID

    5725G79IT

Applicable component levels

  • R800 PSN

       UP

  • R801 PSN

       UP

  • R850 PSN

       UP

  • R851 PSN

       UP

  • R860 PSN

       UP

  • R870 PSN

       UP

  • R871 PSN

       UP

  • R900 PSN

       UP

  • R901 PSN

       UP

  • R910 PSN

       UP

  • R911 PSN

       UP

  • R920 PSN

       UP

  • R921 PSY

       UP



Document information

More support for: Rational Test Workbench

Software version: 920

Reference #: PI99552

Modified date: 03 October 2018