Outbound thread freezes in Processing OB-Data message queue

[Jeanne Cole]

Good Morning,

We have a 5.7MB outbound thread, using a fileset-local protocol writing to a folder on a shared drive, processing large messages (>70,000 bytes in OBX5) – that will freeze when trying to write the message.  Any ideas on what we should be looking at to determine what is causing this?  In the successful example below – the next step is ‘Writing message to Protocol Driver fileset’ – so thinking it might be the protocol, but need help in troubleshooting.

Thanks in advance for your help!

Jeanne

Example of the freeze and of successful processing below:

Outbound thread freezes:

[msg :Msg :INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:17:38] [0.0.258162263] Updating the recovery database

[dbi :rlog:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] [0.0.258162263] Update msg in recovery db to state OB post-SMS

[pti :sche:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] Thread has 0 ready events left.

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has 1 msgs

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has SOME work

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has 1 msgs

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has SOME work

[pti :sche:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] Thread has 1 ready events.

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has 1 msgs

[pd  :thrd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:17:38] OB-Data queue has SOME work

[pd  :thrd:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:17:38] Processing OB-Data message queue

Outbound thread processes successfully:

[pd  :thrd:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:16:39] Processing OB-Data message queue

[pd  :pdtd:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Writing message to Protocol Driver fileset

[fset:wrte:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:16:39] Parsing control string ‘{OBFILE copath_111366.HT} {OBAPPEND 0} {OBSTYLE hl7}’

[fset:wrte:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Over/writing to \USMKE1DTSVM28llogicLLOGICRWJEMRDTS1datainCoPath/copath_111366.HT

[pd  :pdtd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:16:39] Set driver status to PD_STATUS_UP

[pd  :pdtd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Writing message succeeded

[pd  :pdtd:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Latencies: Outbound 0.234, Que 0.015, Total 0.578 secs

[dbi :rlog:INFO/1:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Update msg in recovery db to state OB delivered OK

[pd  :pdtd:INFO/2:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Writing msg to outbound save file rwjuh_note_copath

[pd  :thrd:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Invoking SENDOK

[dbi :rlog:INFO/0:rwjuh_note_copath_tgt:10/11/2016 00:16:39] [0.0.258162185] Delete message from recovery database

Topic

[Robert Kersemakers]

Hi Jeanne,

Is the thread possibly waiting for a reply?

Happened to me more than once that I had copied a tcp/ip thread and changed the protocol into file-set. But forgetting to erase all the ‘Outbound’ settings, causing the thread to write to a file and thenwait for a reply.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies