|
4.0 Session
< Previous Next >
Re: fix 4.2 error
Vinod Patil / Asian CERC
10 Sep 2008 1:24AM ET> Hello,
>
> We are using quickfixj as order management system.
> acceptor run for 10 minutes and stop with below error.
>
> 20080809-06:15:04, FIX.4.2:SERVER1->CLIENT1, event>
> (quickfix.SessionException Logon state is not valid for message
> (MsgType=D))
>
> <20080809-06:15:13, FIX.4.2:SERVER1->CLIENT1, event> (MsgSeqNum too
> high, expecting 4173649 but received 4363760)
>
> We are unable to understand why this happens and what is solution?
> a. Is this problem with Session getting expired or connection
> broken. b. Why is range difference so large? (4363760 - 4173649)?
> b. How do I trap this session message so that I can give a reset
> message or resend from particular sequence number. please send me
> code for this. should this method be invoked from logon() or
> toAdmin() methods of acceptor.
> c. Is there any way I can catch current SessionState?
>
>
> Thanks
QuickFIXJ is an FIX Engine and if you integrated it with your OMS properly still the session management for any FIX server depends on following minimum things which I experienced:
1) System Time at acceptor and initiator, this should be same.
2) May be the connection is breaking
3) Check the heartbeats at both initiator and acceptor which should be same
But I think there is something wrong in the log files. As per the problem you stated you are new to quickfixj and the messages seq number is too high for that. Please clear the log files at both acceptor and initiator and try to run the both again.
Also see that the initiators entry is registered in the cfg file of acceptor and QuickFIXJ doesn't allow more than one client with same details to make connection with the acceptor.
Re: fix 4.2 error
Vinod Patil / Asian CERC 10 Sep 2008 1:24AM ET
|
