Warning Message on Acknowledgements

This topic has 5 replies, 4 voices, and was last updated 9 years, 1 month ago by Heidi Haafke.

Creator

Topic
October 12, 2015 at 6:58 pm #54846
Heidi Haafke
Participant
Hello. I am cleaning up some error log issues and am not clear how to troubleshoot this warning message on acknowledgement messages back from a down-stream system.

tcp :read:WARN/0:to_quantum_orm:10/12/2015 14:03:08] Nonmessage data received. Enable tcp/read/info/0 to see detail

We do get successful acks back from this application (which we log),

On the outbound thread configuration, I set the Msg EO Config to “enable_all” — excerpt from log is below with this on.

Can anyone shed light on how I troubleshoot? I am not clear on what it means to enable tcp/read/info/o to see detail.

msg: 0x03E012C8

msgType : REPLY

msgClass : PROTOCOL

msgState : Unknown: 0 (0)

msgPriority : 5120

msgRecoveryDbState: Log:new (2)

msgFlags : 0x8002

msgMid : [0.0.87661297]

msgSrcMid : midNULL

msgSrcMidGroup : midNULL

msgHostId : 3145399717

msgOrigSrcThread : to_quantum_orm

msgOrigDestThread : fr_mt_rad_orm

msgSrcThread : to_quantum_orm

msgDestThread : fr_mt_rad_orm

msgXlateThread :

msgSkipXlate : 0

msgSepChars :

msgNumRetries : 0

msgGroupId : 0

msgDriverControl :

msgRecordFormat :

msgRoutes :

msgUserData :

msgStaticIsDirty : 1

msgVariableIsDirty: 1

msgTimeStartIb : 1444672988.829

msgTimeStartOb : 1444672988.829

msgTimeCurQueStart: 0.000

msgTimeTotalQue : 0.000

msgTimeRecovery : 1444672988.829

msgEoConfig : 0x03E4C830

msgData (BO) : 0x03E013B0

message : ‘MSH|^~&||||||||111795634||x0dMSA|AA|111795634|OKx0d’

[msg :Msg :INFO/0:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661297] Writing to recovery database

[dbi :rlog:INFO/1:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661297] Write msg to recovery db w/state IB pre-SMS

[tcp :read:WARN/0:to_quantum_orm:10/12/2015 14:03:08] Nonmessage data received. Enable tcp/read/info/0 to see detail

[pd :thrd:DBUG/3:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661297] IB message in encoding conversation

msg: 0x03E012C8

msgType : REPLY

msgClass : PROTOCOL

msgState : IB pre-SMS (1)

msgPriority : 5120

msgRecoveryDbState: Log:update (3)

msgFlags : 0x8002

msgMid : [0.0.87661297]

msgSrcMid : midNULL

msgSrcMidGroup : midNULL

msgHostId : 3145399717

msgOrigSrcThread : to_quantum_orm

msgOrigDestThread : fr_mt_rad_orm

msgSrcThread : to_quantum_orm

msgDestThread : fr_mt_rad_orm

msgXlateThread :

msgSkipXlate : 0

msgSepChars :

msgNumRetries : 0

msgGroupId : 0

msgDriverControl :

msgRecordFormat :

msgRoutes :

msgUserData :

msgStaticIsDirty : 0

msgVariableIsDirty: 0

msgTimeStartIb : 1444672988.829

msgTimeStartOb : 1444672988.829

msgTimeCurQueStart: 0.000

msgTimeTotalQue : 0.015

msgTimeRecovery : 1444672988.829

msgEoConfig : 0x03E4C830

msgData (BO) : 0x03E013B0

message : ‘MSH|^~&||||||||111795634||x0dMSA|AA|111795634|OKx0d’

[sms :sms :INFO/0:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661297] SMS Received msg

[sms :sms :INFO/0:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661297] Driver processing msg

[pd :pdtd:INFO/2:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661313] Writing msg to inbound save file to_quantum_orm_ack

[pd :thrd:INFO/0:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661313] Placing msg on IB pre-SMS queue.

[pd :pdtd:INFO/3:to_quantum_orm:10/12/2015 14:03:08] [0.0.87661313] IB pre-SMS message details

Regards, Heidi

Senior Systems Integration Analyst
IT Imaging and Integration Services
UPMC Pinnacle
heidi.haafke@pinnaclehealth.org
Creator

Topic

Viewing 4 reply threads

Author

Replies
- October 13, 2015 at 2:31 pm #83199
  Robert Milfajt
  Participant
  The only thing odd I see with the ACK is the lack of a message type in MSH-9. I’m not sure how you have your thread configured to receive ACKs, but if the Inbound Replies has Trx ID Determination Format of HL7, that might explain the warning. If you do have HL7 there, try Fixed Record Layout and see if that makes the warning disappear.
  
  Why is the vendor sending such a lean MSH segment? Most applications either copy the MSH sent to them and echo it back (minimally) or build a more complete one with reversed sending/receiving information and ACK in MSH-9 (ideally).
  
  Hope this helps,
  
  Robert Milfajt
  Northwestern Medicine
  Chicago, IL
- October 14, 2015 at 3:20 pm #83200
  David Barr
  Participant
  My guess is that there are extra characters that are sent before the message start or after the message stop characters. I don’t see them in the portion of the log file that you shared. Maybe you can run tcpdump or another network debugging utility to see the complete data.
- October 28, 2015 at 9:19 pm #83201
  Heidi Haafke
  Participant
  Thanks Robert and David.
  
  I tried both suggestions. Setting the Trx ID Determination Format to FRL not help in this particular case, however.
  
  So I used the engine output configurator to get more info on the acks back similar to what David suggested. Below is EO on one ack back:
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] input buffer accepted 53 bytes
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 0b 4d 53 48 7c 5e 7e 5c |.MSH|^~|
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 26 7c 7c 7c 7c 7c 7c 7c |&||||||||
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 7c 31 31 32 36 35 39 39 ||1126599|
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 38 39 7c 7c 0d 4d 53 41 |89||.MSA|
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 7c 41 41 7c 31 31 32 36 ||AA|1126|
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 35 39 39 38 39 7c 4f 4b |59989|OK|
  
  [tcp :read:DBUG/0:to_quantum_orm:10/28/2015 15:48:43] 0d 1c 0d 1c 0d |…..|
  
  [tcp :read:WARN/0:to_quantum_orm:10/28/2015 15:48:43] Nonmessage data received. Enable tcp/read/info/0 to see detail
  
  Just not sure how to interpret the hex — if anyone can help interpret the culprits, I am assuming the problem is in the line that reads
  
  “0d 1c 0d 1c 0d |…..|”.
  
  Thanks again for everyone’s input. Heidi
  
  Senior Systems Integration Analyst
  IT Imaging and Integration Services
  UPMC Pinnacle
  heidi.haafke@pinnaclehealth.org
- October 29, 2015 at 12:21 am #83202
  Jim Kosloskey
  Participant
  Yup that is it.
  
  Contact the system sending the ack, give them a copy of this EO and tell them to read thee HL/7 standard.
  
  They should fix this (sounds like a typical rookie coding error to me).
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- October 29, 2015 at 11:07 am #83203
  Heidi Haafke
  Participant
  Thanks, Jim, and all. Will do that and see that they can handle that.
  
  Senior Systems Integration Analyst
  IT Imaging and Integration Services
  UPMC Pinnacle
  heidi.haafke@pinnaclehealth.org
Author

Replies

Viewing 4 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.