jde_Pid_Date.log
jdedebug_Pid_Date_Index.log
Prior to 898 multiple processes like activconsole,UTBrowse.exe,Busbuild etc write the logging information to the same set of jde.log,jdedebug.log.As a result the file will grow very fast and reach the limit.jdedebug_Pid_Date_Index.log
Also there exists some difficulty in isolating the issues when all of them write to the same logs.
Now with 8.98, each process will have its own set of logs with a suffix of ProcessID,Date and an optional Index.
The maxDebugFileSize setting lets you chose the ceiling on the size of the debug.log .It can be anywhere between 0-2GB.Once the maxDebugFileSize is reached the current debug file will be renamed with a suffix Index _1.If index _n already exists _n+1 will be suffixed....and new debug.log will be created.
The concept of one set of logs to per process is taken from the Enterprise Server and the rollover functionality is taken from the JAS Server.
Note: If output=None in the jde.ini, then all the processes will write the info to same jde.log and jdedebug.log [ofcourse it will contain anything].
Inshort
output=None <----- one jde.log,jdedebug.log for all the processes. output=FILE <----- jde_pid_CurrentDate.log, jdedebug_Pid_CurrentDate_Index.log If you are used to the previous logging mechnism it will take some time to like this.Because to view the logs, you have to find the Pid of that process from taskmanager and then go the logs by date.But once you start using it, you will feel it easy in isolating the issues quickly. Tip:Instead writing the logs to c:\ point it to c:\logs or sth like that.This way you will not mess up with other files in the c drive.
No comments:
Post a Comment