RE: [Quickfix-developers] QF 1.7.1 logon rejects

[Howard S. E. <ho...@Pi...>]

The exception is generated from generateReject (below).  It is caught =
and handled within the library.  "Tried to send a reject while not =
logged on" is logged to the event log for the session.
=20
from Session.cpp
=20
doBadTime calls generateReject, in generateReject..
=20
648:  if ( !m_state.receivedLogon() )
649:    throw std::logic_error( "Tried to send a reject while not logged =
on" );


-----Original Message-----
From: Oren Miller [mailto:or...@qu...]
Sent: Wednesday, May 26, 2004 10:28 AM
To: Howard S. Engelhart
Cc: qui...@li...
Subject: Re: [Quickfix-developers] QF 1.7.1 logon rejects


When you say it generates an exception, what sort of exception? Is it an =
exception that is being thrown from QuickFIX your application? Or an =
internal exception that is trapped and just not being logged?=20

--oren=20

On May 23, 2004, at 11:19 AM, Howard S. Engelhart wrote:=20


Using QF 1.7.1=20
A FIX client initiating a logon to my with tag 52 off by greater than =
the max latency allowed for the session was correctly prevented from =
logging on.  When the engine attempts to generate a reject it results in =
an exception because the session has not logged on.  If this is the =
desired behaviour, would it be possible to log the intended reject =
before throwing, or incorportae into the execption:=20
"Tried to send a SendingTimeAccuracy reject while not logged on"=20
or even=20
"Tried to send a reject (err=3D##,fld=3D##) while not logged on"=20
20040523-07:45:04 : Created session=20
20040523-13:35:11 : Tried to send a reject while not logged on=20
20040523-13:35:11 : Disconnecting=20
-H=20
p.s.  Thanks for a great release.  The improvements made since 1.6 are =
greatly appreciated.  Thanks.=20