E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (1)
View Page History
...
{section} ** the content of service request and reply is dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the file name of the dumped message is added as a new attribute {{payloadContentDumpFile}} of the MONIT log trace.
** the file name of the dumped message is added as a new attribute {{payloadContentDumpFile}} of the MONIT log trace.
h1. Dumping exchange content
When you activate the log handler {{PetalsExchangeDumperFileHandler}}, any log message is saved as following:
* the log trace is logged in the log file identified by the following pattern: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/petals.log}}
* for log trace with level MONIT:
** the content of the message exchange dumped in a file identified as following: {{$PETALS_HOME/logs/flow-monitoring/<flow instance id>/<flow step id>_<trace code>.xml}}
** the exchange content logged is composed of:
*** message exchange identifier,
*** message exchange pattern,
*** message exchange status,
*** interface name of the service provider invoked,
*** service name of the service provider invoked,
*** endpoint,
*** name of operation invoked,
*** message exchange properties,
*** normalized messages "IN", "OUT" or "Fault" of the message exchange, with for each normalized message:
**** normalized message properties,
**** normalized message content, the XML payload,
**** attachments, with for each attachment:
***** attachment name,
***** attachment size if available,
***** attachment content, that will be available in a next version,
*** error if exists.