RE: [Quickfix-developers] BodyLength or CheckSum missing

[Brian E. <Br...@ma...>]

In my Logs\incoming file for the session, all I see is a blank line.  The
previous line and following line are completely normal and have correct
BodyLengths & CheckSums.  I suspect the message may in fact contain no data
at all.  I've added these lines to Message::validate()

...
  catch ( FieldNotFound& e) 
  {
		std::cout << "Message::validate : FieldNotFound (" <<
e.field << ") exception.  The message is:" << std::endl;
		std::cout << "'" << toString().c_str() << "'" << std::endl;
    throw InvalidMessage("BodyLength or CheckSum missing");
...

Next time it occurs, I should get a better idea.  They may be sending me a
NULL character or something.  My plan is wait until I get a record of it
occuring again, then add more logging/checks, then repeat.  I can't
reproduce the problem in the test system, so I just have to wait for it.

-----Original Message-----
From: Miller, Oren [mailto:OM...@ri...]
Sent: Tuesday, October 14, 2003 6:02 PM
To: Br...@ma...; qui...@li...
Subject: Re: [Quickfix-developers] BodyLength or CheckSum missing


Do yo have an example of a message that causes this error?

--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Brian Egge <Br...@ma...>
To: qui...@li...
<qui...@li...>
Sent: Tue Oct 14 10:10:55 2003
Subject: [Quickfix-developers] BodyLength or CheckSum missing

I seem to be having a problem where I get an InvalidMessage("BodyLength or
CheckSum missing") exception thrown from Message::validate().  When I look
at my logs, or even re-parse the message, everything is in tact.  I can't
see any reason why this exception is being thrown.  I only get this with one
venue, and it only happens every couple of days or so.  Has anyone else had
this problem before?

I've added some more logging to this area, and I think I will figure it out
soon.  The item that concerns me more is that this exception does not get
handled, and the EH eventually calls terminate() or abort() and the program
ends.  I'm using version 1.6, and I have two suggestions.

1)  "bool SocketConnection::read( SocketAcceptor& a, SocketServer& s )" has
an exception handler, while bool "SocketConnection::read( SocketConnector& s
)" does not.  My exception occurs in the latter case.  I copied the
exception code from the one read to the other to make them consistent.

2)  I added try {} catch(...) statement to the onStart() procedures, to trap
any unhanded exceptions.   I'd rather have the thread safely terminate than
for my whole app to end.   

If these changes are worthwhile, I'll try to merge them in CVS. 

-Brian


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers