quickfix-developers Mailing List for QuickFIX (Page 254)
Brought to you by:
orenmnero
Menu
▾
▴
quickfix-developers — QuickFIX developers forum
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
(5) |
Mar
(16) |
Apr
(15) |
May
(17) |
Jun
(33) |
Jul
(35) |
Aug
(34) |
Sep
(19) |
Oct
(40) |
Nov
(51) |
Dec
(43) |
| 2003 |
Jan
(45) |
Feb
(79) |
Mar
(124) |
Apr
(121) |
May
(132) |
Jun
(77) |
Jul
(110) |
Aug
(57) |
Sep
(48) |
Oct
(83) |
Nov
(60) |
Dec
(40) |
| 2004 |
Jan
(67) |
Feb
(72) |
Mar
(74) |
Apr
(87) |
May
(70) |
Jun
(96) |
Jul
(75) |
Aug
(147) |
Sep
(128) |
Oct
(83) |
Nov
(67) |
Dec
(42) |
| 2005 |
Jan
(110) |
Feb
(84) |
Mar
(68) |
Apr
(55) |
May
(51) |
Jun
(192) |
Jul
(111) |
Aug
(100) |
Sep
(79) |
Oct
(127) |
Nov
(73) |
Dec
(112) |
| 2006 |
Jan
(95) |
Feb
(120) |
Mar
(138) |
Apr
(127) |
May
(124) |
Jun
(97) |
Jul
(103) |
Aug
(88) |
Sep
(138) |
Oct
(91) |
Nov
(112) |
Dec
(57) |
| 2007 |
Jan
(55) |
Feb
(35) |
Mar
(56) |
Apr
(16) |
May
(20) |
Jun
(77) |
Jul
(43) |
Aug
(47) |
Sep
(29) |
Oct
(54) |
Nov
(39) |
Dec
(40) |
| 2008 |
Jan
(69) |
Feb
(79) |
Mar
(122) |
Apr
(106) |
May
(114) |
Jun
(76) |
Jul
(83) |
Aug
(71) |
Sep
(53) |
Oct
(75) |
Nov
(54) |
Dec
(43) |
| 2009 |
Jan
(32) |
Feb
(31) |
Mar
(64) |
Apr
(48) |
May
(38) |
Jun
(43) |
Jul
(35) |
Aug
(15) |
Sep
(52) |
Oct
(62) |
Nov
(62) |
Dec
(21) |
| 2010 |
Jan
(44) |
Feb
(10) |
Mar
(47) |
Apr
(22) |
May
(5) |
Jun
(54) |
Jul
(19) |
Aug
(54) |
Sep
(16) |
Oct
(15) |
Nov
(7) |
Dec
(8) |
| 2011 |
Jan
(18) |
Feb
(9) |
Mar
(5) |
Apr
(5) |
May
(41) |
Jun
(40) |
Jul
(29) |
Aug
(17) |
Sep
(12) |
Oct
(23) |
Nov
(22) |
Dec
(11) |
| 2012 |
Jan
(8) |
Feb
(24) |
Mar
(5) |
Apr
(5) |
May
(6) |
Jun
(5) |
Jul
(5) |
Aug
(5) |
Sep
(2) |
Oct
(9) |
Nov
(2) |
Dec
(18) |
| 2013 |
Jan
(25) |
Feb
(16) |
Mar
(8) |
Apr
(2) |
May
(16) |
Jun
(17) |
Jul
(2) |
Aug
(13) |
Sep
(3) |
Oct
(4) |
Nov
(1) |
Dec
|
| 2014 |
Jan
(2) |
Feb
|
Mar
(22) |
Apr
(9) |
May
(3) |
Jun
(1) |
Jul
(5) |
Aug
(11) |
Sep
(18) |
Oct
(4) |
Nov
(4) |
Dec
(3) |
| 2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
(4) |
Jun
(37) |
Jul
|
Aug
(4) |
Sep
(6) |
Oct
(1) |
Nov
(4) |
Dec
(2) |
| 2016 |
Jan
(9) |
Feb
(3) |
Mar
(7) |
Apr
(1) |
May
(8) |
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(3) |
Nov
(16) |
Dec
|
| 2017 |
Jan
(1) |
Feb
(15) |
Mar
(2) |
Apr
(12) |
May
(4) |
Jun
(7) |
Jul
(5) |
Aug
|
Sep
|
Oct
|
Nov
(23) |
Dec
(8) |
| 2018 |
Jan
(2) |
Feb
(4) |
Mar
(2) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(5) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(12) |
Aug
(5) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Billy R. <bi...@et...> - 2004-02-05 19:02:07
|
Are there Javadocs avail for the QuickFix Java API? |
|
From: Miller, O. <OM...@ri...> - 2004-02-04 03:54:57
|
What version are you using? I think this was an old bug that was fixed = in a later release. -------------------------- Sent from my BlackBerry Wireless Handheld -----Original Message----- From: sri...@rh... <sri...@rh...> To: qui...@li... = <qui...@li...> Sent: Tue Feb 03 11:58:21 2004 Subject: [Quickfix-developers] sequence number problem How can this happen? The messages that caused sequence number problem are the following: =20 8=3DFIX.4.29=3D19435=3DD34=3D904249=3DPWF205N50=3DLDO52=3D20040130-14:32:= 16.42756=3DCME5 7=3DG142=3DRHO1=3DRHO1411=3D700B21=3D138=3D140=3D244=3D11297554=3D255=3DE= S59=3D060=3D20040130-08 :32:16107=3DESH4167=3DFUT204=3D09702=3D19717=3D700B10=3D000 =20 8=3DFIX.4.29=3D7635=3D034=3D904249=3DPWF205N50=3DLDO52=3D20040130-14:32:4= 6.00556=3DCME57 =3DG142=3DRHO10=3D064 =20 It appears that QuickFix sent a heartbeat with the same sequence number as the preceding new order message. It looks like we need to some kind of locking mechanism on outgoing sequence number. Srinivas Potula ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: <sri...@rh...> - 2004-02-04 03:49:32
|
How can this happen? The messages that caused sequence number problem are the following: =20 8=3DFIX.4.29=3D19435=3DD34=3D904249=3DPWF205N50=3DLDO52=3D20040130-14:32:= 16.42756=3DCME5 7=3DG142=3DRHO1=3DRHO1411=3D700B21=3D138=3D140=3D244=3D11297554=3D255=3DE= S59=3D060=3D20040130-08 :32:16107=3DESH4167=3DFUT204=3D09702=3D19717=3D700B10=3D000 =20 8=3DFIX.4.29=3D7635=3D034=3D904249=3DPWF205N50=3DLDO52=3D20040130-14:32:4= 6.00556=3DCME57 =3DG142=3DRHO10=3D064 =20 It appears that QuickFix sent a heartbeat with the same sequence number as the preceding new order message. It looks like we need to some kind of locking mechanism on outgoing sequence number. Srinivas Potula |
|
From: Miller, O. <OM...@ri...> - 2004-02-04 03:10:02
|
Looks like there is an exception that isn't being caught. I'll take a = look at it. -------------------------- Sent from my BlackBerry Wireless Handheld -----Original Message----- From: Billy Rutledge <bru...@ra...> CC: Quickfix-Developers <qui...@li...> Sent: Tue Feb 03 19:31:23 2004 Subject: Re: [Quickfix-developers] Unexpected exception in native code = outside the VM FYI- I added the line: 'SocketAcceptPort=3D8143' to the defaults section and resolved the unexpected exception. -Billy Billy Rutledge wrote: > Hi- > > I just successfully compiled the quickfix_jni.dll per the instructions = > in the docs (after a fresh install of VisualStudio.NET) on Windows XP=20 > Professional. I wrote a simple Acceptor application and get the=20 > following when I run it. Anyone seen this or have any ideas? > > Thanks, > -Billy > > ------------------------------------ > > An unexpected exception has been detected in native code outside the = VM. > Unexpected Signal : unknown exception code (0xe06d7363) occurred at=20 > PC=3D0x77E73887 > Function=3DRaiseException+0x50 > Library=3DC:\WINDOWS\system32\kernel32.dll > > Current Java thread: > at org.quickfix.SocketAcceptor.create(Native Method) > at org.quickfix.SocketAcceptor.<init>(Unknown Source) > at com.randomwalk.quickfix.FIXAcceptor.main(FIXAcceptor.java:29) > > Dynamic libraries: > 0x00400000 - 0x00407000 C:\j2sdk1.4.2_03\bin\javaw.exe > 0x77F50000 - 0x77FF7000 C:\WINDOWS\System32\ntdll.dll > 0x77E60000 - 0x77F46000 C:\WINDOWS\system32\kernel32.dll > 0x77DD0000 - 0x77E5D000 C:\WINDOWS\system32\ADVAPI32.dll > 0x78000000 - 0x78086000 C:\WINDOWS\system32\RPCRT4.dll > 0x77D40000 - 0x77DCC000 C:\WINDOWS\system32\USER32.dll > 0x77C70000 - 0x77CB0000 C:\WINDOWS\system32\GDI32.dll > 0x77C10000 - 0x77C63000 C:\WINDOWS\system32\MSVCRT.dll > 0x08000000 - 0x08138000 C:\j2sdk1.4.2_03\jre\bin\client\jvm.dll > 0x76B40000 - 0x76B6C000 C:\WINDOWS\System32\WINMM.dll > 0x10000000 - 0x10007000 C:\j2sdk1.4.2_03\jre\bin\hpi.dll > 0x00820000 - 0x0082E000 C:\j2sdk1.4.2_03\jre\bin\verify.dll > 0x00830000 - 0x00849000 C:\j2sdk1.4.2_03\jre\bin\java.dll > 0x00850000 - 0x0085D000 C:\j2sdk1.4.2_03\jre\bin\zip.dll > 0x02E40000 - 0x02EB6000 C:\projects\Tibco = Test\lib\quickfix_jni.dll > 0x71AB0000 - 0x71AC5000 C:\WINDOWS\System32\WS2_32.dll > 0x71AA0000 - 0x71AA8000 C:\WINDOWS\System32\WS2HELP.dll > 0x771B0000 - 0x772D1000 C:\WINDOWS\system32\ole32.dll > 0x77120000 - 0x771AB000 C:\WINDOWS\system32\OLEAUT32.dll > 0x7C080000 - 0x7C0F7000 C:\WINDOWS\System32\MSVCP70.dll > 0x7C000000 - 0x7C054000 C:\WINDOWS\System32\MSVCR70.dll > 0x76FD0000 - 0x77048000 C:\WINDOWS\System32\CLBCATQ.DLL > 0x77050000 - 0x77115000 C:\WINDOWS\System32\COMRes.dll > 0x77C00000 - 0x77C07000 C:\WINDOWS\system32\VERSION.dll > 0x76C90000 - 0x76CB2000 C:\WINDOWS\system32\imagehlp.dll > 0x6D510000 - 0x6D58D000 C:\WINDOWS\system32\DBGHELP.dll > 0x76BF0000 - 0x76BFB000 C:\WINDOWS\System32\PSAPI.DLL > > Heap at VM Abort: > Heap > def new generation total 576K, used 284K [0x10010000, 0x100b0000,=20 > 0x104f0000) > eden space 512K, 54% used [0x10010000, 0x100557f0, 0x10090000) > from space 64K, 9% used [0x100a0000, 0x100a1920, 0x100b0000) > to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000) > tenured generation total 1408K, used 244K [0x104f0000, 0x10650000,=20 > 0x14010000) > the space 1408K, 17% used [0x104f0000, 0x1052d128, 0x1052d200,=20 > 0x10650000) > compacting perm gen total 7168K, used 7128K [0x14010000, 0x14710000,=20 > 0x18010000) > the space 7168K, 99% used [0x14010000, 0x14706078, 0x14706200,=20 > 0x14710000) > > Local Time =3D Tue Feb 03 17:08:59 2004 > Elapsed Time =3D 1 > # > # The exception above was detected in native code outside the VM > # > # Java VM: Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode) > # > # An error report file has been saved as hs_err_pid1076.log. > # Please refer to the file for further information. > # > Process terminated with exit code 1 > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Billy R. <bru...@ra...> - 2004-02-04 01:31:04
|
FYI- I added the line: 'SocketAcceptPort=8143' to the defaults section and resolved the unexpected exception. -Billy Billy Rutledge wrote: > Hi- > > I just successfully compiled the quickfix_jni.dll per the instructions > in the docs (after a fresh install of VisualStudio.NET) on Windows XP > Professional. I wrote a simple Acceptor application and get the > following when I run it. Anyone seen this or have any ideas? > > Thanks, > -Billy > > ------------------------------------ > > An unexpected exception has been detected in native code outside the VM. > Unexpected Signal : unknown exception code (0xe06d7363) occurred at > PC=0x77E73887 > Function=RaiseException+0x50 > Library=C:\WINDOWS\system32\kernel32.dll > > Current Java thread: > at org.quickfix.SocketAcceptor.create(Native Method) > at org.quickfix.SocketAcceptor.<init>(Unknown Source) > at com.randomwalk.quickfix.FIXAcceptor.main(FIXAcceptor.java:29) > > Dynamic libraries: > 0x00400000 - 0x00407000 C:\j2sdk1.4.2_03\bin\javaw.exe > 0x77F50000 - 0x77FF7000 C:\WINDOWS\System32\ntdll.dll > 0x77E60000 - 0x77F46000 C:\WINDOWS\system32\kernel32.dll > 0x77DD0000 - 0x77E5D000 C:\WINDOWS\system32\ADVAPI32.dll > 0x78000000 - 0x78086000 C:\WINDOWS\system32\RPCRT4.dll > 0x77D40000 - 0x77DCC000 C:\WINDOWS\system32\USER32.dll > 0x77C70000 - 0x77CB0000 C:\WINDOWS\system32\GDI32.dll > 0x77C10000 - 0x77C63000 C:\WINDOWS\system32\MSVCRT.dll > 0x08000000 - 0x08138000 C:\j2sdk1.4.2_03\jre\bin\client\jvm.dll > 0x76B40000 - 0x76B6C000 C:\WINDOWS\System32\WINMM.dll > 0x10000000 - 0x10007000 C:\j2sdk1.4.2_03\jre\bin\hpi.dll > 0x00820000 - 0x0082E000 C:\j2sdk1.4.2_03\jre\bin\verify.dll > 0x00830000 - 0x00849000 C:\j2sdk1.4.2_03\jre\bin\java.dll > 0x00850000 - 0x0085D000 C:\j2sdk1.4.2_03\jre\bin\zip.dll > 0x02E40000 - 0x02EB6000 C:\projects\Tibco Test\lib\quickfix_jni.dll > 0x71AB0000 - 0x71AC5000 C:\WINDOWS\System32\WS2_32.dll > 0x71AA0000 - 0x71AA8000 C:\WINDOWS\System32\WS2HELP.dll > 0x771B0000 - 0x772D1000 C:\WINDOWS\system32\ole32.dll > 0x77120000 - 0x771AB000 C:\WINDOWS\system32\OLEAUT32.dll > 0x7C080000 - 0x7C0F7000 C:\WINDOWS\System32\MSVCP70.dll > 0x7C000000 - 0x7C054000 C:\WINDOWS\System32\MSVCR70.dll > 0x76FD0000 - 0x77048000 C:\WINDOWS\System32\CLBCATQ.DLL > 0x77050000 - 0x77115000 C:\WINDOWS\System32\COMRes.dll > 0x77C00000 - 0x77C07000 C:\WINDOWS\system32\VERSION.dll > 0x76C90000 - 0x76CB2000 C:\WINDOWS\system32\imagehlp.dll > 0x6D510000 - 0x6D58D000 C:\WINDOWS\system32\DBGHELP.dll > 0x76BF0000 - 0x76BFB000 C:\WINDOWS\System32\PSAPI.DLL > > Heap at VM Abort: > Heap > def new generation total 576K, used 284K [0x10010000, 0x100b0000, > 0x104f0000) > eden space 512K, 54% used [0x10010000, 0x100557f0, 0x10090000) > from space 64K, 9% used [0x100a0000, 0x100a1920, 0x100b0000) > to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000) > tenured generation total 1408K, used 244K [0x104f0000, 0x10650000, > 0x14010000) > the space 1408K, 17% used [0x104f0000, 0x1052d128, 0x1052d200, > 0x10650000) > compacting perm gen total 7168K, used 7128K [0x14010000, 0x14710000, > 0x18010000) > the space 7168K, 99% used [0x14010000, 0x14706078, 0x14706200, > 0x14710000) > > Local Time = Tue Feb 03 17:08:59 2004 > Elapsed Time = 1 > # > # The exception above was detected in native code outside the VM > # > # Java VM: Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode) > # > # An error report file has been saved as hs_err_pid1076.log. > # Please refer to the file for further information. > # > Process terminated with exit code 1 > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Billy R. <bru...@ra...> - 2004-02-04 01:16:53
|
Hi-
I just successfully compiled the quickfix_jni.dll per the instructions
in the docs (after a fresh install of VisualStudio.NET) on Windows XP
Professional. I wrote a simple Acceptor application and get the
following when I run it. Anyone seen this or have any ideas?
Thanks,
-Billy
------------------------------------
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : unknown exception code (0xe06d7363) occurred at
PC=0x77E73887
Function=RaiseException+0x50
Library=C:\WINDOWS\system32\kernel32.dll
Current Java thread:
at org.quickfix.SocketAcceptor.create(Native Method)
at org.quickfix.SocketAcceptor.<init>(Unknown Source)
at com.randomwalk.quickfix.FIXAcceptor.main(FIXAcceptor.java:29)
Dynamic libraries:
0x00400000 - 0x00407000 C:\j2sdk1.4.2_03\bin\javaw.exe
0x77F50000 - 0x77FF7000 C:\WINDOWS\System32\ntdll.dll
0x77E60000 - 0x77F46000 C:\WINDOWS\system32\kernel32.dll
0x77DD0000 - 0x77E5D000 C:\WINDOWS\system32\ADVAPI32.dll
0x78000000 - 0x78086000 C:\WINDOWS\system32\RPCRT4.dll
0x77D40000 - 0x77DCC000 C:\WINDOWS\system32\USER32.dll
0x77C70000 - 0x77CB0000 C:\WINDOWS\system32\GDI32.dll
0x77C10000 - 0x77C63000 C:\WINDOWS\system32\MSVCRT.dll
0x08000000 - 0x08138000 C:\j2sdk1.4.2_03\jre\bin\client\jvm.dll
0x76B40000 - 0x76B6C000 C:\WINDOWS\System32\WINMM.dll
0x10000000 - 0x10007000 C:\j2sdk1.4.2_03\jre\bin\hpi.dll
0x00820000 - 0x0082E000 C:\j2sdk1.4.2_03\jre\bin\verify.dll
0x00830000 - 0x00849000 C:\j2sdk1.4.2_03\jre\bin\java.dll
0x00850000 - 0x0085D000 C:\j2sdk1.4.2_03\jre\bin\zip.dll
0x02E40000 - 0x02EB6000 C:\projects\Tibco Test\lib\quickfix_jni.dll
0x71AB0000 - 0x71AC5000 C:\WINDOWS\System32\WS2_32.dll
0x71AA0000 - 0x71AA8000 C:\WINDOWS\System32\WS2HELP.dll
0x771B0000 - 0x772D1000 C:\WINDOWS\system32\ole32.dll
0x77120000 - 0x771AB000 C:\WINDOWS\system32\OLEAUT32.dll
0x7C080000 - 0x7C0F7000 C:\WINDOWS\System32\MSVCP70.dll
0x7C000000 - 0x7C054000 C:\WINDOWS\System32\MSVCR70.dll
0x76FD0000 - 0x77048000 C:\WINDOWS\System32\CLBCATQ.DLL
0x77050000 - 0x77115000 C:\WINDOWS\System32\COMRes.dll
0x77C00000 - 0x77C07000 C:\WINDOWS\system32\VERSION.dll
0x76C90000 - 0x76CB2000 C:\WINDOWS\system32\imagehlp.dll
0x6D510000 - 0x6D58D000 C:\WINDOWS\system32\DBGHELP.dll
0x76BF0000 - 0x76BFB000 C:\WINDOWS\System32\PSAPI.DLL
Heap at VM Abort:
Heap
def new generation total 576K, used 284K [0x10010000, 0x100b0000,
0x104f0000)
eden space 512K, 54% used [0x10010000, 0x100557f0, 0x10090000)
from space 64K, 9% used [0x100a0000, 0x100a1920, 0x100b0000)
to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000)
tenured generation total 1408K, used 244K [0x104f0000, 0x10650000,
0x14010000)
the space 1408K, 17% used [0x104f0000, 0x1052d128, 0x1052d200,
0x10650000)
compacting perm gen total 7168K, used 7128K [0x14010000, 0x14710000,
0x18010000)
the space 7168K, 99% used [0x14010000, 0x14706078, 0x14706200,
0x14710000)
Local Time = Tue Feb 03 17:08:59 2004
Elapsed Time = 1
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode)
#
# An error report file has been saved as hs_err_pid1076.log.
# Please refer to the file for further information.
#
Process terminated with exit code 1
|
|
From: Joerg T. <Joe...@ma...> - 2004-02-03 09:18:46
|
Hi Jim, thanks for offering your help! > What are the specifics of the "Sending new message while resending to > INFINITY" issue? Id possible I would like to create an acceptance test for > it. The ResendRequest FROM: nnn TO: 0 means INFINITY, that is "Please resend *all* messages starting from nnn" That is you do not specify an exact message number in the TO: field. This may be helpful after a connection break down if you try to catch up. What QuickFIX does is the following: -> ResendRequest FROM: 42 TO: 0 <- Msg 42, PossDupFlag=Y <- Msg 43, PossDupFlag=Y ... <- Msg 50, PossDupFlag=Y vvvvvvvvvvvvvvvvvvvvvvvvvv <- Msg 63, PossDupFlag=N ^^^^^^^^^^^^^^^^^^^^^^^^^^ <- Msg 51, PossDupFlag=Y ... <- Msg 62, PossDupFlag=Y I.e. while resending old messages (PossDupFlag=Y), QuickFIX also sents *new* messages with much larger msg numbers. This troubles some of our clients. The FIX spec is not very clear about that situation. The more robust solution IMHO would be to send *NEW* messages after all old messages have been resent. Cheers, Jörg |
|
From: James C. D. <jc...@co...> - 2004-02-03 01:15:21
|
Joerg, What are the specifics of the "Sending new message while resending to INFINITY" issue? Id possible I would like to create an acceptance test = for it. Jim =20 James C. Downs Connamara Systems, LLC 53 W. Jackson Blvd Suite 1627 Chicago, IL 60604 312 - 282 - 7746 www.connamara.com -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Miller, Oren Sent: Monday, February 02, 2004 3:43 PM To: Joerg Thoennes Cc: ro...@ri...; qui...@li... Subject: RE: [Quickfix-developers] Fix Log Reader I've already taken care of it. It wasn't that bad it's just that JNI = isn't nearly as easy to work with as managed C++. We are going to be releasing version 1.7 in conjunction with a newly designed website being put together by Anne Lewis, a great designer over = at ThoughtWorks. A fix for that can still be added. For now it will be one that simply solves the problem in the simplest manner which will be to just lock the session mutex during resends. Future versions we may revisit some of = the longer term solutions proposed such as adding a proper send queue. --oren -----Original Message----- From: Joerg Thoennes [mailto:Joe...@ma...] Sent: Monday, February 02, 2004 6:21 AM To: Miller, Oren Cc: ro...@ri...; qui...@li... Subject: Re: [Quickfix-developers] Fix Log Reader Miller, Oren wrote: > Yes, of course it can be done. It's just harder. :) Oren, what I actually wanted to ask you is "please, do not forget Java." I am afraid I am still not fit enough to do it myself since I am still lacking time to spent on QuickFIX. Is it possible to guess from .NET changes what to do for Java? BTW, what are your plans for releasing 1.7? Is it still possible to add some stuff; I think about the issue "Sending new message while resending to INFINITY"? Cheers, J=F6rg ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on = Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Miller, O. <OM...@ri...> - 2004-02-02 21:42:38
|
I've already taken care of it. It wasn't that bad it's just that JNI = isn't nearly as easy to work with as managed C++. We are going to be releasing version 1.7 in conjunction with a newly = designed website being put together by Anne Lewis, a great designer over = at ThoughtWorks. A fix for that can still be added. For now it will be one that simply = solves the problem in the simplest manner which will be to just lock the = session mutex during resends. Future versions we may revisit some of = the longer term solutions proposed such as adding a proper send queue. --oren -----Original Message----- From: Joerg Thoennes [mailto:Joe...@ma...]=20 Sent: Monday, February 02, 2004 6:21 AM To: Miller, Oren Cc: ro...@ri...; qui...@li... Subject: Re: [Quickfix-developers] Fix Log Reader Miller, Oren wrote: > Yes, of course it can be done. It's just harder. :) Oren, what I actually wanted to ask you is "please, do not forget Java." I am afraid I am still not fit enough to do it myself since I am still=20 lacking time to spent on QuickFIX. Is it possible to guess from .NET=20 changes what to do for Java? BTW, what are your plans for releasing 1.7? Is it still possible to add = some stuff; I think about the issue "Sending new message while resending = to INFINITY"? Cheers, J=F6rg |
|
From: Oren M. <ore...@ya...> - 2004-02-02 20:32:17
|
It actually does take a considerable amount of memory in order to compile due to the generated typesafe message classes which are really quite large, but it probably has more to due with how much memory is made available to the compiler than what is available on your machine. You can change this value by change the -Xmx256m setting in src/java/build.sh to something larger. --oren --- Billy Rutledge <bru...@ra...> wrote: > Hi All- > > I've just downloaded QuickFIX and am attempting to > build the Java > library for use in a client app. When I go to the > quickfix/src/java > directory and run 'ant jar' I bombs out with > OutOfMemoryError. I'm > running this on a P4 with 512M RAM. I can't imagine > its really running > out of memory...something must be config'd wrong. > What am I missing? > > ------------------------------------------- > $ ant compile > Buildfile: build.xml > > init: > > compile: > [javac] Compiling 1306 source files to > C:\Documents and > Settings\Billy > Rutledge\Desktop\quickfix\src\java\build > > > [javac] The system is out of resources. > [javac] Consult the following stack trace for > details. > [javac] java.lang.OutOfMemoryError > > BUILD FAILED > --------------------------------------------- > Thanks, > -Billy > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and > Integration > See the breadth of Eclipse activity. February 3-5 in > Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |
|
From: Billy R. <bru...@ra...> - 2004-02-02 18:36:53
|
Hi All-
I've just downloaded QuickFIX and am attempting to build the Java
library for use in a client app. When I go to the quickfix/src/java
directory and run 'ant jar' I bombs out with OutOfMemoryError. I'm
running this on a P4 with 512M RAM. I can't imagine its really running
out of memory...something must be config'd wrong. What am I missing?
-------------------------------------------
$ ant compile
Buildfile: build.xml
init:
compile:
[javac] Compiling 1306 source files to C:\Documents and
Settings\Billy Rutledge\Desktop\quickfix\src\java\build
[javac] The system is out of resources.
[javac] Consult the following stack trace for details.
[javac] java.lang.OutOfMemoryError
BUILD FAILED
---------------------------------------------
Thanks,
-Billy
|
|
From: Joerg T. <Joe...@ma...> - 2004-02-02 12:21:00
|
Miller, Oren wrote: > Yes, of course it can be done. It's just harder. :) Oren, what I actually wanted to ask you is "please, do not forget Java." I am afraid I am still not fit enough to do it myself since I am still lacking time to spent on QuickFIX. Is it possible to guess from .NET changes what to do for Java? BTW, what are your plans for releasing 1.7? Is it still possible to add some stuff; I think about the issue "Sending new message while resending to INFINITY"? Cheers, Jörg |
|
From: Miller, O. <OM...@ri...> - 2004-02-02 11:49:14
|
Yes, of course it can be done. It's just harder. :) -------------------------- Sent from my BlackBerry Wireless Handheld -----Original Message----- From: Joerg Thoennes <Joe...@ma...> To: Miller, Oren <OM...@ri...> CC: Rob Kulseth <ro...@ri...>; = qui...@li... = <qui...@li...> Sent: Mon Feb 02 04:12:27 2004 Subject: Re: [Quickfix-developers] Fix Log Reader Miller, Oren wrote: > This can be done with some modification. In C++ this is already > possible since the constructor for Message takes in a DataDictionary > which it can use to parse messages with repeating groups. What we = need > to do is wrap the data dictionary with a managed C++ class and allow = it > to be passed into the .NET Message constructor, then the message can > parse properly. Oren, I think this should be added to the Java API in the same way. Or=20 is there already that possibility? J=F6rg > --oren >=20 > -----Original Message----- > From: Rob Kulseth [mailto:ro...@ri...]=20 > Sent: Friday, January 23, 2004 8:25 AM > To: qui...@li... > Subject: [Quickfix-developers] Fix Log Reader >=20 > I am using C# trying to build an application that can read a FIX = message > log and present it in a more readable format in order to debug certin > application level errors. I have used the QuickFix.Message class to > parse simple messages, however any message with repeating groups = throws > an invalid message exception. I gather that the problem is that the > Message(string) constructor isn't able to handle parsing repeating > groups unless I somehow attach the Fix spec XML file or use some sort = of > specialized parser. Is this possible with QuickFix, or should I look > elsewhere? Is the only option building my own parser? |
|
From: Joerg T. <Joe...@ma...> - 2004-02-02 11:16:17
|
Miller, Oren wrote: > This can be done with some modification. In C++ this is already > possible since the constructor for Message takes in a DataDictionary > which it can use to parse messages with repeating groups. What we need > to do is wrap the data dictionary with a managed C++ class and allow it > to be passed into the .NET Message constructor, then the message can > parse properly. Oren, I think this should be added to the Java API in the same way. Or is there already that possibility? Jörg > --oren > > -----Original Message----- > From: Rob Kulseth [mailto:ro...@ri...] > Sent: Friday, January 23, 2004 8:25 AM > To: qui...@li... > Subject: [Quickfix-developers] Fix Log Reader > > I am using C# trying to build an application that can read a FIX message > log and present it in a more readable format in order to debug certin > application level errors. I have used the QuickFix.Message class to > parse simple messages, however any message with repeating groups throws > an invalid message exception. I gather that the problem is that the > Message(string) constructor isn't able to handle parsing repeating > groups unless I somehow attach the Fix spec XML file or use some sort of > specialized parser. Is this possible with QuickFix, or should I look > elsewhere? Is the only option building my own parser? |
|
From: Miller, O. <OM...@ri...> - 2004-01-31 06:31:56
|
This can be done with some modification. In C++ this is already possible since the constructor for Message takes in a DataDictionary which it can use to parse messages with repeating groups. What we need to do is wrap the data dictionary with a managed C++ class and allow it to be passed into the .NET Message constructor, then the message can parse properly. --oren -----Original Message----- From: Rob Kulseth [mailto:ro...@ri...]=20 Sent: Friday, January 23, 2004 8:25 AM To: qui...@li... Subject: [Quickfix-developers] Fix Log Reader I am using C# trying to build an application that can read a FIX message log and present it in a more readable format in order to debug certin application level errors. I have used the QuickFix.Message class to parse simple messages, however any message with repeating groups throws an invalid message exception. I gather that the problem is that the Message(string) constructor isn't able to handle parsing repeating groups unless I somehow attach the Fix spec XML file or use some sort of specialized parser. Is this possible with QuickFix, or should I look elsewhere? Is the only option building my own parser? ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Caleb E. <ca...@bk...> - 2004-01-31 02:11:34
|
On Wed, Jan 28, 2004 at 10:36:05AM -0600, Jon Dahl wrote:
> This may be somewhat off topic since QuickFIX is an open source
> project, but I was wondering if anyone has switched the socket
> transport layer with Tibco or something similar? Any pointers would
> be appreciated. Thanks, Jon Dahl
The big problem with pushing a FIX session over something
datagram-oriented like TIB/RV is how do you do authentication?
How can you tell who a message is really from? I'd be
interested in peoples thoughts on this.
--
Caleb Epstein | bklyn . org | A man of genius makes no mistakes. His errors
cae at | Brooklyn Dust | are volitional and are the portals of
bklyn dot org | Bunny Mfg. | discovery.
| | -- James Joyce, "Ulysses"
|
|
From: Oren M. <ore...@ya...> - 2004-01-31 00:39:21
|
The engine was designed with this in mind, although I don't know that anyone has implemented it. Essentially new TibcoInitiator and TibcoAcceptor classes need to be created. Do you intend on using the point-to-point functionality to do this, or will you be broadcasting messages on subjects? --oren Jon Dahl <jd...@li...> wrote: This may be somewhat off topic since QuickFIX is an open source project, but I was wondering if anyone has switched the socket transport layer with Tibco or something similar? Any pointers would be appreciated. Thanks, Jon Dahl N×­zf¢+,¦ì¢·o! *lx*'ÛM8>·¦êÞ ßz·§qê':§N%°7¯zZ)éíjwH× ­«b¢tzØ^n·vØh|G% iËb¾+ræ빪òߧv¡z)m§ÿðÃ*lyÊ'¢¸?¢ÇgBèø±uëÞ^®ÉX§X¬µ ¢rGâÅׯzZ)z»%Ël²«qç讧zØm¶?þX¬¶Ë(º· ~àzw­þX¬¶ÏåËbú?ªèø±uëÞ^® --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! |
|
From: Rob K. <ro...@ri...> - 2004-01-29 17:12:24
|
I am using C# trying to build an application that can read a FIX message = log and present it in a more readable format in order to debug certin = application level errors. I have used the QuickFix.Message class to = parse simple messages, however any message with repeating groups throws = an invalid message exception. I gather that the problem is that the = Message(string) constructor isn't able to handle parsing repeating = groups unless I somehow attach the Fix spec XML file or use some sort of = specialized parser. Is this possible with QuickFix, or should I look = elsewhere? Is the only option building my own parser? |
|
From: Jon D. <jd...@li...> - 2004-01-28 16:36:12
|
VGhpcyBtYXkgYmUgc29tZXdoYXQgb2ZmIHRvcGljIHNpbmNlIFF1aWNrRklYIGlzIGFuIG9wZW4g c291cmNlIHByb2plY3QsIGJ1dCBJIHdhcyB3b25kZXJpbmcgaWYgYW55b25lIGhhcyBzd2l0Y2hl ZCB0aGUgc29ja2V0IHRyYW5zcG9ydCBsYXllciB3aXRoIFRpYmNvIG9yIHNvbWV0aGluZyBzaW1p bGFyPw0KIA0KQW55IHBvaW50ZXJzIHdvdWxkIGJlIGFwcHJlY2lhdGVkLg0KIA0KVGhhbmtzLA0K IA0KSm9uIERhaGwNCg== |
|
From: H. S. <st...@st...> - 2004-01-26 13:16:38
|
hello, shouldnt QF silently handle invalid fix messages? I've done some tests with invalid body lengths. when receiving such a message, the log shows: "Expected BodyLength=58, Recieved BodyLength=1" Then, an InvalidMessage exception is thrown which crashes the application. I expected that Session::next already catches it. But the exception is re-thrown in the catch() block. I guess such malformed messages should not bother at application level at all. Is that the correct behaviour of QF? Here goes the trace : thread(16384): at process_sleep(Utility.cpp:373) thread(16386):N3FIX14InvalidMessageE: Expected BodyLength=58, Recieved BodyLength=1 at time_gmtime(Utility.cpp:296) at Session::next(Session.cpp:1039) at SocketConnection::read(SocketConnection.cpp:93) at SocketInitiator::onData(SocketInitiator.cpp:147) at ConnectorWrapper::onEvent(SocketConnector.cpp:78) at SocketMonitor::block(SocketMonitor.cpp:161) at SocketConnector::block(SocketConnector.cpp:150) at SocketInitiator::onStart(SocketInitiator.cpp:99) at Initiator::startThread(Initiator.cpp:211) Aborted Thanks for your help, Heri -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. |
|
From: <ili...@bn...> - 2004-01-23 10:24:17
|
Thanks for your answer Oren. Here's a slightly simplified version of my
code. no_allocs & no_misc_fees are the integer values of the fields
NoAllocs and NoMiscFees.
All the other variables are string containing the value of the corresponding FIX field. Please assume that they are initialised correctly within the
first "for" loop.
FIX41::Allocation::NoAllocs groupNoAllocs ;
for (int i=0 ; i < no_allocs ; i++){
if (account.length()>0)
groupNoAllocs.set( FIX::AllocAccount ( account ) );
if (shares.length()>0)
groupNoAllocs.set( FIX::AllocShares ( atoi( shares ) ) );
// and so on and so forth
if (accruedinterestamt.length()>0)
groupNoAllocs.set( FIX::AccruedInterestAmt ( atof( accruedinterestamt) ) );
if (settlinstmode).length()>0)
groupNoAllocs.set( FIX::SettlInstMode ( atoi( settlinstmode ) ) );
if (no_misc_fees > 0) {
FIX41::Allocation::NoAllocs::NoMiscFees groupNoMiscFees ;
for (int k=0; k<no_misc_fees; k++) {
if (miscfeeamt.length()>0)
groupNoMiscFees.set( FIX::MiscFeeAmt ( atof( miscfeeamt ) ) );
if (miscfeecurr.length()>0)
groupNoMiscFees.set( FIX::MiscFeeCurr ( miscfeecurr ) );
if (miscfeetype.length()>0)
groupNoMiscFees.set( FIX::MiscFeeType ( miscfeetype ) );
groupNoAllocs.addGroup(groupNoMiscFees);
}
}
message.addGroup(groupNoAllocs);
}
}
This is the message we send:
8=FIX.4.1
9=781
35=J
34=7
49=FIXTEST
52=20040123-10:03:51
56=TEST
6=16.061700
15=EUR
22=2
48=7118047
53=87850
54=1
55=Official Confirmation to follow
60=20040121-08:21:04
63=6
64=20040126
70=005157150011
71=0
73=1
11=MANUAL
37=00902020
75=20040121
78=2
// 1st Alloc Repeating Group
79=ACCOUNT1 80=87850 76=BROKER1 109=CLIENT1 12=4233.06 13=3 153=16.109885 154=1415253.41 119=1415253.41 120=EUR
136=2
// MiscFee Repeating Groups
137=111 138=EUR 139=1
137=222 138=USD 139=2
// 2nd Alloc Repeating Group
79=ACCOUNT2 80=90000 76=BROKER2 109=CLIENT2 12=8466.06 13=1 153=32.109885 154=1415253.41 119=1415253.41 120=EUR
136=6
// MiscFee Repeating Groups
137=111 138=EUR 139=1 // shouldn't be here
137=222 138=USD 139=2 // shouldn't be here
137=333 138=EUR 139=3
137=444 138=USD 139=4
137=555 138=GBP 139=5
137=666 138=SGD 139=6
107=SUEZ ORD EUR 2 SHS
118=1415253.410000
124=0
10=078
Many thanks,
Ilyas
Internet
OM...@ri... - 22/01/2004 22:36
Pour : Ilias USAL, quickfix-developers
cc :
Objet : RE: [Quickfix-developers] Problem with repeating groups
Can you post the code you are using to create the message as well as the
results from the toString call?
--oren
-----Original Message-----
From: ili...@bn... [mailto:ili...@bn...]
Sent: Thursday, January 22, 2004 11:05 AM
To: qui...@li...
Subject: [Quickfix-developers] Problem with repeating groups
Hello,
I'm getting a strange behaviour when I send a FIX 41 allocation message.
The message contains 2 NoAllocs repeating groups, and each one of those
groups contains 2 NoMiscFees repeating groups.
For instance:
1st NoAlloc repeating group:
136=2
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
2nd NoAlloc repeating group:
136=2
137=3333
138=EUR
139=1
137=4444
138=EUR
139=1
When I send the message, I get:
1st NoAlloc repeating group is correct:
136=2
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
2nd NoAlloc repeating group contains both repeating groups:
136=4
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
137=3333
138=EUR
139=1
137=4444
138=EUR
139=1
I do create the repeating group for each new NoAlloc repeating group
with:
FIX41::Allocation::NoAllocs::NoMiscFees groupNoMiscFees ;
Do you guys know how to solve this?
Many thanks,
Ilyas
This message and any attachments (the "message") is intended solely for
the addressees and is confidential.
If you receive this message in error, please delete it and immediately
notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval.
The internet can not guarantee the integrity of this message. BNP
PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont
etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce message non conforme
a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales)
decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
This message and any attachments (the "message") is intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.
The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
|
|
From: Miller, O. <OM...@ri...> - 2004-01-22 21:36:49
|
SW4gb25seSB1c2VzIHRoZSBDTFIgZm9yIHRoZSAuTkVUIGxpYnJhcnksIHF1aWNrZml4X25ldC5k bGwsIHdoaWNoIGlzIGJ1aWx0IG9uIHRvcCBvZiB0aGUgQysrIGxpYnJhcnkuICBUaGUgY29yZSBs aWJyYXJ5LCBxdWlja2ZpeC5saWIsIGlzIGJ1aWx0IHdpdGggdW5tYW5hZ2VkIGMrKyBldmVuIGlu IFZDNy4NCg0KLS1vcmVuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBKb24g RGFobCBbbWFpbHRvOmpkYWhsQGxpcXVpZGl0eWRpcmVjdC5jb21dIA0KU2VudDogVGh1cnNkYXks IEphbnVhcnkgMjIsIDIwMDQgMTI6NTkgUE0NClRvOiBxdWlja2ZpeC1kZXZlbG9wZXJzQGxpc3Rz LnNvdXJjZWZvcmdlLm5ldA0KU3ViamVjdDogW1F1aWNrZml4LWRldmVsb3BlcnNdIENvbXBpbGlu ZyBWQzYgUHJvamVjdCB3LyAuTkVUDQoNCkkndmUgcmVjZW50bHkgZ290IG15IGhhbmRzIG9uIFZT IC5ORVQgYW5kIGxvb2tlZCBhdCB0aGUgVkM3Lm1hayBmaWxlLiBJIGFtIGFzc3VtaW5nIHRoaXMg aG9va3MgaW4gdGhlIENMUiBpbnRvIHRoZSBRdWlja0ZpeCBsaWJzLg0KIA0KSSB3b3VsZCBsaWtl IHRvIGF2b2lkIHRoYXQgYW5kIGNyZWF0ZSBhbiB1bm1hbmFnZWQgbGliIHVzaW5nIHRoZSBWQzYu bWFrIG9yIHF1aWNrZml4LmRzdyBmaWxlLg0KIA0KSXMgdGhlIHBvc3NpYmxlPw0KIA0KVGhhbmtz LA0KIA0KSm9uIERhaGwNCk4XFNetemYrLOyit28hHCpseConTTg+4aS3DQoNCnrkoLdxJzrnl6dO JTd6WikJandI16BidHpebumTt3ZofEcl4bOKHmli4aW+K3IVBgICdnopAhttDQroipwqbHkn5aai P2dC54GpdeeRrt6WXsmaWFgNCnJHAtevelopeiVs4KyycQ0KDQp6beWktj9Y5qy2KB5+enfkoK1Y D2Llrp0/5beqdeeVr96WXg0K |
|
From: Miller, O. <OM...@ri...> - 2004-01-22 21:36:49
|
Can you post the code you are using to create the message as well as the
results from the toString call?
--oren
-----Original Message-----
From: ili...@bn... [mailto:ili...@bn...]=20
Sent: Thursday, January 22, 2004 11:05 AM
To: qui...@li...
Subject: [Quickfix-developers] Problem with repeating groups
Hello,
I'm getting a strange behaviour when I send a FIX 41 allocation message.
The message contains 2 NoAllocs repeating groups, and each one of those
groups contains 2 NoMiscFees repeating groups.
For instance:
1st NoAlloc repeating group:
136=3D2
137=3D1111
138=3DEUR
139=3D1
137=3D2222
138=3DEUR
139=3D1
2nd NoAlloc repeating group:
136=3D2
137=3D3333
138=3DEUR
139=3D1
137=3D4444
138=3DEUR
139=3D1
When I send the message, I get:
1st NoAlloc repeating group is correct:
136=3D2
137=3D1111
138=3DEUR
139=3D1
137=3D2222
138=3DEUR
139=3D1
2nd NoAlloc repeating group contains both repeating groups:
136=3D4
137=3D1111
138=3DEUR
139=3D1
137=3D2222
138=3DEUR
139=3D1
137=3D3333
138=3DEUR
139=3D1
137=3D4444
138=3DEUR
139=3D1
I do create the repeating group for each new NoAlloc repeating group
with:
FIX41::Allocation::NoAllocs::NoMiscFees groupNoMiscFees ;
Do you guys know how to solve this?
Many thanks,
Ilyas
This message and any attachments (the "message") is intended solely for
the addressees and is confidential.=20
If you receive this message in error, please delete it and immediately
notify the sender. Any use not in accord with=20
its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval.=20
The internet can not guarantee the integrity of this message. BNP
PARIBAS (and its subsidiaries) shall (will) not=20
therefore be liable for the message if modified.=20
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont
etablis a l'intention exclusive de ses=20
destinataires et sont confidentiels. Si vous recevez ce message par
erreur, merci de le detruire et d'en avertir=20
immediatement l'expediteur. Toute utilisation de ce message non conforme
a sa destination, toute diffusion=20
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas=20
d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales)
decline(nt) toute responsabilite au titre de ce=20
message, dans l'hypothese ou il aurait ete modifie.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
|
|
From: Jon D. <jd...@li...> - 2004-01-22 18:59:29
|
SSd2ZSByZWNlbnRseSBnb3QgbXkgaGFuZHMgb24gVlMgLk5FVCBhbmQgbG9va2VkIGF0IHRoZSBW QzcubWFrIGZpbGUuIEkgYW0gYXNzdW1pbmcgdGhpcyBob29rcyBpbiB0aGUgQ0xSIGludG8gdGhl IFF1aWNrRml4IGxpYnMuDQogDQpJIHdvdWxkIGxpa2UgdG8gYXZvaWQgdGhhdCBhbmQgY3JlYXRl IGFuIHVubWFuYWdlZCBsaWIgdXNpbmcgdGhlIFZDNi5tYWsgb3IgcXVpY2tmaXguZHN3IGZpbGUu DQogDQpJcyB0aGUgcG9zc2libGU/DQogDQpUaGFua3MsDQogDQpKb24gRGFobA0K |
|
From: <ili...@bn...> - 2004-01-22 17:04:47
|
Hello,
I'm getting a strange behaviour when I send a FIX 41 allocation message.
The message contains 2 NoAllocs repeating groups, and each one of those
groups contains 2 NoMiscFees repeating groups.
For instance:
1st NoAlloc repeating group:
136=2
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
2nd NoAlloc repeating group:
136=2
137=3333
138=EUR
139=1
137=4444
138=EUR
139=1
When I send the message, I get:
1st NoAlloc repeating group is correct:
136=2
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
2nd NoAlloc repeating group contains both repeating groups:
136=4
137=1111
138=EUR
139=1
137=2222
138=EUR
139=1
137=3333
138=EUR
139=1
137=4444
138=EUR
139=1
I do create the repeating group for each new NoAlloc repeating group with:
FIX41::Allocation::NoAllocs::NoMiscFees groupNoMiscFees ;
Do you guys know how to solve this?
Many thanks,
Ilyas
This message and any attachments (the "message") is intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval.
The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
---------------------------------------------
Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
|
98 messages has been excluded from this view by a project administrator.
