Menu
▾
▴
quickfixj-users — General mailing list for QuickFIX/J topics.
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(13) |
Jun
(21) |
Jul
(14) |
Aug
(29) |
Sep
(39) |
Oct
(47) |
Nov
(70) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(43) |
Feb
(50) |
Mar
(90) |
Apr
(96) |
May
(84) |
Jun
(40) |
Jul
(58) |
Aug
(55) |
Sep
(55) |
Oct
(52) |
Nov
(38) |
Dec
(75) |
| 2008 |
Jan
(49) |
Feb
(72) |
Mar
(49) |
Apr
(55) |
May
(21) |
Jun
(31) |
Jul
(47) |
Aug
(59) |
Sep
(59) |
Oct
(77) |
Nov
(51) |
Dec
(54) |
| 2009 |
Jan
(52) |
Feb
(57) |
Mar
(17) |
Apr
(27) |
May
(44) |
Jun
(46) |
Jul
(69) |
Aug
(38) |
Sep
(39) |
Oct
(45) |
Nov
(38) |
Dec
(37) |
| 2010 |
Jan
(49) |
Feb
(35) |
Mar
(21) |
Apr
(33) |
May
(52) |
Jun
(28) |
Jul
(39) |
Aug
(34) |
Sep
(21) |
Oct
(82) |
Nov
(36) |
Dec
(20) |
| 2011 |
Jan
(28) |
Feb
(64) |
Mar
(93) |
Apr
(75) |
May
(151) |
Jun
(77) |
Jul
(35) |
Aug
(53) |
Sep
(56) |
Oct
(36) |
Nov
(94) |
Dec
(59) |
| 2012 |
Jan
(105) |
Feb
(43) |
Mar
(68) |
Apr
(91) |
May
(45) |
Jun
(18) |
Jul
(103) |
Aug
(77) |
Sep
(45) |
Oct
(59) |
Nov
(58) |
Dec
(43) |
| 2013 |
Jan
(48) |
Feb
(65) |
Mar
(63) |
Apr
(22) |
May
(41) |
Jun
(60) |
Jul
(43) |
Aug
(17) |
Sep
(20) |
Oct
(20) |
Nov
(42) |
Dec
(43) |
| 2014 |
Jan
(54) |
Feb
(34) |
Mar
(34) |
Apr
(20) |
May
(31) |
Jun
(39) |
Jul
(66) |
Aug
(22) |
Sep
(52) |
Oct
(22) |
Nov
(67) |
Dec
(70) |
| 2015 |
Jan
(18) |
Feb
(5) |
Mar
(40) |
Apr
(32) |
May
(62) |
Jun
(28) |
Jul
(86) |
Aug
(44) |
Sep
(61) |
Oct
(65) |
Nov
(8) |
Dec
(19) |
| 2016 |
Jan
(50) |
Feb
(22) |
Mar
(38) |
Apr
(55) |
May
(30) |
Jun
(42) |
Jul
(11) |
Aug
(9) |
Sep
(4) |
Oct
(51) |
Nov
(38) |
Dec
(31) |
| 2017 |
Jan
(40) |
Feb
(40) |
Mar
(23) |
Apr
(35) |
May
(121) |
Jun
(55) |
Jul
(37) |
Aug
(16) |
Sep
(27) |
Oct
(109) |
Nov
(67) |
Dec
(23) |
| 2018 |
Jan
(52) |
Feb
(6) |
Mar
(23) |
Apr
(28) |
May
(32) |
Jun
(20) |
Jul
(20) |
Aug
(22) |
Sep
(8) |
Oct
(33) |
Nov
(32) |
Dec
(13) |
| 2019 |
Jan
(16) |
Feb
(29) |
Mar
(17) |
Apr
(16) |
May
(1) |
Jun
(2) |
Jul
(25) |
Aug
(50) |
Sep
(17) |
Oct
(29) |
Nov
(16) |
Dec
(7) |
| 2020 |
Jan
|
Feb
|
Mar
(29) |
Apr
(64) |
May
(25) |
Jun
(49) |
Jul
(15) |
Aug
(10) |
Sep
(37) |
Oct
(20) |
Nov
(19) |
Dec
(9) |
| 2021 |
Jan
(33) |
Feb
(10) |
Mar
(67) |
Apr
(40) |
May
(70) |
Jun
(33) |
Jul
(14) |
Aug
(10) |
Sep
|
Oct
(7) |
Nov
(6) |
Dec
(16) |
| 2022 |
Jan
(27) |
Feb
(2) |
Mar
(5) |
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(6) |
Oct
(2) |
Nov
|
Dec
(10) |
| 2023 |
Jan
(1) |
Feb
(2) |
Mar
(21) |
Apr
(3) |
May
(15) |
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(1) |
| 2024 |
Jan
(7) |
Feb
(2) |
Mar
(8) |
Apr
(11) |
May
(6) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2025 |
Jan
(10) |
Feb
(4) |
Mar
(9) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: AJIT G. <aji...@gm...> - 2023-03-27 13:40:40
|
Hi, I would like to highlight one scenario and any solution for the same will be appreciated. I received huge multiple number of resend request on my Quickfix Java application and in this way my log messages were full. Is there any way I can control or set the throttling for admin messages in Quickfix Java. Regards Ajit |
|
From: Christoph J. <chr...@ma...> - 2023-03-18 11:43:37
|
I thought about it some more and don't think a Slack Channel is a good idea for the following reasons: 1. It is closed so cannot be accessed by anonymous users. 2. It cannot be searched by Google or similar. At least as far that I know. 3. A message archive of only 90 days is somewhat low, given that Stackoverflow, mailing list or github discussions are there forever. 4. Users might expect synchronous communication, I.e. that someone will immediately there to help them which will probably not be the case. I think slack is better for communicating inside an organisation where people will be online during regular hours. Best regards Chris 17 Mar 2023 23:34:27 Hasnain Khan <kha...@gm...>: > A lot of the slack channels are not used much tbh. Particularly for more advanced frameworks since such communities are smaller anyway. I would be interested in a slack channel. > Warm regards, > * > **Hasnain Khan* > Bachelor's of Science in Computer Science and Minor in Accountancy, > DePaul University Class of 2016 > http://linkedin.com/in/hasnain-k-538b01a2 > > > > > On Mon, Mar 13, 2023 at 12:26 PM Christoph John via Quickfixj-users <qui...@li...> wrote: >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> There was a Slack channel but I am not sure if it is for general use. I will check. >> >> I shortly thought about using Zulip but actually I am not sure if I'd like to have yet another >> channel where messages come in. But it probably would be good for users to chat about problems. But >> can't tell if many will use it given that on other places (github discussions or this mailing list) >> there is not much going on. ;) >> >> Cheers >> Chris >> >> >> >> On 12.03.23 08:35, Hasnain Khan wrote: >>> QFJ Documentation: http://www.quickfixj.org/documentation/ >>> QFJ Support: http://www.quickfixj.org/support/ >>> >>> >>> Is there a slack channel for quickfix? >>> >>> >>> _______________________________________________ >>> Quickfixj-users mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> >> -- >> Christoph John >> Software Engineering >> T +49 241 557080-28 >> chr...@ma... >> >> MACD GmbH >> Oppenhoffallee 103 >> 52066 Aachen, Germany >> www.macd.com[http://www.macd.com] >> >> Amtsgericht Aachen: HRB 8151 >> Ust.-Id: DE 813021663 >> Geschäftsführer: George Macdonald >> >> >> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users |
|
From: Hasnain K. <kha...@gm...> - 2023-03-17 22:34:27
|
A lot of the slack channels are not used much tbh. Particularly for more advanced frameworks since such communities are smaller anyway. I would be interested in a slack channel. Warm regards, *Hasnain Khan* Bachelor's of Science in Computer Science and Minor in Accountancy, DePaul University Class of 2016 http://linkedin.com/in/hasnain-k-538b01a2 On Mon, Mar 13, 2023 at 12:26 PM Christoph John via Quickfixj-users < qui...@li...> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > There was a Slack channel but I am not sure if it is for general use. I > will check. > > I shortly thought about using Zulip but actually I am not sure if I'd like > to have yet another > channel where messages come in. But it probably would be good for users to > chat about problems. But > can't tell if many will use it given that on other places (github > discussions or this mailing list) > there is not much going on. ;) > > Cheers > Chris > > > > On 12.03.23 08:35, Hasnain Khan wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > > QFJ Support: http://www.quickfixj.org/support/ > > > > > > Is there a slack channel for quickfix? > > > > > > _______________________________________________ > > Quickfixj-users mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > -- > Christoph John > Software Engineering > T +49 241 557080-28 > chr...@ma... > > MACD GmbH > Oppenhoffallee 103 > 52066 Aachen, Germany > www.macd.com > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE 813021663 > Geschäftsführer: George Macdonald > > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Christoph J. <chr...@ma...> - 2023-03-17 17:27:13
|
Hi Zhu, that link is not for QuickFIX C but for a FIX engine from another vendor AFAICT. If you'd like you could get the 2.3.x branch from here https://github.com/quickfix-j/quickfixj/tree/QFJ_2_3_x, incorporate your changes and build and test. Build instructions are here: https://github.com/quickfix-j/quickfixj/tree/QFJ_2_3_x#build-instructions If you need help, just ask. Cheers Chris On 17.03.23 16:23, Zhu Tan wrote: > Hello Chris, > > I did try the option of endRedundantResendRequests=Y and it does not work. I am wondering whether > someone has passed the test somehow without forking the repo too. > > As for the other requirements of CME DC. one more CME-specific requirement is to provide > CME-1-SHA-256 hash on logon message, which can be done via > overriddig ApplicationAdaptor.toAdmin(). I am able to pass all other CME tests. > > I see the quickfx c version has a specific setup for CME > (https://ref.onixs.biz/net-core-fix-engine-guide/articles/cme-specific-settings.html. ) > > how big is the effort to fix this in quickfixj? I can certainly help with testing. > > Thanks, > Zhu > > > > On Fri, 17 Mar 2023 at 15:03, Christoph John via Quickfixj-users > <qui...@li...> wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hi, > > as you can see in the JIRA issue I did not pursue this further due to the lack of messages > logs and eventually time. Up to now no-one requested this change and it has been almost seven > years. So I am asking myself if people in the meantime somehow got the test to pass. > On one comment in the issue I mention the config parameter SendRedundantResendRequests=Y . Did > you try that out? But probably it is not going to help since already the first resend request > fails for you. > > I did look at that CME website and it seems there is more than just that check in the Session > class. There are some more rules that need to be followed so I don't know if fixing that one > line will help. > > Best regards > Chris > > > > > On 17.03.23 14:58, Zhu Tan wrote: >> QFJ Documentation:http://www.quickfixj.org/documentation/ >> QFJ Support:http://www.quickfixj.org/support/ >> >> >> >> Hello, >> >> I am using quickfixj 2.1.1 to connect to CME DropCopy 4.0. CME DC requires all Resend >> Requests not to request more than the maximum limit of 2500 messages (see >> https://www.cmegroup.com/confluence/display/EPICSANDBOX/Drop+Copy+Session+Layer+-+Resend+Request). >> Therefore. I set >> >> ResendRequestChunkSize=2000, however, I am having issue to pass the automated failover >> certification test due to the test expect multiple resend request messages to recover all >> missed messages. I.e. seems QFJ failed to send the resend request for the first chunk only as >> the fix messages below: >> >> 2023-03-17 06:06:13.510 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=225|35=A|34=48|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.437|56=CME|57=G|142=GB|98=0|108=30|354=20|355=zXQ7fgakpLQ9ng5x4HZ0|1400=CME-1-SHA-256|1401=43|1402=R8yifHbBZbJGiKua50B5o-pwlcrbe71fbk3N6Tw6VNk|1603=COM_RISK|1604=1.0|1605=COM|10=111| >> >> 2023-03-17 06:06:13.662 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - >> 8=FIX.4.2|9=126|35=A|34=8042|369=48|52=20230317-06:06:13.606|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|98=0|108=30|1603=COM_RISK|1604=1.0|1605=COM|10=109| >> >> 2023-03-17 06:06:13.670 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - >> 8=FIX.4.2|9=97|35=1|34=8043|369=48|52=20230317-06:06:13.607|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zty|10=159| >> >> 2023-03-17 06:06:13.676 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] >> quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=2|34=49|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.675|56=CME|57=G|142=GB|7=4042|16=6041|10=055| >> >> 2023-03-17 06:06:18.800 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - >> 8=FIX.4.2|9=127|35=4|34=4042|369=49|52=20230317-06:06:18.758|43=Y|49=CME|50=G|56=OAEAAAN|57=9Q5|122=20230317-06:06:18.758|143=GB|36=8044|123=Y|10=021| >> >> 2023-03-17 06:06:44.432 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=73|35=0|34=50|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.431|56=CME|57=G|142=GB|10=114| >> >> 2023-03-17 06:06:44.730 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - >> 8=FIX.4.2|9=97|35=1|34=8044|369=49|52=20230317-06:06:44.688|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3ztz|10=175| >> >> 2023-03-17 06:06:44.734 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] >> quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=0|34=51|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.734|56=CME|57=G|142=GB|112=IDlf5n3ztz|10=238| >> >> 2023-03-17 06:07:15.428 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=73|35=0|34=52|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.427|56=CME|57=G|142=GB|10=120| >> >> 2023-03-17 06:07:15.732 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - >> 8=FIX.4.2|9=97|35=1|34=8045|369=51|52=20230317-06:07:15.691|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zu0|10=089| >> >> 2023-03-17 06:07:15.736 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] >> quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=0|34=53|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.735|56=CME|57=G|142=GB|112=IDlf5n3zu0|10=167| >> >> Also found this old thread >> (https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280 >> <https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280> ) >> that identified the issue was due to the check, newSequence < range.getEndSeqNo() >> >> At >> https://github.com/quickfix-j/quickfixj/blob/0ef2ac42ac9966a965b9e811713b9b8c6bc7c32c/quickfixj-core/src/main/java/quickfix/Session.java#L1549 >> >> Which makes sense to me. >> >> /upon receiving SequenceReset messages QuickFIX/J will determine if a new ResendRequest chunk >> message needs to get sent out based on the following criteria in the nextSequenceReset method >> of the Session class by checking if newSequence < range.getEndSeqNo(). Since this fails, some >> ResendRequests fail to ever get sent out./ >> >> A solution has been proposed in the thread too. Not sure what has been fixed following the >> thread. But the code in Session.java has the newSequence < range.getEndSeqNo() check in >> github currently. >> >> Have anyone successfully certified with CME DC 4.0 with quickfixj. Any help would be very >> appreciated. >> >> Best, >> >> Zhu >> >> >> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > -- > Christoph John > Software Engineering > T +49 241 557080-28 > chr...@ma... > > MACD GmbH > Oppenhoffallee 103 > 52066 Aachen, Germany > www.macd.com <http://www.macd.com> > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE 813021663 > Geschäftsführer: George Macdonald > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |
|
From: Zhu T. <zh...@gm...> - 2023-03-17 15:28:35
|
maybe just provide a option to remove the newSequence < range.getEndSeqNo() checking? I can test it out. I am new to quickfixj codebase, hence not sure the impact of removing that check. On Fri, 17 Mar 2023 at 15:23, Zhu Tan <zh...@gm...> wrote: > Hello Chris, > > I did try the option of endRedundantResendRequests=Y and it does not work. > I am wondering whether someone has passed the test somehow without forking > the repo too. > > As for the other requirements of CME DC. one more CME-specific requirement > is to provide CME-1-SHA-256 hash on logon message, which can be done via > overriddig ApplicationAdaptor.toAdmin(). I am able to pass all other CME > tests. > > I see the quickfx c version has a specific setup for CME ( > https://ref.onixs.biz/net-core-fix-engine-guide/articles/cme-specific-settings.html. > ) > > how big is the effort to fix this in quickfixj? I can certainly help with > testing. > > Thanks, > Zhu > > > > On Fri, 17 Mar 2023 at 15:03, Christoph John via Quickfixj-users < > qui...@li...> wrote: > >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> Hi, >> >> as you can see in the JIRA issue I did not pursue this further due to the >> lack of messages logs and eventually time. Up to now no-one requested this >> change and it has been almost seven years. So I am asking myself if people >> in the meantime somehow got the test to pass. >> On one comment in the issue I mention the config parameter >> SendRedundantResendRequests=Y . Did you try that out? But probably it is >> not going to help since already the first resend request fails for you. >> >> I did look at that CME website and it seems there is more than just that >> check in the Session class. There are some more rules that need to be >> followed so I don't know if fixing that one line will help. >> >> Best regards >> Chris >> >> >> >> >> On 17.03.23 14:58, Zhu Tan wrote: >> >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> Hello, >> >> >> >> I am using quickfixj 2.1.1 to connect to CME DropCopy 4.0. CME DC >> requires all Resend Requests not to request more than the maximum limit of >> 2500 messages (see >> https://www.cmegroup.com/confluence/display/EPICSANDBOX/Drop+Copy+Session+Layer+-+Resend+Request). >> Therefore. I set >> >> ResendRequestChunkSize=2000, however, I am having issue to pass the >> automated failover certification test due to the test expect multiple >> resend request messages to recover all missed messages. I.e. seems QFJ >> failed to send the resend request for the first chunk only as the fix >> messages below: >> >> >> >> 2023-03-17 06:06:13.510 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=225|35=A|34=48|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.437|56=CME|57=G|142=GB|98=0|108=30|354=20|355=zXQ7fgakpLQ9ng5x4HZ0|1400=CME-1-SHA-256|1401=43|1402=R8yifHbBZbJGiKua50B5o-pwlcrbe71fbk3N6Tw6VNk|1603=COM_RISK|1604=1.0|1605=COM|10=111| >> >> 2023-03-17 06:06:13.662 [INFO ] [NioProcessor-2] quickfixj.msg.incoming >> - >> 8=FIX.4.2|9=126|35=A|34=8042|369=48|52=20230317-06:06:13.606|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|98=0|108=30|1603=COM_RISK|1604=1.0|1605=COM|10=109| >> >> 2023-03-17 06:06:13.670 [INFO ] [NioProcessor-2] quickfixj.msg.incoming >> - >> 8=FIX.4.2|9=97|35=1|34=8043|369=48|52=20230317-06:06:13.607|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zty|10=159| >> >> 2023-03-17 06:06:13.676 [INFO ] [QF/J Session dispatcher: >> FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=2 >> |34=49|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.675|56=CME|57=G|142=GB|7=4042|16=6041|10=055| >> >> 2023-03-17 06:06:18.800 [INFO ] [NioProcessor-2] quickfixj.msg.incoming >> - >> 8=FIX.4.2|9=127|35=4|34=4042|369=49|52=20230317-06:06:18.758|43=Y|49=CME|50=G|56=OAEAAAN|57=9Q5|122=20230317-06:06:18.758|143=GB|36=8044|123=Y|10=021| >> >> 2023-03-17 06:06:44.432 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=73|35=0|34=50|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.431|56=CME|57=G|142=GB|10=114| >> >> 2023-03-17 06:06:44.730 [INFO ] [NioProcessor-2] quickfixj.msg.incoming >> - >> 8=FIX.4.2|9=97|35=1|34=8044|369=49|52=20230317-06:06:44.688|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3ztz|10=175| >> >> 2023-03-17 06:06:44.734 [INFO ] [QF/J Session dispatcher: >> FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=0|34=51|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.734|56=CME|57=G|142=GB|112=IDlf5n3ztz|10=238| >> >> 2023-03-17 06:07:15.428 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=73|35=0|34=52|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.427|56=CME|57=G|142=GB|10=120| >> >> 2023-03-17 06:07:15.732 [INFO ] [NioProcessor-2] quickfixj.msg.incoming >> - >> 8=FIX.4.2|9=97|35=1|34=8045|369=51|52=20230317-06:07:15.691|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zu0|10=089| >> >> 2023-03-17 06:07:15.736 [INFO ] [QF/J Session dispatcher: >> FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - >> 8=FIX.4.2|9=88|35=0|34=53|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.735|56=CME|57=G|142=GB|112=IDlf5n3zu0|10=167| >> >> >> >> Also found this old thread ( >> https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280 ) >> that identified the issue was due to the check, newSequence < >> range.getEndSeqNo() >> >> At >> https://github.com/quickfix-j/quickfixj/blob/0ef2ac42ac9966a965b9e811713b9b8c6bc7c32c/quickfixj-core/src/main/java/quickfix/Session.java#L1549 >> >> Which makes sense to me. >> >> *upon receiving SequenceReset messages QuickFIX/J will determine if a new >> ResendRequest chunk message needs to get sent out based on the following >> criteria in the nextSequenceReset method of the Session class by checking >> if newSequence < range.getEndSeqNo(). Since this fails, some ResendRequests >> fail to ever get sent out.* >> >> A solution has been proposed in the thread too. Not sure what has been >> fixed following the thread. But the code in Session.java has the >> newSequence < range.getEndSeqNo() check in github currently. >> >> >> >> Have anyone successfully certified with CME DC 4.0 with quickfixj. Any >> help would be very appreciated. >> >> >> >> Best, >> >> Zhu >> >> >> >> >> _______________________________________________ >> Quickfixj-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> >> >> -- >> Christoph John >> Software Engineering >> T +49 241 557...@ma... >> >> MACD GmbH >> Oppenhoffallee 103 >> 52066 Aachen, Germanywww.macd.com >> >> Amtsgericht Aachen: HRB 8151 >> Ust.-Id: DE 813021663 >> Geschäftsführer: George Macdonald >> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> > |
|
From: Zhu T. <zh...@gm...> - 2023-03-17 15:23:49
|
Hello Chris, I did try the option of endRedundantResendRequests=Y and it does not work. I am wondering whether someone has passed the test somehow without forking the repo too. As for the other requirements of CME DC. one more CME-specific requirement is to provide CME-1-SHA-256 hash on logon message, which can be done via overriddig ApplicationAdaptor.toAdmin(). I am able to pass all other CME tests. I see the quickfx c version has a specific setup for CME ( https://ref.onixs.biz/net-core-fix-engine-guide/articles/cme-specific-settings.html. ) how big is the effort to fix this in quickfixj? I can certainly help with testing. Thanks, Zhu On Fri, 17 Mar 2023 at 15:03, Christoph John via Quickfixj-users < qui...@li...> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hi, > > as you can see in the JIRA issue I did not pursue this further due to the > lack of messages logs and eventually time. Up to now no-one requested this > change and it has been almost seven years. So I am asking myself if people > in the meantime somehow got the test to pass. > On one comment in the issue I mention the config parameter > SendRedundantResendRequests=Y . Did you try that out? But probably it is > not going to help since already the first resend request fails for you. > > I did look at that CME website and it seems there is more than just that > check in the Session class. There are some more rules that need to be > followed so I don't know if fixing that one line will help. > > Best regards > Chris > > > > > On 17.03.23 14:58, Zhu Tan wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hello, > > > > I am using quickfixj 2.1.1 to connect to CME DropCopy 4.0. CME DC requires > all Resend Requests not to request more than the maximum limit of 2500 > messages (see > https://www.cmegroup.com/confluence/display/EPICSANDBOX/Drop+Copy+Session+Layer+-+Resend+Request). > Therefore. I set > > ResendRequestChunkSize=2000, however, I am having issue to pass the > automated failover certification test due to the test expect multiple > resend request messages to recover all missed messages. I.e. seems QFJ > failed to send the resend request for the first chunk only as the fix > messages below: > > > > 2023-03-17 06:06:13.510 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=225|35=A|34=48|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.437|56=CME|57=G|142=GB|98=0|108=30|354=20|355=zXQ7fgakpLQ9ng5x4HZ0|1400=CME-1-SHA-256|1401=43|1402=R8yifHbBZbJGiKua50B5o-pwlcrbe71fbk3N6Tw6VNk|1603=COM_RISK|1604=1.0|1605=COM|10=111| > > 2023-03-17 06:06:13.662 [INFO ] [NioProcessor-2] quickfixj.msg.incoming > - > 8=FIX.4.2|9=126|35=A|34=8042|369=48|52=20230317-06:06:13.606|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|98=0|108=30|1603=COM_RISK|1604=1.0|1605=COM|10=109| > > 2023-03-17 06:06:13.670 [INFO ] [NioProcessor-2] quickfixj.msg.incoming > - > 8=FIX.4.2|9=97|35=1|34=8043|369=48|52=20230317-06:06:13.607|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zty|10=159| > > 2023-03-17 06:06:13.676 [INFO ] [QF/J Session dispatcher: > FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=2 > |34=49|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.675|56=CME|57=G|142=GB|7=4042|16=6041|10=055| > > 2023-03-17 06:06:18.800 [INFO ] [NioProcessor-2] quickfixj.msg.incoming > - > 8=FIX.4.2|9=127|35=4|34=4042|369=49|52=20230317-06:06:18.758|43=Y|49=CME|50=G|56=OAEAAAN|57=9Q5|122=20230317-06:06:18.758|143=GB|36=8044|123=Y|10=021| > > 2023-03-17 06:06:44.432 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=73|35=0|34=50|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.431|56=CME|57=G|142=GB|10=114| > > 2023-03-17 06:06:44.730 [INFO ] [NioProcessor-2] quickfixj.msg.incoming > - > 8=FIX.4.2|9=97|35=1|34=8044|369=49|52=20230317-06:06:44.688|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3ztz|10=175| > > 2023-03-17 06:06:44.734 [INFO ] [QF/J Session dispatcher: > FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=0|34=51|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.734|56=CME|57=G|142=GB|112=IDlf5n3ztz|10=238| > > 2023-03-17 06:07:15.428 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=73|35=0|34=52|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.427|56=CME|57=G|142=GB|10=120| > > 2023-03-17 06:07:15.732 [INFO ] [NioProcessor-2] quickfixj.msg.incoming > - > 8=FIX.4.2|9=97|35=1|34=8045|369=51|52=20230317-06:07:15.691|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zu0|10=089| > > 2023-03-17 06:07:15.736 [INFO ] [QF/J Session dispatcher: > FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=0|34=53|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.735|56=CME|57=G|142=GB|112=IDlf5n3zu0|10=167| > > > > Also found this old thread ( > https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280 ) > that identified the issue was due to the check, newSequence < > range.getEndSeqNo() > > At > https://github.com/quickfix-j/quickfixj/blob/0ef2ac42ac9966a965b9e811713b9b8c6bc7c32c/quickfixj-core/src/main/java/quickfix/Session.java#L1549 > > Which makes sense to me. > > *upon receiving SequenceReset messages QuickFIX/J will determine if a new > ResendRequest chunk message needs to get sent out based on the following > criteria in the nextSequenceReset method of the Session class by checking > if newSequence < range.getEndSeqNo(). Since this fails, some ResendRequests > fail to ever get sent out.* > > A solution has been proposed in the thread too. Not sure what has been > fixed following the thread. But the code in Session.java has the > newSequence < range.getEndSeqNo() check in github currently. > > > > Have anyone successfully certified with CME DC 4.0 with quickfixj. Any > help would be very appreciated. > > > > Best, > > Zhu > > > > > _______________________________________________ > Quickfixj-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > > -- > Christoph John > Software Engineering > T +49 241 557...@ma... > > MACD GmbH > Oppenhoffallee 103 > 52066 Aachen, Germanywww.macd.com > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE 813021663 > Geschäftsführer: George Macdonald > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Christoph J. <chr...@ma...> - 2023-03-17 15:01:07
|
Hi, as you can see in the JIRA issue I did not pursue this further due to the lack of messages logs and eventually time. Up to now no-one requested this change and it has been almost seven years. So I am asking myself if people in the meantime somehow got the test to pass. On one comment in the issue I mention the config parameter SendRedundantResendRequests=Y . Did you try that out? But probably it is not going to help since already the first resend request fails for you. I did look at that CME website and it seems there is more than just that check in the Session class. There are some more rules that need to be followed so I don't know if fixing that one line will help. Best regards Chris On 17.03.23 14:58, Zhu Tan wrote: > QFJ Documentation:http://www.quickfixj.org/documentation/ > QFJ Support:http://www.quickfixj.org/support/ > > > > Hello, > > I am using quickfixj 2.1.1 to connect to CME DropCopy 4.0. CME DC requires all Resend Requests not > to request more than the maximum limit of 2500 messages (see > https://www.cmegroup.com/confluence/display/EPICSANDBOX/Drop+Copy+Session+Layer+-+Resend+Request). > Therefore. I set > > ResendRequestChunkSize=2000, however, I am having issue to pass the automated failover > certification test due to the test expect multiple resend request messages to recover all missed > messages. I.e. seems QFJ failed to send the resend request for the first chunk only as the fix > messages below: > > 2023-03-17 06:06:13.510 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=225|35=A|34=48|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.437|56=CME|57=G|142=GB|98=0|108=30|354=20|355=zXQ7fgakpLQ9ng5x4HZ0|1400=CME-1-SHA-256|1401=43|1402=R8yifHbBZbJGiKua50B5o-pwlcrbe71fbk3N6Tw6VNk|1603=COM_RISK|1604=1.0|1605=COM|10=111| > > 2023-03-17 06:06:13.662 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - > 8=FIX.4.2|9=126|35=A|34=8042|369=48|52=20230317-06:06:13.606|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|98=0|108=30|1603=COM_RISK|1604=1.0|1605=COM|10=109| > > 2023-03-17 06:06:13.670 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - > 8=FIX.4.2|9=97|35=1|34=8043|369=48|52=20230317-06:06:13.607|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zty|10=159| > > 2023-03-17 06:06:13.676 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] > quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=2|34=49|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.675|56=CME|57=G|142=GB|7=4042|16=6041|10=055| > > 2023-03-17 06:06:18.800 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - > 8=FIX.4.2|9=127|35=4|34=4042|369=49|52=20230317-06:06:18.758|43=Y|49=CME|50=G|56=OAEAAAN|57=9Q5|122=20230317-06:06:18.758|143=GB|36=8044|123=Y|10=021| > > 2023-03-17 06:06:44.432 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=73|35=0|34=50|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.431|56=CME|57=G|142=GB|10=114| > > 2023-03-17 06:06:44.730 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - > 8=FIX.4.2|9=97|35=1|34=8044|369=49|52=20230317-06:06:44.688|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3ztz|10=175| > > 2023-03-17 06:06:44.734 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] > quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=0|34=51|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.734|56=CME|57=G|142=GB|112=IDlf5n3ztz|10=238| > > 2023-03-17 06:07:15.428 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - > 8=FIX.4.2|9=73|35=0|34=52|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.427|56=CME|57=G|142=GB|10=120| > > 2023-03-17 06:07:15.732 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - > 8=FIX.4.2|9=97|35=1|34=8045|369=51|52=20230317-06:07:15.691|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zu0|10=089| > > 2023-03-17 06:07:15.736 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] > quickfixj.msg.outgoing - > 8=FIX.4.2|9=88|35=0|34=53|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.735|56=CME|57=G|142=GB|112=IDlf5n3zu0|10=167| > > Also found this old thread > (https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280 > <https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280> ) > that identified the issue was due to the check, newSequence < range.getEndSeqNo() > > At > https://github.com/quickfix-j/quickfixj/blob/0ef2ac42ac9966a965b9e811713b9b8c6bc7c32c/quickfixj-core/src/main/java/quickfix/Session.java#L1549 > > Which makes sense to me. > > /upon receiving SequenceReset messages QuickFIX/J will determine if a new ResendRequest chunk > message needs to get sent out based on the following criteria in the nextSequenceReset method of > the Session class by checking if newSequence < range.getEndSeqNo(). Since this fails, some > ResendRequests fail to ever get sent out./ > > A solution has been proposed in the thread too. Not sure what has been fixed following the thread. > But the code in Session.java has the newSequence < range.getEndSeqNo() check in github currently. > > Have anyone successfully certified with CME DC 4.0 with quickfixj. Any help would be very appreciated. > > Best, > > Zhu > > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |
|
From: Zhu T. <zh...@gm...> - 2023-03-17 13:59:12
|
Hello, I am using quickfixj 2.1.1 to connect to CME DropCopy 4.0. CME DC requires all Resend Requests not to request more than the maximum limit of 2500 messages (see https://www.cmegroup.com/confluence/display/EPICSANDBOX/Drop+Copy+Session+Layer+-+Resend+Request). Therefore. I set ResendRequestChunkSize=2000, however, I am having issue to pass the automated failover certification test due to the test expect multiple resend request messages to recover all missed messages. I.e. seems QFJ failed to send the resend request for the first chunk only as the fix messages below: 2023-03-17 06:06:13.510 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - 8=FIX.4.2|9=225|35=A|34=48|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.437|56=CME|57=G|142=GB|98=0|108=30|354=20|355=zXQ7fgakpLQ9ng5x4HZ0|1400=CME-1-SHA-256|1401=43|1402=R8yifHbBZbJGiKua50B5o-pwlcrbe71fbk3N6Tw6VNk|1603=COM_RISK|1604=1.0|1605=COM|10=111| 2023-03-17 06:06:13.662 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - 8=FIX.4.2|9=126|35=A|34=8042|369=48|52=20230317-06:06:13.606|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|98=0|108=30|1603=COM_RISK|1604=1.0|1605=COM|10=109| 2023-03-17 06:06:13.670 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - 8=FIX.4.2|9=97|35=1|34=8043|369=48|52=20230317-06:06:13.607|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zty|10=159| 2023-03-17 06:06:13.676 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - 8=FIX.4.2|9=88|35=2 |34=49|49=OAEAAAN|50=9Q5|52=20230317-06:06:13.675|56=CME|57=G|142=GB|7=4042|16=6041|10=055| 2023-03-17 06:06:18.800 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - 8=FIX.4.2|9=127|35=4|34=4042|369=49|52=20230317-06:06:18.758|43=Y|49=CME|50=G|56=OAEAAAN|57=9Q5|122=20230317-06:06:18.758|143=GB|36=8044|123=Y|10=021| 2023-03-17 06:06:44.432 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - 8=FIX.4.2|9=73|35=0|34=50|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.431|56=CME|57=G|142=GB|10=114| 2023-03-17 06:06:44.730 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - 8=FIX.4.2|9=97|35=1|34=8044|369=49|52=20230317-06:06:44.688|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3ztz|10=175| 2023-03-17 06:06:44.734 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - 8=FIX.4.2|9=88|35=0|34=51|49=OAEAAAN|50=9Q5|52=20230317-06:06:44.734|56=CME|57=G|142=GB|112=IDlf5n3ztz|10=238| 2023-03-17 06:07:15.428 [INFO ] [QFJ Timer] quickfixj.msg.outgoing - 8=FIX.4.2|9=73|35=0|34=52|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.427|56=CME|57=G|142=GB|10=120| 2023-03-17 06:07:15.732 [INFO ] [NioProcessor-2] quickfixj.msg.incoming - 8=FIX.4.2|9=97|35=1|34=8045|369=51|52=20230317-06:07:15.691|49=CME|50=G|56=OAEAAAN|57=9Q5|143=GB|112=IDlf5n3zu0|10=089| 2023-03-17 06:07:15.736 [INFO ] [QF/J Session dispatcher: FIX.4.2:OAEAAAN/9Q5/GB->CME/G:cgw] quickfixj.msg.outgoing - 8=FIX.4.2|9=88|35=0|34=53|49=OAEAAAN|50=9Q5|52=20230317-06:07:15.735|56=CME|57=G|142=GB|112=IDlf5n3zu0|10=167| Also found this old thread ( https://www.quickfixj.org/jira/browse/QFJ-880?focusedCommentId=12807&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1280 ) that identified the issue was due to the check, newSequence < range.getEndSeqNo() At https://github.com/quickfix-j/quickfixj/blob/0ef2ac42ac9966a965b9e811713b9b8c6bc7c32c/quickfixj-core/src/main/java/quickfix/Session.java#L1549 Which makes sense to me. *upon receiving SequenceReset messages QuickFIX/J will determine if a new ResendRequest chunk message needs to get sent out based on the following criteria in the nextSequenceReset method of the Session class by checking if newSequence < range.getEndSeqNo(). Since this fails, some ResendRequests fail to ever get sent out.* A solution has been proposed in the thread too. Not sure what has been fixed following the thread. But the code in Session.java has the newSequence < range.getEndSeqNo() check in github currently. Have anyone successfully certified with CME DC 4.0 with quickfixj. Any help would be very appreciated. Best, Zhu |
|
From: Christoph J. <chr...@ma...> - 2023-03-13 16:25:00
|
There was a Slack channel but I am not sure if it is for general use. I will check. I shortly thought about using Zulip but actually I am not sure if I'd like to have yet another channel where messages come in. But it probably would be good for users to chat about problems. But can't tell if many will use it given that on other places (github discussions or this mailing list) there is not much going on. ;) Cheers Chris On 12.03.23 08:35, Hasnain Khan wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Is there a slack channel for quickfix? > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |
|
From: Christoph J. <chr...@ma...> - 2023-03-13 16:08:00
|
No worries, of course there will be fixes for security problems for the last 2.3.x version. But please understand that I can only do this on a best effort basis. New features will only go into the 3.x version. Cheers Chris On 12.03.23 19:20, Andrew Marlow wrote: > QFJ Documentation:http://www.quickfixj.org/documentation/ > QFJ Support:http://www.quickfixj.org/support/ > > > > Yes, unfortunately I am still using JDK8. Tried to get the project to move to at least 11 but > without success. > > On Sun, 12 Mar 2023 at 17:38, M J <mje...@gm...> wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hi > > Yes I am still using JDK8. > > Kind regards > > Matjaz > > On Sun, 12 Mar 2023, 08:34 Fuad Azhar, <fua...@gm...> wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > My company still using jdk8 but in future Will migrate to 11 > > Pada tanggal Min, 12 Mar 2023 14.13, Hasnain Khan <kha...@gm...> menulis: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Is there a slack channel for quickfix? > > > > On Sat, Mar 11, 2023 at 5:42 AM Christoph John via Quickfixj-users > <qui...@li...> wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Please comment here or vote on > https://github.com/quickfix-j/quickfixj/discussions/620 > > Thank you > _____________________ > -- > Regards, > > Andrew Marlow > http://www.andrewpetermarlow.co.uk > > > > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users -- Christoph John Software Engineering T +49 241 557080-28 chr...@ma... MACD GmbH Oppenhoffallee 103 52066 Aachen, Germany www.macd.com Amtsgericht Aachen: HRB 8151 Ust.-Id: DE 813021663 Geschäftsführer: George Macdonald |
|
From: Andrew M. <mar...@gm...> - 2023-03-12 18:20:40
|
Yes, unfortunately I am still using JDK8. Tried to get the project to move to at least 11 but without success. On Sun, 12 Mar 2023 at 17:38, M J <mje...@gm...> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hi > > Yes I am still using JDK8. > > Kind regards > > Matjaz > > On Sun, 12 Mar 2023, 08:34 Fuad Azhar, <fua...@gm...> wrote: > >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> My company still using jdk8 but in future Will migrate to 11 >> >> Pada tanggal Min, 12 Mar 2023 14.13, Hasnain Khan < >> kha...@gm...> menulis: >> >>> QFJ Documentation: http://www.quickfixj.org/documentation/ >>> QFJ Support: http://www.quickfixj.org/support/ >>> >>> >>> Is there a slack channel for quickfix? >>> >>> >>> >>> On Sat, Mar 11, 2023 at 5:42 AM Christoph John via Quickfixj-users < >>> qui...@li...> wrote: >>> >>>> QFJ Documentation: http://www.quickfixj.org/documentation/ >>>> QFJ Support: http://www.quickfixj.org/support/ >>>> >>>> >>>> Please comment here or vote on >>>> https://github.com/quickfix-j/quickfixj/discussions/620 >>>> >>>> Thank you >>>> _______________________________________________ >>>> Quickfixj-users mailing list >>>> Qui...@li... >>>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >>>> >>> _______________________________________________ >>> Quickfixj-users mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >>> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Regards, Andrew Marlow http://www.andrewpetermarlow.co.uk |
|
From: M J <mje...@gm...> - 2023-03-12 17:37:20
|
Hi Yes I am still using JDK8. Kind regards Matjaz On Sun, 12 Mar 2023, 08:34 Fuad Azhar, <fua...@gm...> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > My company still using jdk8 but in future Will migrate to 11 > > Pada tanggal Min, 12 Mar 2023 14.13, Hasnain Khan <kha...@gm...> > menulis: > >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> Is there a slack channel for quickfix? >> >> >> >> On Sat, Mar 11, 2023 at 5:42 AM Christoph John via Quickfixj-users < >> qui...@li...> wrote: >> >>> QFJ Documentation: http://www.quickfixj.org/documentation/ >>> QFJ Support: http://www.quickfixj.org/support/ >>> >>> >>> Please comment here or vote on >>> https://github.com/quickfix-j/quickfixj/discussions/620 >>> >>> Thank you >>> _______________________________________________ >>> Quickfixj-users mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >>> >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Hasnain K. <kha...@gm...> - 2023-03-12 07:35:13
|
Is there a slack channel for quickfix? |
|
From: Fuad A. <fua...@gm...> - 2023-03-12 07:33:16
|
My company still using jdk8 but in future Will migrate to 11 Pada tanggal Min, 12 Mar 2023 14.13, Hasnain Khan <kha...@gm...> menulis: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Is there a slack channel for quickfix? > > > > On Sat, Mar 11, 2023 at 5:42 AM Christoph John via Quickfixj-users < > qui...@li...> wrote: > >> QFJ Documentation: http://www.quickfixj.org/documentation/ >> QFJ Support: http://www.quickfixj.org/support/ >> >> >> Please comment here or vote on >> https://github.com/quickfix-j/quickfixj/discussions/620 >> >> Thank you >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Hasnain K. <kha...@gm...> - 2023-03-12 07:11:50
|
Is there a slack channel for quickfix? On Sat, Mar 11, 2023 at 5:42 AM Christoph John via Quickfixj-users < qui...@li...> wrote: > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Please comment here or vote on > https://github.com/quickfix-j/quickfixj/discussions/620 > > Thank you > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Christoph J. <chr...@ma...> - 2023-03-11 10:41:16
|
Please comment here or vote on https://github.com/quickfix-j/quickfixj/discussions/620 Thank you |
|
From: Colin D. <co...@ma...> - 2023-03-02 19:53:27
|
Restart FIX connection is not the same as reset the session. The logs below indicate that the FIX acceptor is not available, not that there’s a mismatch in the session config. What parameters did you mutually agree upon for the begin/end of the session? > On Mar 2, 2023, at 10:46 AM, MelaninaBeauty <mel...@gm...> wrote: > > QFJ Documentation: http://www.quickfixj.org/documentation/ > QFJ Support: http://www.quickfixj.org/support/ > > > Hello All, > > I have a FIX connection with an external vendor. This vendor restarts their FIX connection twice on Sunday. I tried the configuration below, but it fails to initialize the session on Sunday. Can you advise on the correct way to allow a session to start and stop twice every day? > Error in Logs: > Session state is not current; resetting FIXT.1.1:MKTDATA->TWINCOME:SessionA > Pending connection not established after 60784ms. > [QFJ Timer] ERROR quickfixj.errorEvent - FIXT.1.1:MKTDATA->TWINCOME:SessionA: java.net.ConnectException during connection to 123.123.123.123:9823 <http://123.123.123.123:9823/>: java.net.ConnectException: Connection timed out. > Session state is not current; resetting FIXT.1.1:MKTDATA->TWINCOME:Session > [QFJ Timer] ERROR quickfixj.errorEvent - FIXT.1.1:MKTDATA->TWINCOME:SessionB: java.net.ConnectException during connection to 123.123.123.123:9823 <http://123.123.123.123:9823/>: java.net.ConnectException: Connection timed out. > > Configuration: > [DEFAULT] > ConnectionType=initiator > ReconnectInterval=60 > SenderCompID=MKTDATA > > [SESSION] > SessionQualifier=SessionA > BeginString=FIXT.1.1 > TargetCompID=TWINCOME > Weekdays=Sun > TimeZone=America/New_York > StartTime=19:00:00 > EndTime=10:00:00 > HeartBtInt=300 > SocketConnectPort=9823 > SocketConnectHost=123.123.123.123 > DataDictionary=somewhere/FIX41.xml > > [SESSION] > SessionQualifier=SessionB > BeginString=FIXT.1.1 > TargetCompID=TWINCOME > Weekdays=Sun > TimeZone=America/New_York > StartTime=11:00:00 > EndTime=18:05:00 > HeartBtInt=300 > SocketConnectPort=9823 > SocketConnectHost=123.123.123.123 > DataDictionary=somewhere/FIX41.xml > > [SESSION] > BeginString=FIXT.1.1 > TargetCompID=TWINCOME > Weekdays=Mon,Tue,Wed,Thu,Fri,Sat > TimeZone=America/New_York > StartTime=19:00:00 > EndTime=18:05:00 > HeartBtInt=300 > SocketConnectPort=9823 > SocketConnectHost=123.123.123.123 > DataDictionary=somewhere/FIX41.xml > > Thanks. > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users |
|
From: MelaninaBeauty <mel...@gm...> - 2023-03-02 18:46:24
|
Hello All, I have a FIX connection with an external vendor. This vendor restarts their FIX connection twice on Sunday. I tried the configuration below, but it fails to initialize the session on Sunday. Can you advise on the correct way to allow a session to start and stop twice every day? Error in Logs: Session state is not current; resetting FIXT.1.1:MKTDATA->TWINCOME:SessionA Pending connection not established after 60784ms. [QFJ Timer] ERROR quickfixj.errorEvent - FIXT.1.1:MKTDATA->TWINCOME:SessionA: java.net.ConnectException during connection to 123.123.123.123:9823: java.net.ConnectException: Connection timed out. Session state is not current; resetting FIXT.1.1:MKTDATA->TWINCOME:Session [QFJ Timer] ERROR quickfixj.errorEvent - FIXT.1.1:MKTDATA->TWINCOME:SessionB: java.net.ConnectException during connection to 123.123.123.123:9823: java.net.ConnectException: Connection timed out. Configuration: [DEFAULT] ConnectionType=initiator ReconnectInterval=60 SenderCompID=MKTDATA [SESSION] SessionQualifier=SessionA BeginString=FIXT.1.1 TargetCompID=TWINCOME Weekdays=Sun TimeZone=America/New_York StartTime=19:00:00 EndTime=10:00:00 HeartBtInt=300 SocketConnectPort=9823 SocketConnectHost=123.123.123.123 DataDictionary=somewhere/FIX41.xml [SESSION] SessionQualifier=SessionB BeginString=FIXT.1.1 TargetCompID=TWINCOME Weekdays=Sun TimeZone=America/New_York StartTime=11:00:00 EndTime=18:05:00 HeartBtInt=300 SocketConnectPort=9823 SocketConnectHost=123.123.123.123 DataDictionary=somewhere/FIX41.xml [SESSION] BeginString=FIXT.1.1 TargetCompID=TWINCOME Weekdays=Mon,Tue,Wed,Thu,Fri,Sat TimeZone=America/New_York StartTime=19:00:00 EndTime=18:05:00 HeartBtInt=300 SocketConnectPort=9823 SocketConnectHost=123.123.123.123 DataDictionary=somewhere/FIX41.xml Thanks. |
|
From: Christoph J. <chr...@ma...> - 2023-02-04 11:48:07
|
Please check if the data dictionary contains all needed tags. Otherwise tags might get truncated. Cheers Chris 4 Feb 2023 12:39:54 Jalal Kharsa <jk...@gr...>: > Hi all, > > When the FIX message that is being received via ‘fromApp’ from the server of type AR, it works fine and the whole message is delivered, when the message type is AE then the message is being truncated, for example I cannot find the side fields such as 54, 11, 37, etc. > > Can anyone help with this? > > Thanks, > > Privileged or confidential information may be contained in this message. If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Gresham does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Gresham does not accept liability for any damage sustained as a result of viruses. Statements in this message that do not relate to the business of Gresham are neither given nor endorsed by the company or its directors. Gresham Technologies plc Registered in England and Wales. Company No. 01072032 Registered Office: Aldermary House, 10-15 Queen Street, London, EC4N 1TX. Further information about Gresham Technologies can be found on our website: www.greshamtech.com |
|
From: Jalal K. <jk...@gr...> - 2023-02-01 16:48:04
|
Hi all, When the FIX message that is being received via 'fromApp' from the server of type AR, it works fine and the whole message is delivered, when the message type is AE then the message is being truncated, for example I cannot find the side fields such as 54, 11, 37, etc. Can anyone help with this? Thanks, Privileged or confidential information may be contained in this message. If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Gresham does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Gresham does not accept liability for any damage sustained as a result of viruses. Statements in this message that do not relate to the business of Gresham are neither given nor endorsed by the company or its directors. Gresham Technologies plc Registered in England and Wales. Company No. 01072032 Registered Office: Aldermary House, 10-15 Queen Street, London, EC4N 1TX. Further information about Gresham Technologies can be found on our website: www.greshamtech.com |
|
From: Christoph J. <chr...@ma...> - 2023-01-04 17:04:32
|
Hi, is anyone able to conduct tests against a proxy? Preferrably with and without SSL enabled? In #441 <https://github.com/quickfix-j/quickfixj/pull/441> I created a pull request which is compiled against MINA 2.2.x which overhauled the SSL support. To make it compile I needed to do some minor changes. But I cannot test against a proxy. Is anyone of you guys able to help me out with that? Please answer here or on https://github.com/quickfix-j/quickfixj/discussions/596 Thanks in advance! |
|
From: Christoph J. <chr...@ma...> - 2022-12-10 12:40:14
|
Hi Geoff, Good catch. I knew that we modified the files to work around some code generation issues (although I didn't remember which issues exactly). But I wasn't aware that we include the unmodified files in the distribution. Maybe that should be changed to avoid issues like the one you were having. Best regards Chris Dec 10, 2022 05:46:11 Geoffrey Gershaw <gge...@ho...>: > Hi Christoph, > > I recalled seeing that there are actually 2 versions of several of the fix specs. See here for instance. https://github.com/quickfix-j/quickfixj/tree/master/quickfixj-messages/quickfixj-messages-fix50sp2/src/main/resources > > If you diff the files, you can see the following lines are changed in FIX50SP2.modified.xml[https://github.com/quickfix-j/quickfixj/blob/master/quickfixj-messages/quickfixj-messages-fix50sp2/src/main/resources/FIX50SP2.modified.xml] to avoid the issue. The pom file you mentioned is referring to this file, which is why it works and mine doesn't. I don't know how to make this work another way. > > FIX50SP2.modified.xml > <!-- MODIFIED: renamed SecurityXML field to SecurityXMLData to avoid duplicate field --> > <field name="SecurityXMLData" required="N"/> > > Geoff > > > ---------------------------------------- > *From:* Christoph John via Quickfixj-users <qui...@li...> > *Sent:* Friday, December 9, 2022 3:08 PM > *To:* qui...@li... <qui...@li...> > *Cc:* Christoph John <chr...@ma...> > *Subject:* Re: [Quickfixj-users] Source generated by maven plugin does not compile > > QFJ Documentation: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.quickfixj.org%2Fdocumentation%2F&data=05%7C01%7C%7C9f4e56c2b0294748390008dada2156c7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638062135041152004%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=et3uJmAgxMp5dR13D%2FBbGjvkvnuZ5lqnyJX5JGwjkdE%3D&reserved=0 > QFJ Support: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.quickfixj.org%2Fsupport%2F&data=05%7C01%7C%7C9f4e56c2b0294748390008dada2156c7%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638062135041152004%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7PodMTrjDpLCdaHU6NjQWiwBBKUQNbiPtulgeS1x5Dk%3D&reserved=0 > > |
103 messages has been excluded from this view by a project administrator.
