Quantcast

Not reconnecting after Timed out waiting for heartbeat

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Not reconnecting after Timed out waiting for heartbeat

Dan Corneanu
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Not reconnecting after Timed out waiting for heartbeat

thannon
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Not reconnecting after Timed out waiting for heartbeat

Dan Corneanu
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Hi Tommy,
I'll try that and see what happens.

In the meantime I had a closer look to the log file and to the source code and ended up with two question marks:
1. Isn't the session supposed to send a Test Request after a heartbeat timeout before actually disconnecting?
2. From the source code I can see that the timeout is computed as 2.4 * HeartBtInt which in my case would be 2.4 * 20 = 40.8 seconds. Looking at the logs I can confirm that the other party did send a HeartBeat every 20 secs so I do not understand how did my session decide it has timed-out?

Here is a slightly bigger chunk from my logfile:

2016-06-16 03:09:03.137  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377352=20160616-03:09:03.73910=063
2016-06-16 03:09:13.333  INFO 40764 --- [      QFJ Timer] quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=6435=034=376349=OMFDTSDEMO52=20160616-03:09:13.33356=TTDS68BO10=165
2016-06-16 03:09:23.137  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377452=20160616-03:09:23.73910=066
2016-06-16 03:09:33.332  INFO 40764 --- [      QFJ Timer] quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=6435=034=376449=OMFDTSDEMO52=20160616-03:09:33.33256=TTDS68BO10=167
2016-06-16 03:09:43.135  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377552=20160616-03:09:43.73910=069
2016-06-16 03:09:53.332  INFO 40764 --- [      QFJ Timer] quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=6435=034=376549=OMFDTSDEMO52=20160616-03:09:53.33256=TTDS68BO10=170
2016-06-16 03:10:03.135  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377652=20160616-03:10:03.73910=058
2016-06-16 03:10:13.332  INFO 40764 --- [      QFJ Timer] quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=6435=034=376649=OMFDTSDEMO52=20160616-03:10:13.33256=TTDS68BO10=159
2016-06-16 03:10:23.134  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377752=20160616-03:10:23.73910=061
2016-06-16 03:10:33.332  INFO 40764 --- [      QFJ Timer] quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=6435=034=376749=OMFDTSDEMO52=20160616-03:10:33.33256=TTDS68BO10=162
2016-06-16 03:11:41.449  INFO 40764 --- [ NioProcessor-2] quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO: 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377852=20160616-03:10:43.73910=064
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)

Any clues are 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://sdm.link/zohomanageengine
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Not reconnecting after Timed out waiting for heartbeat

thannon
Hi Dan,

I am wondering if maybe your application might be blocking in one of the callback methods.  This can cause the engine to react undesirably.

Dan Corneanu wrote
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/



Hi Tommy,
I'll try that and see what happens.

In the meantime I had a closer look to the log file and to the source code
and ended up with two question marks:
1. Isn't the session supposed to send a Test Request after a heartbeat
timeout before actually disconnecting?
2. From the source code I can see that the timeout is computed as 2.4 *
HeartBtInt which in my case would be 2.4 * 20 = 40.8 seconds. Looking at
the logs I can confirm that the other party did send a HeartBeat every 20
secs so I do not understand how did my session decide it has timed-out?

Here is a slightly bigger chunk from my logfile:

2016-06-16 03:09:03.137  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377352=20160616-03:09:03.73910=063
2016-06-16 03:09:13.333  INFO 40764 --- [      QFJ Timer]
quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=6435=034=376349=OMFDTSDEMO52=20160616-03:09:13.33356=TTDS68BO10=165
2016-06-16 03:09:23.137  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377452=20160616-03:09:23.73910=066
2016-06-16 03:09:33.332  INFO 40764 --- [      QFJ Timer]
quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=6435=034=376449=OMFDTSDEMO52=20160616-03:09:33.33256=TTDS68BO10=167
2016-06-16 03:09:43.135  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377552=20160616-03:09:43.73910=069
2016-06-16 03:09:53.332  INFO 40764 --- [      QFJ Timer]
quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=6435=034=376549=OMFDTSDEMO52=20160616-03:09:53.33256=TTDS68BO10=170
2016-06-16 03:10:03.135  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377652=20160616-03:10:03.73910=058
2016-06-16 03:10:13.332  INFO 40764 --- [      QFJ Timer]
quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=6435=034=376649=OMFDTSDEMO52=20160616-03:10:13.33256=TTDS68BO10=159
2016-06-16 03:10:23.134  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377752=20160616-03:10:23.73910=061
2016-06-16 03:10:33.332  INFO 40764 --- [      QFJ Timer]
quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=6435=034=376749=OMFDTSDEMO52=20160616-03:10:33.33256=TTDS68BO10=162
2016-06-16 03:11:41.449  INFO 40764 --- [ NioProcessor-2]
quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377852=20160616-03:10:43.73910=064
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)

