Log Flags for Client-Side Diagnostics

The client middleware proxy can be enabled to log additional diagnostic information. In some cases this information is redundant with the MES middleware service logging on the server side. However, setting client-side log flags can be useful if you are working at the client or if the node on which the middleware service is running is logging too many log entries to make sense of them.

FactMES.Server.Proxies Assembly

LogDataChangeEvents

Logs each data change event, including error events.

LogDeadlocks

Logs each deadlock retry. Errors resulting from exceeding the retry count are always logged.

LogErrorXML

Logs the XML content for XML messages that fail.

LogEvtBrokerHeartbeat

Logs subscriptions, when subscriptions are canceled, when the heartbeat is refreshed, and when subscriptions are processed.

LogSequenceDetails

For a call being made from the client, logs the sequence key and sequence number of the message that is being processed asynchronously.

LogValidationError

For a call being made from the client, logs the message that was submitted if its validation fails when the synchronous or asynchronous command fails or when the event broker subscription fails.

Start-Stop

When this flag is turned on, the steps that are executed when connecting the client middleware proxy to the middleware are logged. The step log entries contain the context data at each step. The context data can help with diagnosing connection issues.

Note: It is strongly recommended to turn on this flag only for diagnostic purposes. This is because when this flag is on, several messages will be logged by the Logger every time that the client middleware proxy pings the middleware to verify that the connection is working.

Trace

Logs every XML message and its response as they go through the WCF Proxy. It also shows all EventBroker subscriptions and re-subscriptions.