Maximum incoming message size

[Jim Gibson]

Is there a limit on the size of inbound messages cloverleaf can handle.  We have a new application that is sending some very large messages and twice in the last month messages have produced an “Application Error (AE) – Message does not begin with a HEADER Segment” error message even though the messages do have proper headers.  I can run the message through route tests without an error.

Both messages have been over 64000 bytes with the latest at 64074 bytes.

Anyone know of such a limit and if so, any way around it.

Thanks

Topic

[Dennis Pfeifer]

Don’t know of a limit.

Make sure that your field defs are setup, if some of the fields are very large.

also make sure that you don’t have ‘short’ timeouts..

I’ve processed messages in the 500K size.

64K .. do that routinely with EKG waveforms.

Dennis

[Alan Fleming]

We are sending PDF (in OBX 5) which can be very large. We manually edited the HL7 variant (the size for OBX 5) and are having no problems.

[Jim Gibson]

None of the fields in these messages are very large, they just like to send many OBX segments in the messages.  Some have over 300 OBX segments.

What “timeouts” are you referring to?

[Dennis Pfeifer]

oops .. you are correct.

Not time out on inbound ..

only on replies and outbound.

I guess .. make sure the sending sytem isn’t timing out waiting for an ack.

Dennis

[Jim Kosloskey]

Actually, if you are using PDL (and I am guessing you are) there is a time out potential while waiting for all of the packets.

However, normally that means you do not get the message or you get the ‘no more phrases’ error.

I am guessing you are getting a message since your proc is complaining.

A troubleshooting step I might do is to have the complaining proce echo out the message to the log so that you can see exaqctly what it is working with. I would probably couple that with the log noise level up high so I can see what is actually received and all of the activity in the engine handling the incoming message. Furthermore I would test with the above by having the sending system resend the offending message rather than resending internally.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Gibson]

Finally figured out the problem was due to the application we were sending to.  It had a 64k limit and was rejecting the messages.  I split the messages up using DSC segments and had no more errors after that.

Thanks for everyone’s replies.

Jim

[Author]

Replies