Log file commands listed while an error occurred.

We have a Data Innovations Instrument Manager system, which we use for sending Lab results to our Interface Engine.

We do not want to just stop the inbound thread as it has been know to cause corruption on the inbound file. If anyone knows of a configuration setting we might use so that we can stop the thread and not corrupt files that would be great.

Also, we had an issue on 4/30 which the DI system stopped sending data, here part of the log from the inbound thread when this incident started.

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Receiving a command

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Received command: ‘di_xlate xrel_post’

[cmd :cmd :INFO/0:     di_xlate:04/30/2015 05:53:18] Doing ‘xrel_post’ command with args ‘‘

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Receiving a command

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Command client went away.  Closing connection.

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Receiving a command

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Received command: ”di_xlate’

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Cmd null in ”di_xlate’

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Receiving a command

[cmd :cmd :INFO/0:       di_cmd:04/30/2015 05:53:18] Command client went away.  Closing connection.

Normally the log looks like this.

Engine idle — 04/30/2015 05:24:45

Engine idle — 04/30/2015 05:25:05

Engine idle — 04/30/2015 05:25:25

Engine idle — 04/30/2015 05:25:45

Engine idle — 04/30/2015 05:26:05

Engine idle — 04/30/2015 05:26:25

Engine idle — 04/30/2015 05:26:45

Engine idle — 04/30/2015 05:27:06

Engine idle — 04/30/2015 05:27:26

Engine idle — 04/30/2015 05:27:46

Engine idle — 04/30/2015 05:28:06

Engine idle — 04/30/2015 05:28:26

Engine idle — 04/30/2015 05:28:46

Engine idle — 04/30/2015 05:29:06

Engine idle — 04/30/2015 05:29:46

Engine idle — 04/30/2015 05:30:06

Engine idle — 04/30/2015 05:30:26

Engine idle — 04/30/2015 05:31:06

Engine idle — 04/30/2015 05:31:26

Engine idle — 04/30/2015 05:31:46

Engine idle — 04/30/2015 05:32:06

Engine idle — 04/30/2015 05:32:26

Engine idle — 04/30/2015 05:32:46

Engine idle — 04/30/2015 05:33:06

Engine idle — 04/30/2015 05:33:26

Engine idle — 04/30/2015 05:33:46

Engine idle — 04/30/2015 05:34:06

Engine idle — 04/30/2015 05:34:26

Engine idle — 04/30/2015 05:34:46

Engine idle — 04/30/2015 05:35:14

I am wondering if anyone knows if that area where the format of the log changed would have changed the status of the thread? I am thinking that it may have changed from UP to some other status and we can create an alert for those types of incidents.

Not sure if we can recreate the issue in test, but I will ask DI. Thanks in Advance.