Logging Request/Response Messages in the Server Log

Logging request/response (send/receive) messages can be useful for TIBCO Support when trying to debug a problem. This ability adds detailed information to the log concerning messages the client sends to the server, and the responses received back from the server. This is also known as trace message logging.

Example request/response messages in the server log are shown :

00181|0011C|07/03/2001 08:11:25.988|00010000|TRACE|SEND|10.20.30.43:44812|Len(4092)|MsgCode(QQ)
00000: 00 00 0f f8 00 00 02 5c  46 00 00 00 00 00 00 0f  |.......\F.......|
00016: fc 51 51 00 73 77 5f 64  61 6e 61 00 32 00 30 00  |.QQ.sw_quest.2.0.|
00181|0011C|07/03/2001 08:11:26.229|00000020|TRACE|RECV|10.20.30.43:44812|Len(134)|MsgCode(QQ)
00000: 00 00 02 30 73 77 61 64  6d 69 6e 0a 73 77 61 64  |...0swadmin.swad|
00016: 6d 69 6e 0a 51 51 0a 73  77 61 64 6d 69 6e 40 6d  |min.QQ.swadmin@m|

TRACE is logged in place of one of the log levels described in the previous section. This is followed by either SEND or RECV to indicate if it’s a request or response message, respectively. This is then followed by the data in the message to and from the server.

Warning: Unless directed by TIBCO Support, it is highly recommended that the request/response logging functionality be turned off. Turning this functionality on could cause an extremely large amount of information to be written to the server log. This will cause the performance and response time of TIBCO iProcess® Objects Server to be seriously degraded. It also causes the possibility of critical error messages being lost if the log file fills up and rolls over.

The default is for request/response messages to not be logged.

Request/response message logging can be turned on/off using the following:

• Object Model - Only the on-disk log tracing can be set via the object model. The following methods can be used to set log trace for the on-disk log:
— TIBCO iProcess Objects - SetLogTrace method
— TIBCO iProcess Server Objects - SetSrvLogOptions method (using the aTrace parameter)
• TIBCO iProcess Objects Server Configuration Utility:
— For on-disk logging, click in the Write request and response messages to the log check box on the Disk Log tab to enable tracing.
— For in-memory logging, click in the Write request and response messages to the log check box on the Memory Log tab to enable tracing,
• TIBCO iProcess® Objects Server Configuration File:
— For on-disk logging, locate the TRACE_MSG entry in the swentobjsv.cfg file and set it to “0” to turn off trace message logging or “1” to turn on trace message logging. For more information, see TRACE_MSG.
— For in-memory logging, locate the MEMLOG_TRACE_MSG entry in the swentobjsv.cfg file and set it to “0” to turn off trace message logging or “1” to turn on trace message logging. For more information, see MEMLOG_TRACE_MSG.