![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The logfile configuration parameter in tibemsd.conf controls the location and the name of the log file.You can specify that the log file should be backed up and emptied after it reaches a maximum size. This allows you to rotate the log file and ensure that the log file does not grow boundlessly. The logfile_max_size configuration parameter allows you to specify the maximum size of the current log file. Set the parameter to 0 to specify no limit. Use KB, MB, or GB units.For example, if the current log file is named tibems.log, the first copy is named tibems.log.1, the second is named tibems.log.2, and so on. Similarly, if the highest sequence number in use when the server starts is 19, or tibemsd.log.19, then the next backup file created will be named tibemsd.log.20. This is true even if you removed tibemsd.log.19 and all other log files after the server started.If logfile_max_count is specified, the server keeps at most the number of log files specified by that parameter, including the current log file. When the maximum number of log files has been reached and the server needs to back up the current log file, it deletes the oldest log file (the ones with smallest number). If you change the parameter setting, after the server is restarted, the next time it needs to rotate the log file it deletes however many of the lowest sequence numbered files required to reach the logfile_max_count maximum.You can also dynamically force the log file to be backed up and truncated using the rotatelog command in tibemsadmin. See Command Listing for more information about the rotatelog command.
• By configuring the log_trace and/or console_trace parameters in the tibemsd.conf file; see Table 17.
• By specifying the -trace option when starting the server
• By using the set server command when the server is running.log_trace and console_trace can be used to configure what types of messages are to go to the log file and to the console.
When you want trace messages to be sent to a log file, you must also configure the logfile configuration parameter. If you specify log_trace, and the logfile configuration parameter is not set to a valid file, the tracing options are stored, but they are not used until the server is started with a valid log file.When configuring log or console tracing, you have a variety of options for the types of trace messages that can be generated. Table 81 describes the available tracing options.
• + A trace option preceded by + adds the option to the current set of trace options.
• - A trace option preceded by - removes the option from the current set of trace options.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |