Re: [Quickfixj-users] Not reconnecting after Timed out waiting for heartbeat

[thannon <th...@ft...>]

Just a shot in the dark...

Try removing the following setting from your configuration:
DisconnectOnError=Y

Regards - Tommy


Dan Corneanu wrote
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> 
> 
> 
> Hello list,
> I have a QuickFixJ initiator application that sometimes gets stuck after a
> heartbeat timeout and does not try to reconnect again.
> 
> Here are the last lines from my log file:
> 
> 2016-06-16 03:11:41.572  INFO 40764 --- [ssage Processor]
> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
> 8=FIX.4.29=6435=034=376849=OMFDTSDEMO52=20160616-03:11:41.55756=TTDS68BO10=172
> 2016-06-16 03:11:42.373 ERROR 40764 --- [      QFJ Timer]
> quickfixj.errorEvent                     : FIX.4.2:OMFDTSDEMO->TTDS68BO:
> Disconnecting: Timed out waiting for heartbeat
> 2016-06-16 03:11:43.413  INFO 40764 --- [ NioProcessor-2]
> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377952=20160616-03:11:03.73910=062
> 2016-06-16 03:11:46.740 ERROR 40764 --- [ssage Processor]
> quickfixj.errorEvent                     : FIX.4.2:OMFDTSDEMO->TTDS68BO:
> quickfix.SessionException Logon state is not valid for message (MsgType=0)
> 2016-06-16 03:11:46.758  INFO 40764 --- [ssage Processor]
> quickfixj.event                          : FIX.4.2:OMFDTSDEMO->TTDS68BO:
> Already disconnected: Verifying message failed: quickfix.SessionException:
> Logon state is not valid for message (MsgType=0)
> 
>>From now on the Session is stuck and no reconnect is attempted. I have to
> kill the process and restart it again. It looks like shortly after a
> timeout is detected and the session was disconnected, a HeartBeat message
> is received from the other party and fails to validate (since the session
> is disconnected).
> 
> I am using QuickFixJ 1.6.1 with the following configuration settings:
> 
> [DEFAULT]
> ConnectionType=initiator
> ReconnectInterval=60
> SenderCompID=OMFDTSDEMO
> StartTime=06:15:00
> EndTime=05:50:00
> ValidateFieldsOutOfOrder=N
> ValidateUserDefinedFields=N
> 
> [SESSION]
> BeginString=FIX.4.2
> TargetCompID=TTDS68BO
> HeartBtInt=20
> DataDictionary=FIX42_tt.xml
> ResetOnLogon=Y
> DisconnectOnError=Y
> RejectMessageOnUnhandledException=N
> 
> # validation
> ValidateFieldsOutOfOrder=N
> ValidateFieldsHaveValues=N
> ValidateUserDefinedFields=N
> ValidateUnorderedGroupFields=N
> 
> Is there any way to get past this error and try to reconnect again? Any
> help is greatly appreciated.
> 
> Regards,
> Dan
> 
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
> _______________________________________________
> Quickfixj-users mailing list

> Quickfixj-users@.sourceforge

> https://lists.sourceforge.net/lists/listinfo/quickfixj-users





--
View this message in context: http://quickfix-j.364392.n2.nabble.com/Not-reconnecting-after-Timed-out-waiting-for-heartbeat-tp7579538p7579540.html
Sent from the QuickFIX/J mailing list archive at Nabble.com.