LO64693: EXCEPTION DURING STARTUP ARE NOT WRITTEN TO LOG FILE

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

• This fix is included in Lotus Traveler 8.5.3.1 and
  all future releases.  See this technote for the latest Lotus
  Traveler maintenance information:
  
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

Comments

APAR Information

• 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