How to handle broken message

[Mauri Kaatrasalo]

Hi!

I had today a situation, where connecting application started to send somehow broken message.

Here are related messages from EventLog:
Disconnecting from ...
Discarding leftover input ''
Disconnecting due to ERROR <EnsEDIHL7>ErrEndBlock: Received unexpected EndBlock 'lr' in input "lr", expected 'er, on |TCP|11412'
Returning unused unexpected 1-char segment 'l'
New connection on port 11412 from ...

I think Ensemble doesn't send any ack or nak in this situation, because it doesn't catch any message from service.

Connecting application tried to send broken message about an hour before it gave up.

I wonder what should I need have done, if connecting application wouldn't have given up resending broken message. I propably should have to code a COS routine listening that port and have that taken broken message in and sending ack back.

And wonder too, that why service didn't send alert, even I have there AlertOnError=True.

Does anyone know, if there is possibility to log service/operation input/output to a file? Like with SOAP there is just nice hook:
s ^ISCSOAP("Log") = "ios"
s ^ISCSOAP("LogFile") = "mysoaplog.log"
and you can get all SOAP workload in file.

I missed broken message this time, was just configuring WireShark to log data when connecting application gave up resending broken message.

Our version is like this:
Cache for Windows (x86-64) 2010.2.2 (Build 600_0_10092U) Tue Jan 18 2011 11:52:02 EST

Best regards, Mauri