Logging and Diagnostics

Logging Improvements

At the time of user signout, all EnterpriseOne related memory structures should be freed. If they are not, then the three new settings listed in the Error and Debug Logging section can help isolate the value and origin of these outstanding memory objects. These memory objects are gracefully removed when a user signs out. However, these represent a potential buildup of objects in processes that do not represent a problem in long running processes such as subsystem jobs, long running batch jobs, or if an interactive user does not sign out for a long time (such as interop jobs).

Error and Debug Logging section

Three new fields have been added to the Error and Debug Logging section:

Field

Description

Log memory diagnostics at signoff

INI Filename - /u01/jdedwards/e812/ini/JDE.INI

INI Section Name - DEBUG

INI Entry - logMemDiagsAtSignoff

Default Value - FALSE

Allowed Values:

  • TRUE

  • FALSE

This setting specifies whether or not memory diagnostics will be logged when a CallObject Kernel user session is ended or a UBE process ends. The memory diagnostics will be written to the jdedebug log.

Log JDE Cache leaks at signoff

INI Filename - /u01/jdedwards/e812/ini/JDE.INI

INI Section Name - DEBUG

INI Entry - logCacheLeaksAtSignoff

Default Value - FALSE

Allowed Values:

  • TRUE

  • FALSE

This setting specifies whether or not JDE Cache leaks will be logged when a user session is freed in an E1 Server process. Details about the leaked JDE Caches will be written to the jde log.

Log Data Pointer leaks at signoff

INI Filename - /u01/jdedwards/e812/ini/JDE.INI

INI Section Name - DEBUG

INI Entry - logDPLeaksAtSignoff

Default Value - FALSE

Allowed Values:

  • TRUE

  • FALSE

This setting specifies whether or not Data Pointer leaks will be logged when a user session is freed in an E1 Server process. Details about the leaked Data Pointers will be written to the jde log.