quickfix-developers Mailing List for QuickFIX (Page 131)
Brought to you by:
orenmnero
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
|
| 2026 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andrew C. <And...@Tw...> - 2006-09-28 22:41:12
|
It appears to me no matter what order I put field tags into a repeating group, when I add the group to the message the field tags get sorted in numerical order. I believe this is causing my execution report to be rejected. Is there any way to specify that the group should not be reordered but processed in the way that I added the fields? =20 6971=3D2=01 =20 6972=3D10=016973=3D20060918=016985=3D1=016986=3DEUR=016987=3D1.2739=01698= 8=3DUSD=016989=3D12.74=01 6972=3D10=016973=3D20060925=016985=3D2=016986=3DEUR=016987=3D1.27382=0169= 88=3DUSD=016989=3D12.74 =20 I need (and put the fields into the group in this order) =20 6971=3D2=01 =20 6985=3D1=016986=3DEUR=016972=3D10=016988=3DUSD=016989=3D12.74=016987=3D1.= 2739=016973=3D20060918=01 6985=3D2=016986=3DEUR=016972=3D10=016988=3DUSD=016989=3D12.74=016987=3D1.= 27382=016973=3D20060925 =20 =20 Thanks in advance ! =20 Andrew Culross TwoFour Systems (914) 220-8849 www.TwoFour.Com =20 The views and opinions expressed in this e-mail message are the sender's own and do not necessarily represent the views and opinions of {TwoFour Systems, LLC or F-O-R Software, LLC} =20 |
|
From: Tarandeep S. <tar...@ef...> - 2006-09-28 09:25:40
|
Hi,
I am using quickfix library as initiator in my application. When we send
logon request to the remote server they reply with logon confirmation.
Then they again send us a logon request with ResetSeqNumFlag (141) set
to 'Y' and wait for us to send logon confirmation with 34=1 and 141=Y.
The flow goes something like this.
FIX CLIENT FIX SERVER
============ =============
Send LOGON ------>
<------ Send LOGON 34=1
<------ Send LOGON
34=1 141=Y
Send LOGON ------>
34=1 141=Y
I fixed this problem by sending FIX::Logon message with (141=Y) in
FIX::Application::fromAdmin(const FIX::Message& message, const
FIX::SessionID& sessionID)
throw(FIX::FieldNotFound, FIX::IncorrectDataFormat,
FIX::IncorrectTagValue, FIX::RejectLogon)
1. First I would like to know whether the above mentioned logon protocol
part of standard FIX.
2. If yes, then is there any option to enable this on quickfix library
without applying any patch.
3. If no, how can I read heartbeat interval in my class derived from
FIX::Application as sending FIX::Logon message directly doesn't set tags
heartbeatinterval(108) and EncryptMethod(98) automatically.
Thanks in advance.
Regards,
Tarandeep Singh
|
|
From: Oren M. <or...@qu...> - 2006-09-27 14:57:35
|
There is no guarantee that your session will be logged on immediately
after calling start(). In fact, it is rather unlikely.
How have you confirmed that onLogon is being invoked before you call
isLoggedOn()? Have you also confirmed you were not subsequently
logged off? (Are you monitoring onLogout?)
isLoggedOn and onLogon are intimately related. The code within the
session to invoke onLogon is:
if ( isLoggedOn() )
m_application.onLogon( m_sessionID );
So by definition it is not possible for onLogon to be invoked unless
at some point isLoggedOn returns true.
isLoggedOn will return false if either sentLogon() or recevedLogon()
return false. Can you confirm that either of these return false as
well?
--oren
> In our application, sometimes we get Session.lookupSession
> (sessionID).isLoggedOn() returning false value after calling
> initiator.start(), onLogon(SessionID sessionID) be triggered and
> even receiving heartbeat. Can anyone explain to me what should
> cause this function returning false?
|
|
From: <bre...@am...> - 2006-09-27 14:29:01
|
Hi, In our application, sometimes we get Session.lookupSession(sessionID).isLoggedOn() returning false value after calling initiator.start(), onLogon(SessionID sessionID) be triggered and even receiving heartbeat. Can anyone explain to me what should cause this function returning false? Thanks, Brenda 09/14/2006 04:49 PM Brenda LEI New York Credit Trading Development - CRD IT NY 787 Seventh Ave., 7th floor New York, NY 10019-6016 tel : +1 212 841 3394 To: quickfix-developers cc: Subject: QuickFix Logon Hi, One of our application use QuickFix to connect to Bloomberg fix server. Sometimes, after calling initiator.start(), event onLogon(SessionID sessionID)was trigger, but function initiator.isLoggedOn() still return false. I wonder which is the right way to determine initiator has logged on Fix server successfully. Thanks, Brenda 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. |
|
From: Joerg T. <Joe...@ma...> - 2006-09-27 13:57:48
|
On 09/27/06 11:59, Noha AlAsem wrote:
> i'm new to FIX & QuickFix, my brokerage company connects to the online =
market in=20
> egypt, the online stock market will send the client orders and my compa=
ny=20
> validates these orders and send the responce back to the stock.
> =20
> i need to know how to implement my company's part, i looked up in the e=
xamples=20
> of qiuckfix but i didn't get the whole picture, i use c# to programe th=
is service
Hi Noha,
have a look at the tradeclient and executor examples: The tradeclient con=
nects to the executor which=20
fills every limit order. There are run scripts in the bin dir after you h=
ave built the complete code.
Using this example you can get a first impression how it works.
Cheers, J=F6rg
--=20
Joerg Thoennes
http://macd.com
Tel.: +49 (0)241 44597-24 Macdonald Associates GmbH
Fax : +49 (0)241 44597-10 Lothringer Str. 52, D-52070 Aachen
|
|
From: Noha A. <bun...@ho...> - 2006-09-27 09:59:37
|
<html><div style='background-color:'><DIV class=RTE>Hello everyone,</DIV> <DIV class=RTE> </DIV> <DIV class=RTE>i'm new to FIX & QuickFix, my brokerage company connects to the online market in egypt, the online stock market will send the client orders and my company validates these orders and send the responce back to the stock.</DIV> <DIV class=RTE> </DIV> <DIV class=RTE>i need to know how to implement my company's part, i looked up in the examples of qiuckfix but i didn't get the whole picture, i use c# to programe this service</DIV> <DIV class=RTE> </DIV> <DIV class=RTE>thanks alot</DIV> <DIV class=RTE> </DIV> <DIV class=RTE>noha</DIV></div><br clear=all><hr>FREE pop-up blocking with the new MSN Toolbar <a href="http://g.msn.com/8HMBEN/2752??PS=47575" target="_top">MSN Toolbar</a> Get it now!</html> |
|
From: Eranga S. <pe...@ri...> - 2006-09-26 09:48:37
|
Hi, Quickfix JNI layer was not serializable. So that what is the correct way to copy fix message values to DTO (data transfer object)? I want to send fix message values through network but in fix independent way. My approach is to extract fix values from message and fill a java bean using those values. Is that causing what is the most correct way to address serialization issue? Thanks BR, Eranga |
|
From: Robert P. <rob...@gm...> - 2006-09-25 19:50:02
|
Hi folks,
I'm using the python binding from quickfix 1.12.4, and seeing a
possible bug in the python interface to the Application class. The
platform is CentOS 4.4 (equiv to RHEL 4, update 4).
(1)
Basically in C++, defining the method
FIX::MyApplication::onCreate(const FIX::SessionID& sessionID )
{
cout << sessionID.toString() << endl;
}
works, and prints the session ID as a string when the session is
instantiated, but under python, the code:
class MyApplication(quickfix.Application):
def onCreate(self, sessionID): print "Session ID = " + sessionID
throws an exception when called: "terminate called after throwing an
instance of 'Swig::DirectorMethodException' ". However, calling
sessionID.toString() here instead works.
(2)
In addition, in a very simple application, I'm getting more of these
Swig::DirectorMethodException' errors, and can't seem to determine
the origin.
Below I've included a simple, sample program and the gdb backtrace
from when the program puked. The error occurs in the Initiator.block()
method.
Any ideas on the cause of these errors?
thanks,
rob
-------------------------------------------------------------------
import quickfix
import time, sys
from twisted.python import log
class QuickFIXQuoteClient(quickfix.Application):
def onCreate(self, sessionID):
log.msg("QuickFIXQuoteClient: created. SessionID = "
+sessionID.toString())
def onLogon(self, sessionID): return
def onLogout(self, sessionID): return
def toAdmin(self, message, sessionID):
log.msg("QuickFIXQuoteClient:toAdmin." )
log.msg(" session ID = " + sessionID.toString() )
log.msg(" message = \n"+message.toXML())
def toApp(self, message, sessionID): return
def fromAdmin(self, message, sessionID): return
def fromApp(self, message, sessionID): return
fileName = "config.conf"
settings = quickfix.SessionSettings(fileName)
application = QuickFIXQuoteClient()
storeFactory = quickfix.FileStoreFactory(settings)
logFactory = quickfix.FileLogFactory(settings)
initiator = quickfix.SocketInitiator(application,
storeFactory,settings, logFactory)
initiator.start()
while 1 == 1 :
time.sleep(1)
print "waiting..."
initiator.stop()
------------------------------------------------------
The following is a session from gdb and python2.3
------------------------------------------------------------------
user@host src> gdb python2.3
GNU gdb Red Hat Linux (6.3.0.0-1.132.EL4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...(no debugging
symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) set args -u FIXQuoteClientStub.py
(gdb) r
Starting program: /usr/bin/python2.3 -u FIXQuoteClientStub.py
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208301888 (LWP 19118)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
2006/09/25 15:30 -0400 [-] Log opened.
2006/09/25 15:30 -0400 [-] QuickFIXQuoteClient: created. SessionID =
FIX.4.4:BLAH_TEST->BLAH
[New Thread -1215657040 (LWP 19124)]
2006/09/25 15:33 -0400 [-] QuickFIXQuoteClient:toAdmin.
2006/09/25 15:33 -0400 [-] session ID = FIX.4.4:BLAH_TEST->BLAH
2006/09/25 15:33 -0400 [-] message =
<message>
<header>
<field number="8"><![CDATA[FIX.4.4]]></field>
<field number="35"><![CDATA[A]]></field>
<field number="34"><![CDATA[22]]></field>
<field number="49"><![CDATA[BLAH]]></field>
<field number="52"><![CDATA[20060925-19:33:52.882]]></field>
<field number="56"><![CDATA[BLAH]]></field>
</header>
<body>
<field number="98"><![CDATA[0]]></field>
<field number="108"><![CDATA[20]]></field>
</body>
<trailer>
</trailer>
</message>
terminate called after throwing an instance of 'Swig::DirectorMethodException'
Program received signal SIGABRT, Aborted.
[Switching to Thread -1215657040 (LWP 19124)]
0x007e67a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0 0x007e67a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x008267a5 in raise () from /lib/tls/libc.so.6
#2 0x00828209 in abort () from /lib/tls/libc.so.6
#3 0x00b4a14b in __gnu_cxx::__verbose_terminate_handler () from
/usr/lib/libstdc++.so.6
#4 0x00b47e61 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#5 0x00b47e96 in std::terminate () from /usr/lib/libstdc++.so.6
#6 0x00b47eab in std::terminate () from /usr/lib/libstdc++.so.6
#7 0x00b47da3 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#8 0x004e603d in FIX::Initiator::block (this=Variable "this" is not available.
) at Initiator.cpp:217
#9 0x002616bf in _wrap_Initiator_block (args=0xb796f8cc) at
QuickfixPython.cpp:150095
#10 0x0099a961 in PyCFunction_Call () from /usr/lib/libpython2.3.so.1.0
#11 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#12 0x009cca88 in _PyEval_SliceIndex () from /usr/lib/libpython2.3.so.1.0
#13 0x009cf196 in PyEval_EvalCodeEx () from /usr/lib/libpython2.3.so.1.0
#14 0x009cde89 in _PyEval_SliceIndex () from /usr/lib/libpython2.3.so.1.0
#15 0x009cf196 in PyEval_EvalCodeEx () from /usr/lib/libpython2.3.so.1.0
#16 0x0098ae6e in PyFunction_SetClosure () from /usr/lib/libpython2.3.so.1.0
#17 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#18 0x009c92a0 in PyEval_CallObjectWithKeywords () from
/usr/lib/libpython2.3.so.1.0
#19 0x009f1172 in _PyObject_GC_Del () from /usr/lib/libpython2.3.so.1.0
#20 0x00a67371 in start_thread () from /lib/tls/libpthread.so.0
#21 0x008c6ffe in clone () from /lib/tls/libc.so.6
(gdb)
|
|
From: Robert P. <rob...@gm...> - 2006-09-25 19:32:18
|
Hi folks,
I'm using the python binding from quickfix 1.12.4, and seeing a
possible bug in the python interface to the Application class. The
platform is CentOS 4.4 (equiv to RHEL 4, update 4).
Basically in C++, defining the method
FIX::MyApplication::onCreate(const FIX::SessionID& sessionID )
{
cout << sessionID.toString() << endl;
}
works, and prints the session ID as a string when the session is
instantiated, but under python, the code:
class MyApplication(quickfix.Application):
def onCreate(self, sessionID): print "Session ID = " + sessionID
throws an exception when called: "terminate called after throwing an
instance of 'Swig::DirectorMethodException' ". However, calling
sessionID.toString() here instead works.
In addition,
Is it possible that onCreate is being called before the session is
instantiated in the SWIG interface, or the ?
It should be very easy to reproduce the bug, since all that is needed
it to call
import quickfix
import time, sys
from twisted.python import log
class QuickFIXQuoteClient(quickfix.Application):
def onCreate(self, sessionID):
log.msg("QuickFIXQuoteClient: created. SessionID = " +
sessionID.toString())
def onLogon(self, sessionID): return
def onLogout(self, sessionID): return
# def toAdmin(self, message, sessionID): return
def toAdmin(self, message, sessionID):
log.msg("QuickFIXQuoteClient:toAdmin." )
log.msg(" session ID = " + sessionID.toString() )
log.msg(" message = \n"+message.toXML())
def toApp(self, message, sessionID): return
def fromAdmin(self, message, sessionID): return
def fromApp(self, message, sessionID): return
fileName = "config.conf"
settings = quickfix.SessionSettings(fileName)
application = QuickFIXQuoteClient()
storeFactory = quickfix.FileStoreFactory(settings)
logFactory = quickfix.FileLogFactory(settings)
initiator = quickfix.SocketInitiator(application, storeFactory,
settings, logFactory)
initiator.start()
while 1 == 1 :
time.sleep(1)
print "waiting..."
initiator.stop()
------------------------------------------------------
The following is a stacktrace from gdb python2.3
------------------------------------------------------
terminate called after throwing an instance of 'Swig::DirectorMethodException'
Program received signal SIGABRT, Aborted.
[Switching to Thread -1208904000 (LWP 2747)]
0x007e67a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0 0x007e67a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x008267a5 in raise () from /lib/tls/libc.so.6
#2 0x00828209 in abort () from /lib/tls/libc.so.6
#3 0x00b4a14b in __gnu_cxx::__verbose_terminate_handler () from
/usr/lib/libstdc++.so.6
#4 0x00b47e61 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#5 0x00b47e96 in std::terminate () from /usr/lib/libstdc++.so.6
#6 0x00b47eab in std::terminate () from /usr/lib/libstdc++.so.6
#7 0x00b47da3 in __cxa_call_unexpected () from /usr/lib/libstdc++.so.6
#8 0x0044178a in FIX::SessionFactory::create (this=0xbffcbb30,
sessionID=@0x9e02588, settings=@0x9e17974)
at /usr/lib/gcc/i386-redhat-linux/3.4.6/../../../../include/c++/3.4.6/ext/new_allocator.h:69
#9 0x00456758 in FIX::Initiator::initialize (this=0x9e006c8) at
/usr/lib/gcc/i386-redhat-linux/3.4.6/../../../../include/c++/3.4.6/bits/stl_tree.h:246
#10 0x004575c5 in Initiator (this=0x9e006c8, application=@0x9e03af0,
messageStoreFactory=@0x9de00a0, settings=@0x9c7d5c8,
logFactory=@0x9dfbf38)
at Initiator.cpp:60
#11 0x0045d4d1 in SocketInitiator (this=0x9e006c8,
application=@0x9e03af0, factory=@0x9de00a0, settings=@0x9c7d5c8,
logFactory=@0x9dfbf38)
at SocketInitiator.cpp:49
#12 0x001d177d in _wrap_new_SocketInitiatorBase (self=0x0,
args=0xb78d384c) at QuickfixPython.cpp:150717
#13 0x0099a961 in PyCFunction_Call () from /usr/lib/libpython2.3.so.1.0
#14 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#15 0x009cca88 in _PyEval_SliceIndex () from /usr/lib/libpython2.3.so.1.0
#16 0x009cf196 in PyEval_EvalCodeEx () from /usr/lib/libpython2.3.so.1.0
#17 0x0098ae6e in PyFunction_SetClosure () from /usr/lib/libpython2.3.so.1.0
#18 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#19 0x0097edc8 in PyMethod_New () from /usr/lib/libpython2.3.so.1.0
#20 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#21 0x009ccc6f in _PyEval_SliceIndex () from /usr/lib/libpython2.3.so.1.0
#22 0x009cf196 in PyEval_EvalCodeEx () from /usr/lib/libpython2.3.so.1.0
#23 0x0098ae6e in PyFunction_SetClosure () from /usr/lib/libpython2.3.so.1.0
#24 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#25 0x0097edc8 in PyMethod_New () from /usr/lib/libpython2.3.so.1.0
#26 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#27 0x009af93c in _PyObject_SlotCompare () from /usr/lib/libpython2.3.so.1.0
#28 0x009a8d1c in PyType_IsSubtype () from /usr/lib/libpython2.3.so.1.0
#29 0x00977637 in PyObject_Call () from /usr/lib/libpython2.3.so.1.0
#30 0x009ccc6f in _PyEval_SliceIndex () from /usr/lib/libpython2.3.so.1.0
#31 0x009cf196 in PyEval_EvalCodeEx () from /usr/lib/libpython2.3.so.1.0
#32 0x009cf45d in PyEval_EvalCode () from /usr/lib/libpython2.3.so.1.0
#33 0x009e8917 in PyErr_Display () from /usr/lib/libpython2.3.so.1.0
#34 0x009e9a42 in PyRun_SimpleFileExFlags () from /usr/lib/libpython2.3.so.1.0
#35 0x009eaa94 in PyRun_AnyFileExFlags () from /usr/lib/libpython2.3.so.1.0
#36 0x009ef78e in Py_Main () from /usr/lib/libpython2.3.so.1.0
#37 0x080485b2 in main ()
|
|
From: Alexey Z. <ale...@gm...> - 2006-09-25 13:32:10
|
Hello,
I have several similar projects too. They work great.
The only problem I had is that all target names must be unique - the map
of sessions is static.
Another thing is that in some environments (VC6, Win2K) there are
exceptions during debugging when ThreadedSocketInitiator is in use.
Regards,
Alexey.
>
> There is no problem doing this. We have implemented a similar design
> ourselves on several projects.
>
> --oren
>
>
>> When these are all run inside one .exe can this cause a problem in
>> QuickFix? Do we need to only have one SocketInitiator object that
>> manages all our sessions?
>>
>> Just trying to look down the road ahead for any sharp turns ;-)
>>
>
|
|
From: Oren M. <or...@qu...> - 2006-09-23 04:52:24
|
Thanks, the patch has been commited to svn. The readon there isn't a binary build for windows is because the generated file is too large to compile under Visual Studio. We are working on reducing its size so hopefully we can build the ruby and python APIs in windows. --oren > We've been playing around with the Ruby API for QuickFIX and it looks > great. Is there any reason why it is not included in the binary build of > QuickFIX for Windows? Thanks. >=20 > As a bonus, I found a small typo, and attached a patch to this bug: |
|
From: Graham M. <gm...@ma...> - 2006-09-23 00:01:22
|
Hello all, We've been playing around with the Ruby API for QuickFIX and it looks great. Is there any reason why it is not included in the binary build of QuickFIX for Windows? Thanks. As a bonus, I found a small typo, and attached a patch to this bug: http://www.quickfixengine.org/bugtracker/bug.php?op=show&bugid=207&pos=0 graham -- Marketcetera Trading Platform download.run.trade. www.marketcetera.org |
|
From: Francis G. <fr...@at...> - 2006-09-22 23:13:13
|
Hi, When HttpAcceptPort is set to port 8080 in the default section of the config, QuickFix ThreadedInitiator.NET 1.12.4 will crash after about an hour of Start()-Stop() calls. QuickFix.RuntimeError: "Runtime error: Unable to create, bind, or listen to port 8080" at QuickFix.ThreadedSocketInitiator.start() If I disable this setting then QF does not crash. I have tried on two separate computers with different configurations and got the same result. Does anyone else have the same issue? Thanks, Francis |
|
From: Oren M. <or...@qu...> - 2006-09-22 20:45:06
|
There is no problem doing this. We have implemented a similar design ourselves on several projects. --oren > When these are all run inside one .exe can this cause a problem in=20 > QuickFix? Do we need to only have one SocketInitiator object that=20 > manages all our sessions? >=20 > Just trying to look down the road ahead for any sharp turns ;-) |
|
From: Tim B. <tim...@bl...> - 2006-09-22 20:12:39
|
Hi, We have code to handle several exchange connections and each do a SocketInitiator.start() to get their session going. Right now each of our exchanges is a separate dll as is quickfix (modified in-house with various classes exported). The exchanges currently don't know anything about each other and can each run totally independently. When these are all run inside one .exe can this cause a problem in QuickFix? Do we need to only have one SocketInitiator object that manages all our sessions? Just trying to look down the road ahead for any sharp turns ;-) Thanks ... thnx, tcb |
|
From: Oren M. <or...@qu...> - 2006-09-21 18:01:50
|
The testing tool is independent of any particular API. It was designed to test QuickFIX, so it is necessarily is not dependent on QuickFIX. The tool itself is implemented in Ruby, so it will run on any platform that has a ruby interpreter, which is just about all of them at this point. The ruby scripts themselves are located in the quickfix/test directory. The starting script is Runner.rb, and it is loaded as such: ruby Runner.rb [ADDRESS] [PORT] tests The currently available test runner acts as an initiator which can be used to test against any engine that acts as an acceptor. We have an updated version we will be making available which can simultaneously act as an acceptor. It will also have improvements to the testing langage which will make it easier to write tests. --oren > Ultimately I would like use this tool to create my own test cases > (initiated and expected messages) and connect this engine to my own > engine for testing of my own engine. I am unable to locate where this > engine is, how I would create test cases, how I specify the > configuration (e.g. what ip/port to connect to), etc. I have > successfully built quickfix and run the ruby runat program to verify my > install. I would prefer to use the C/C++ version of quickfix but I am > open to the Java version if that is the only one that has this > acceptance test tool. >=20 > Any guidance is greatly appreciated. |
|
From: Stephen C. <Ste...@mi...> - 2006-09-21 15:26:56
|
All, I have read over the documentation and tried to look thru the source for information on how to use the acceptance tests described at: http://www.quickfixengine.org/quickfix/doc/html/acceptance_tests.html. Ultimately I would like use this tool to create my own test cases (initiated and expected messages) and connect this engine to my own engine for testing of my own engine. I am unable to locate where this engine is, how I would create test cases, how I specify the configuration (e.g. what ip/port to connect to), etc. I have successfully built quickfix and run the ruby runat program to verify my install. I would prefer to use the C/C++ version of quickfix but I am open to the Java version if that is the only one that has this acceptance test tool. Any guidance is greatly appreciated. Thanks, Steve Stephen Cooper Vice President Miletus Trading, LLC www.miletustrading.com <http://www.mi...@mi...>=20 ---------- This e-mail message and its attachments are confidential, intended only = for the addressee(s) named above and may contain information that is = proprietary, privileged, or otherwise exempt from disclosure. If you = receive this message in error please notify us at = pos...@mi... and immediately delete this message and = its attachments from your system. Miletus Trading, LLC is not responsible for any recommendation, = solicitation, offer or agreement or any information about any = transaction, customer account or account activity contained in this = communication. |
|
From: Oren M. <or...@qu...> - 2006-09-20 22:44:14
|
There were definately some socket issues in previous 1.12.x versions fixed in subsequent releases. I could see some of them causing potentially bizaare behavior. We should see how things work when you get your system up on the latest version before spending too much time on this issue. --oren > I agree. But on the same note, the 1.11.0 binaries work fine and the same 1.12.1 binaries work well on=20 > other QA servers where there aren't nearly as many connections established. Is there anything that happens=20 > with the non-blocking sockets at connect time that may be behaving badly? |
|
From: Oren M. <or...@qu...> - 2006-09-20 22:41:11
|
I suspect this may have to do with attempting to use one of the gcc allocators in a stlport collection. I've checked in an update which should prevent this. --oren > Linux 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 i386 GNU/Linux > gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-52) > stlport 4.6.2 > pgsql 7.4.6 |
|
From: Sean K. <sea...@pi...> - 2006-09-20 20:46:20
|
Sure. Linux 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 = i386 GNU/Linux gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-52) stlport 4.6.2 pgsql 7.4.6 > -----Original Message----- > From: Oren Miller [mailto:or...@qu...] > Sent: Wednesday, September 20, 2006 4:29 PM > To: Sean Kirkpatrick > Cc: qui...@li... > Subject: Re: [Quickfix-developers] 1.12.4 link error >=20 >=20 > Can you post what version of linux, gcc, stlport, and pgsql you are > using? >=20 > --oren >=20 > > /bootstrap > > /configure --with-stlport=3D/usr/local --disable-callstack > --with-postgresql=3D/usr/local/pgsql > > make >=20 Disclaimer: Any references to Pipeline performance contained herein are = based on historic performance levels which Pipeline expects to maintain = or exceed but nevertheless does not guarantee. Congested networks, price = volatility, or other extraordinary events may impede future trading = activities and degrade performance statistics. |
|
From: Oren M. <or...@qu...> - 2006-09-20 20:29:06
|
Can you post what version of linux, gcc, stlport, and pgsql you are using? --oren > /bootstrap > /configure --with-stlport=3D/usr/local --disable-callstack --with-postgresql=3D/usr/local/pgsql > make |
|
From: Sean K. <sea...@pi...> - 2006-09-20 15:45:43
|
I agree. But on the same note, the 1.11.0 binaries work fine and the = same 1.12.1 binaries work well on other QA servers where there aren't = nearly as many connections established. Is there anything that happens = with the non-blocking sockets at connect time that may be behaving = badly? --Sean > -----Original Message----- > From: Oren Miller [mailto:or...@qu...] > Sent: Wednesday, September 20, 2006 11:40 AM > To: Sean Kirkpatrick > Cc: qui...@li... > Subject: Re: [Quickfix-developers] QF 1.12.1 crash >=20 >=20 > Something looks very wrong here. How is it that > FIX::SocketAcceptor::onConnect is located in stl/_ostream.h? >=20 > --oren >=20 > > I'm having an issue with a server I recently ugraded to 1.12.1. It > appears that when multiple clients are=20 > > logging on the crash occurs. Here is the stack trace: >=20 > > #8 0x008e2f91 in FIX::SocketAcceptor::onConnect (this=3D0x9292038, > server=3D@0x96e8970, a=3D11, s=3D18) > > at /usr/local/include/stlport/stl/_ostream.h:300 >=20 Disclaimer: Any references to Pipeline performance contained herein are = based on historic performance levels which Pipeline expects to maintain = or exceed but nevertheless does not guarantee. Congested networks, price = volatility, or other extraordinary events may impede future trading = activities and degrade performance statistics. |
|
From: Sean K. <sea...@pi...> - 2006-09-20 15:45:04
|
/bootstrap /configure --with-stlport=3D/usr/local --disable-callstack = --with-postgresql=3D/usr/local/pgsql make > -----Original Message----- > From: Oren Miller [mailto:or...@qu...] > Sent: Wednesday, September 20, 2006 11:43 AM > To: Sean Kirkpatrick > Cc: qui...@li... > Subject: Re: [Quickfix-developers] 1.12.4 link error >=20 >=20 > You are getting this when you do a ./configure && make? >=20 > --oren >=20 > > I'm trying to drop in 1.12.4 to my test environment, but at=20 > link time > I'm getting a bunch of undefined=20 > > references. Has something changed that would cause these errors? >=20 Disclaimer: Any references to Pipeline performance contained herein are = based on historic performance levels which Pipeline expects to maintain = or exceed but nevertheless does not guarantee. Congested networks, price = volatility, or other extraordinary events may impede future trading = activities and degrade performance statistics. |
|
From: Oren M. <or...@qu...> - 2006-09-20 15:42:58
|
You are getting this when you do a ./configure && make? --oren > I'm trying to drop in 1.12.4 to my test environment, but at link time I'm getting a bunch of undefined=20 > references. Has something changed that would cause these errors? |
|
From: Oren M. <or...@qu...> - 2006-09-20 15:39:41
|
Something looks very wrong here. How is it that =46IX::SocketAcceptor::onConnect is located in stl/_ostream.h? --oren > I'm having an issue with a server I recently ugraded to 1.12.1. It appears that when multiple clients are=20 > logging on the crash occurs. Here is the stack trace: > #8 0x008e2f91 in FIX::SocketAcceptor::onConnect (this=3D0x9292038, server=3D@0x96e8970, a=3D11, s=3D18) > at /usr/local/include/stlport/stl/_ostream.h:300 |