IBM Support

LO64693: EXCEPTION DURING STARTUP ARE NOT WRITTEN TO LOG FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Exceptions are usually displayed in the console and written to
    the NTSErrors log file.  However if this occurs during startup,
    like the defrag routine, these aren't captured.
    

Local fix

  • n/a
    

Problem summary

  • Customer reported the Lotus Traveler Database Defrag function
    failed to run successfully, but no message was displayed as to
    why.
    

Problem conclusion

  • The fix is actually just to log the error.  The defrag command
    terminated because the Java stack ran out of memory.  The
    solution is to simply increase the amount of memory used by the
    Lotus Traveler server, but the user would not know that since
    the out of memory error was not logged.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO64693

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    852

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-13

  • Closed date

    2011-11-11

  • Last modified date

    2011-11-11

  • 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

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R852 PSY

       UP

  • R853 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"}, "Product":{"code":"SSYRPW","label":"Lotus Notes Traveler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.2","Edition":""}]

Document Information

Modified date:
11 November 2011