Re: [Quickfix-developers] QF 1.7.1 logon rejects

[Oren M. <or...@qu...>]

When you say it generates an exception, what sort of exception?  Is it=20=

an exception that is being thrown from QuickFIX your application? Or an=20=

internal exception that is trapped and just not being logged?

--oren

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

> Using QF 1.7.1
> =A0
> A FIX client initiating a logon to my with tag 52 off by greater than=20=

> the max latency allowed for the session was correctly prevented from=20=

> logging on.=A0 When the engine attempts to generate a reject it =
results=20
> in an exception because the session has not logged on.=A0 If this is =
the=20
> desired behaviour, would it be possible to log the intended reject=20
> before throwing, or incorportae into the execption:
> =A0
> "Tried to send a SendingTimeAccuracy reject while not logged on"
> or even
> "Tried to send a reject (err=3D##,fld=3D##) while not logged on"
> =A0
> 20040523-07:45:04 : Created session
> 20040523-13:35:11 : Tried to send a reject while not logged on
> 20040523-13:35:11 : Disconnecting
> -H
> =A0
> p.s.=A0 Thanks for a great release.=A0 The improvements made since 1.6 =
are=20
> greatly appreciated.=A0 Thanks.
> =A0