Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# TRACE_MSG

It is a flag (0=NO and 1=YES) that specifies whether a client request and response messages should be traced to the log file. Note that even if this parameter is set to “0” (No), messages will still be traced if LOG_LEVEL (see LOG_LEVEL) is set to “4” (Debug). In addition, only transactions that are specified through the LOG_CATEGORIES are traced.

Warning: Unless directed otherwise by TIBCO support, ensure that TRACE_MSG is set to “0” (No). Setting this parameter to “1” could cause the log file to quickly fill. This could cause critical error messages to be overlooked or lost when the log reaches its maximum size and is truncated. Turning this parameter on will degrade the performance and response time of the TIBCO iProcess® Objects Server.

Values: 0 or 1
Default: 0

Process Attribute | Description
`TRACE_MSG` Type : Integer Range : 0 (no) or 1 (yes) Default : 0 | Flag specifying if client request and response messages should be written to the log file. This process attribute can be changed while the TIBCO iProcess Objects Server is running.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine

Copyright © 1994-2024. Cloud Software Group, Inc. All Rights Reserved.