Product Documentation

Knowledgebase

Previous Topic

Next Topic

How to Reproduce a Problem Using TRAPCOMM.FCS

The DIAGNOSTICS TRAP_COMM keyword instructs the FairCom Server to log incoming communications packets to a file called TRAPCOMM.FCS prior to execution. If a copy of the initial data and index files are preserved, this log can be played back using the cttrap utility and a debug build of the FairCom Server to observe the results of the client requests. This allows client activities to be exactly duplicated and repeated.

The following is a step-by-step procedure on how to produce a TRAPCOMM.FCS file.

These instructions are intended for a FairCom Server operator or administrator who is experiencing a problem and would like to help FairCom Support by creating a reproducible case. Please follow these steps:

  1. Cleanly shut down the FairCom Server and remove the *.FCS files (you may want to move them to a backup directory).
  2. Back up all the data you are going to access.
  3. Start the FairCom Server with DIAGNOSTICS TRAP_COMM in ctsrvr.cfg.
  4. Start your client applications and reproduce the error.
  5. Shut down the FairCom Server.

At this point you should have a TRAPCOMM.FCS file that contains all the client requests sent to the server. You can use this file to re-play the requests with the cttrap utility.

To replay the TRAPCOMM.FCS please follow these steps:

  1. Cleanly shut down the FairCom Server and remove the *.FCS files.
  2. Restore the data that you backed up before running the TRAP_COMM instance.
  3. Start the FairCom Server without the DIAGNOSTICS TRAP_COMM in ctsrvr.cfg.
  4. Run cttrap passing the TRAPCOMM.FCS file path as command-line argument.

See Also:

TOCIndex