Setting the TIBCO Enterprise Message Service (EMS) server log trace using the tibemsadmin command“set server log_trace=trace-items” on an already running EMS server results in no tracing information.
book
Article ID: KB0094226
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Message Service
-
Not Applicable
-
Description
Resolution: Description: =========
1). The EMS server is already running.
2). Set the server parameters “tcp://localhost:7222> set server log_trace=DEFAULT,+MSG,+PRODCONS”.
3). No tracing information is generated by the EMS server.
Environment: ==========
All versions of EMS.
Resolution: ========
For trace messages to be sent to a log file, you must also configure the logfile configuration parameter. If you specify only "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 restarted with a valid log file.
To make the log tracing effective you need to have the “logfile“ parameter set. If the EMS server “logfile “ parameter is not set then the EMS server will not log the information to file as by default, if not specified, logging to file is disabled.
Whenever an EMS server is started it takes the configuration information from the main configuration file “tibemsd.conf” file of the EMS installation. The only way to log the EMS server information to the file is to:
1). Stop the already running EMS Server.
2). In the main configuration file “tibemsd.conf”, specify the logfile = <Log file name and location to store the LOG file> log_trace = <trace-items>
3). Restart the EMS server.
The logfile will be created in the specified location with the defined <trace-items> tracing information.
Issue/Introduction
Setting the TIBCO Enterprise Message Service (EMS) server log trace using the tibemsadmin command“set server log_trace=trace-items” on an already running EMS server results in no tracing information.