[
https://issues.apache.org/jira/browse/CAMEL-12887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16653777#comment-16653777
]
Luca Burgazzoli commented on CAMEL-12887:
-----------------------------------------
the fix cinematic is not governed by camel afaik but by the underlying engine,
can you check if the same behavior is observed by using a plain quickfixj app ?
A reproducer would also be very welcome
> In case of disconnect relogin is not working
> --------------------------------------------
>
> Key: CAMEL-12887
> URL: https://issues.apache.org/jira/browse/CAMEL-12887
> Project: Camel
> Issue Type: Bug
> Components: camel-quickfix
> Affects Versions: 2.14.1
> Environment: JAVA 8
> Ubuntu 16
> Reporter: bhavishya
> Priority: Major
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
