[QFJ-957] In case of disconnect relogin is not working Created: 16/Oct/18  Updated: 17/Oct/18  Resolved: 17/Oct/18

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.5.3
Fix Version/s: None

Type: Bug Priority: Default
Reporter: Bhavishya Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

JAVA 8


 Description   

My application is sending logon request and getting logon response and session get logged in perfectly at first time . After some time session get disconnected due to heartbeat timeout and my application send login again and acceptor send login response within same second but my initiator don't get connected after 10 second it send another login request. Ideally it should not send login request again.

Event logs are

20181015-13:36:34: Sent test request TEST

20181015-13:37:01: Disconnecting: Timed out waiting for heartbeat

20181015-13:37:02: Initiated logon request

20181015-13:37:13: Disconnecting: Timed out waiting for logon response

20181015-13:37:32: Disconnecting: Socket exception (/192.168.40.29:31815): java.io.IOException: Connection reset by peer

20181015-13:38:02: Initiated logon request

Message logs

8=FIX.4.2^A9=69^A35=A^A34=1064^A49=test^A52=20181015-13:37:02.570^A56=test^A98=0^A108=30^A10=075^A
8=FIX.4.2^A9=000593^A35=A^A34=001527^A43=N^A52=20181015-13:37:02^A49=test^A56=test^A98=0^A108=30^A6247=prod^A6272=AMEX/OPT,CBOE/OPT,PHLX/OPT,PSE/OPT,DTB/OPT,ISE/OPT,BELFOX/OPT,GLOBEX/FOP,MONEP/OPT,SOFFEX/OPT,FTA/OPT,ASX/OPT,BOX/OPT,ECBOT/FOP,IBCX/BAG,BATS/OPT,NASDAQOM/OPT,ICEEU/OPT^A6382=S3^A6387=s3.amazonaws.com^A6386=0WWXP5X5ZAMQC93NZR82^A6492=1^A6541=1^A6530=1^A6550=1^A6560=1/Maximize Rebate,9/Prefer Rebate,11/Prefer Fill,12/Maximize Fill,2/Primary Exchange,3/Highest Volume Exchange With Rebate,4/High Volume Exchange With Lowest Fee^A6749=1/Maximize Rebate,9/Prefer Rebate,11/Prefer Fill,12/Maximize Fill^A8035=5bc41694.^A10=210^A
8=FIX.4.2^A9=69^A35=A^A34=1065^A49=test^A52=20181015-13:38:02.569^A56=test^A98=0^A108=30^A10=085^A
8=FIX.4.2^A9=000593^A35=A^A34=001528^A43=N^A52=20181015-13:38:02^A49=test^A56=test^A98=0^A108=30^A6247=prod^A6272=AMEX/OPT,CBOE/OPT,PHLX/OPT,PSE/OPT,DTB/OPT,ISE/OPT,BELFOX/OPT,GLOBEX/FOP,MONEP/OPT,SOFFEX/OPT,FTA/OPT,ASX/OPT,BOX/OPT,ECBOT/FOP,IBCX/BAG,BATS/OPT,NASDAQOM/OPT,ICEEU/OPT^A6382=S3^A6387=s3.amazonaws.com^A6386=0WWXP5X5ZAMQC93NZR82^A6492=1^A6541=1^A6530=1^A6550=1^A6560=1/Maximize Rebate,9/Prefer Rebate,11/Prefer Fill,12/Maximize Fill,2/Primary Exchange,3/Highest Volume Exchange With Rebate,4/High Volume Exchange With Lowest Fee^A6749=1/Maximize Rebate,9/Prefer Rebate,11/Prefer Fill,12/Maximize Fill^A8035=5bc41694.^A10=212^A

As you can see we send login request at 20181015-13:37:02.570 and get response at 20181015-13:37:02 then still it send one more login request.
Any help would be really appreciated

I have removed actual SendercompId and Target comp Id

I am using camel 2.14.1 and quickfixh 1.5.3. I have raised in mailing list but no reply and this is production issue so please pardon me.

 Comments   
Comment by Christoph John [ 17/Oct/18 ]

Well, asking on the mailing list is the preferred way. And it took slightly more than one hour for a reply on the mailing list.
For commercial support you could always contact one of the companies listed here: https://www.quickfixj.org/support/

One advice though: your QFJ version is rather old. Try updating first.
If you have any more questions please ask on the mailing list.

Thanks,
Chris.

Comment by Bhavishya [ 17/Oct/18 ]

I have tried upgrading on 2.0.0 but still facing same issue

Comment by Bhavishya [ 17/Oct/18 ]

It's has been more than one day but still no reply

Comment by Christoph John [ 17/Oct/18 ]

Two things:

  • your mail client does not seem to work correctly. There were replies. You can also check here: https://sourceforge.net/p/quickfixj/mailman/quickfixj-users/
  • this is an open source project so reply times may vary. If commercial support and low response times are needed you have the options listed in my first comment.
Generated at Wed May 08 23:13:00 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.