Any clues are 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://sdm.link/zohomanageengine
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Not reconnecting after Timed out waiting for heartbeat

Christoph John
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/


Hi Dan,

a stack trace would be helpful.

Cheers

On 21/06/16 02:23, thannon wrote:

> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
>
>
> Hi Dan,
>
> I am wondering if maybe your application might be blocking in one of the
> callback methods.  This can cause the engine to react undesirably.
>
>
> Dan Corneanu wrote
>> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
>> QuickFIX/J Support: http://www.quickfixj.org/support/
>>
>>
>>
>> Hi Tommy,
>> I'll try that and see what happens.
>>
>> In the meantime I had a closer look to the log file and to the source code
>> and ended up with two question marks:
>> 1. Isn't the session supposed to send a Test Request after a heartbeat
>> timeout before actually disconnecting?
>> 2. From the source code I can see that the timeout is computed as 2.4 *
>> HeartBtInt which in my case would be 2.4 * 20 = 40.8 seconds. Looking at
>> the logs I can confirm that the other party did send a HeartBeat every 20
>> secs so I do not understand how did my session decide it has timed-out?
>>
>> Here is a slightly bigger chunk from my logfile:
>>
>> 2016-06-16 03:09:03.137  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377352=20160616-03:09:03.73910=063
>> 2016-06-16 03:09:13.333  INFO 40764 --- [      QFJ Timer]
>> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=6435=034=376349=OMFDTSDEMO52=20160616-03:09:13.33356=TTDS68BO10=165
>> 2016-06-16 03:09:23.137  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377452=20160616-03:09:23.73910=066
>> 2016-06-16 03:09:33.332  INFO 40764 --- [      QFJ Timer]
>> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=6435=034=376449=OMFDTSDEMO52=20160616-03:09:33.33256=TTDS68BO10=167
>> 2016-06-16 03:09:43.135  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377552=20160616-03:09:43.73910=069
>> 2016-06-16 03:09:53.332  INFO 40764 --- [      QFJ Timer]
>> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=6435=034=376549=OMFDTSDEMO52=20160616-03:09:53.33256=TTDS68BO10=170
>> 2016-06-16 03:10:03.135  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377652=20160616-03:10:03.73910=058
>> 2016-06-16 03:10:13.332  INFO 40764 --- [      QFJ Timer]
>> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=6435=034=376649=OMFDTSDEMO52=20160616-03:10:13.33256=TTDS68BO10=159
>> 2016-06-16 03:10:23.134  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377752=20160616-03:10:23.73910=061
>> 2016-06-16 03:10:33.332  INFO 40764 --- [      QFJ Timer]
>> quickfixj.msg.outgoing                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=6435=034=376749=OMFDTSDEMO52=20160616-03:10:33.33256=TTDS68BO10=162
>> 2016-06-16 03:11:41.449  INFO 40764 --- [ NioProcessor-2]
>> quickfixj.msg.incoming                   : FIX.4.2:OMFDTSDEMO->TTDS68BO:
>> 8=FIX.4.29=0006435=049=TTDS68BO56=OMFDTSDEMO34=377852=20160616-03:10:43.73910=064
>> 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)
>>
>> Any clues are 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://sdm.link/zohomanageengine
>> _______________________________________________
>> 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-tp7579538p7579548.html
> Sent from the QuickFIX/J mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> _______________________________________________
> Quickfixj-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users

--
Christoph John
Development & Support
Direct: +49 241 557080-28
Mailto:[hidden email]
       


http://www.macd.com <http://www.macd.com/>
----------------------------------------------------------------------------------------------------
       
----------------------------------------------------------------------------------------------------
MACD GmbH
Oppenhoffallee 103
D-52066 Aachen
Tel: +49 241 557080-0 | Fax: +49 241 557080-10
         Amtsgericht Aachen: HRB 8151
Ust.-Id: DE 813021663

Geschäftsführer: George Macdonald
----------------------------------------------------------------------------------------------------
       
----------------------------------------------------------------------------------------------------

take care of the environment - print only if necessary

------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Quickfixj-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
Loading...