In-Memory Log File

With this method of storing log messages, you can ensure that log messages are stored in memory during server operations, rather than on disk. The log is written to disk if the server terminates. This method of TIBCO iProcess® Objects Server logging can be used if the performance impact of using the “standard” on-disk logging is too great (especially when logging at the debug level).

Note: In-memory logging is available only if your TIBCO iProcess® Objects Server has CR 14205 implemented.

This method of logging is turned off by default. To turn it on, perform the following steps:

• Windows - Check the Enable Memory Logging check box on the Memory Log tab using the TIBCO iProcess® Objects Server Configuration Utility. This then enables the rest of the selections on the tab so you can set the in-memory log level and categories.
• UNIX - Set the MEMLOG_LEVEL TIBCO iProcess® Objects Server configuration parameter to a value from 1 (error level) to 4 (debug level). A setting of zero disables in-memory logging.

For more information, see the MEMLOG_LEVEL parameter on MEMLOG_LEVEL.

Writing the In-Memory Log to Disk

The following describes the ways in which the in-memory log is written to disk (if in-memory logging is enabled):

• If TIBCO iProcess® Objects Server crashes, an attempt is made to automatically write the in-memory log to a file.
Note:

This only occurs if the "auto dump" feature has been turned on in the engine (using the PROCESS_AUTO_DUMPLOG process attribute). If auto dump is enabled (the default), the contents of the processes’ debug shared memory segment is written to disk when that process fails.

For more information, see TIBCO iProcess Engine Administrator’s Guide.

• You can manually write the in-memory log to a file using the swsvrmgr DUMPLOG command (even when the server is still running). The syntax is: 
swsvrmgr DUMPLOG [<MachineName>|<MachineID>[<ProcessName>[<ProcessInstance>]]]
Note: If the server crashes, and the log cannot be written to a file for some reason, the shared memory containing the log may still exist. If the shared memory still exists, you can manually write the in-memory log to a file by using the swsvrmgr DUMPLOG command shown above.