quickfix-developers Mailing List for QuickFIX (Page 286)
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
|
From: Alexandre H. <a....@ca...> - 2003-04-01 15:35:09
|
Hello, I archive the FIX messages I receive through QuickFIX in an SQL Server database. Basically, if I receive a quote request, encapsulated in an object of = class "QuoteRequest", I do: "aQuoteRequest.toString()" and I put the string in the database. Now I want to retrieve from my database the quote request. So I first = use a query to get the string I have just stored. Then a can create a Message: Message aMessage =3D new Message(stringRetrievedFromDB); But then, I cannot do the following:=20 Symbol aSymbol =3D new Symbol(); aMessage.get(aSymbol); // does not work ! I actually need to cast to the "Message" to "org.quickfix.fix42.QuoteRequest".=20 But this is not possible: I get a class cast exception. Is there a way to do this casting ? Or is there a better way to archive messages ? I have thought of = archiving the tags one by one, but doing with makes it more difficult to = reconstruct an object of class "Message". Thanks for any idea, Alexandre -----Message d'origine----- De : qui...@li... [mailto:qui...@li...] Envoy=E9 : vendredi 28 mars 2003 21:35 =C0 : qui...@li... Objet : Quickfix-developers digest, Vol 1 #193 - 5 msgs Send Quickfix-developers mailing list submissions to qui...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/quickfix-developers or, via email, send a message with subject or body 'help' to qui...@li... You can reach the person managing the list at qui...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Quickfix-developers digest..." Today's Topics: 1. COM Error when trying to initialize acceptor (Jacob Steyn) 2. RE: COM Error when trying to initialize acceptor (Jacob Steyn) 3. Re: COM Error when trying to initialize acceptor (Vitor Castro) 4. SessionNotFound Exception sending messages in Java (David = Monheit) 5. Message storage and retrieval (David Monheit) --__--__-- Message: 1 Date: Fri, 28 Mar 2003 10:58:53 +0200 From: "Jacob Steyn" <ja...@pe...> To: <qui...@li...> Subject: [Quickfix-developers] COM Error when trying to initialize = acceptor HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in =3D quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac --__--__-- Message: 2 Subject: RE: [Quickfix-developers] COM Error when trying to initialize acceptor Date: Fri, 28 Mar 2003 12:23:24 +0200 From: "Jacob Steyn" <ja...@pe...> To: "Vitor Castro" <vc...@hi...>, <qui...@li...> Hi Vitor Thanks. Im not trying to expose them. Using the default quickfix_net_debug.dll in 1.4.0 and just referencing it in my .net solution which doesnt register in COM. -----Original Message----- From: Vitor Castro [mailto:vc...@hi...] Sent: 28 March 2003 11:27 To: Jacob Steyn; qui...@li... Subject: RE: [Quickfix-developers] COM Error when trying to initialize acceptor Hi Jac, Are you trying to expose the objects in quickfix_net_debug.dll as COM objects? If not check to see if your quickfix .net project isn't by mistake enabling the registration of the dll as a COM server. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Jacob Steyn Sent: sexta-feira, 28 de Mar=3DE7o de 2003 8:59 To: qui...@li... Subject: [Quickfix-developers] COM Error when trying to initialize acceptor HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers --__--__-- Message: 3 From: "Vitor Castro" <vc...@hi...> Cc: <qui...@li...> Subject: Re: [Quickfix-developers] COM Error when trying to initialize acceptor Date: Fri, 28 Mar 2003 10:18:20 -0000 Organization: HiperBit Hi Jac, Are you trying to expose the objects in quickfix_net_debug.dll as COM objects? If not check to see if your quickfix .net project isn't by mistake enabling the registration of the dll as a COM server. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Jacob Steyn Sent: sexta-feira, 28 de Mar=3DE7o de 2003 8:59 To: qui...@li... Subject: [Quickfix-developers] COM Error when trying to initialize acceptor HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers --__--__-- Message: 4 Date: Fri, 28 Mar 2003 14:47:47 +0000 From: David Monheit <Dav...@mo...> Reply-To: Dav...@mo... Organization: Morgan Stanley To: qui...@li... Subject: [Quickfix-developers] SessionNotFound Exception sending = messages in Java Hi all, Coming along in QF. I saw some old threads which experienced this = exact problem, ie, QF for Java has some problem finding the right session.=20 Here is the scoop: There are 3 overrides to Session.sendToTarget a) sendToTarget(Message) b) sendToTarget(Message, SessionID) c) sendToTarget(Message, SenderCompID (string), SenderTargetID = (string)) It turns out that no matter what I tried with c, I ALWAYS got SessionNotFound!!! I also noticed that if I set the following in the cfg file: SenderCompID=3DOrderEngine TargetCompID=3Dmonheit I got back a sessionID of "FIX.4.0:OrderEngine->monheit" on the C++ program, ie, executor. When I ran my order entry program in Java with = a cfg of: SenderCompID=3Dmonheit TargetCompID=3DOrderEngine the sessionID was "FIX.4.0: monheit->OrderEngine" !!! Note the space = in there!!!! The way I got it to work is by using override b, and sending the SessionID which I got on the order... I did not try method a yet. Need to have a look at why this is. Regards David --__--__-- Message: 5 Date: Fri, 28 Mar 2003 15:06:53 +0000 From: David Monheit <Dav...@mo...> Reply-To: Dav...@mo... Organization: Morgan Stanley To: Quickfix <qui...@li...> Subject: [Quickfix-developers] Message storage and retrieval Hi Starting the debate of earlier threads again... IMHO a client app could either try to keep the state of the world (SOW) itself of delegate it to something else which then uses different methods for dispersing this info. A client app could go to a db to get known orders and status on startup, connect to a pub/sub system and request the current SOW or whatever. A server, however, specially something like an order manager must keep track of its orders EVEN through a core !!! As Oren mentioned in some earlier thread, this presents a problem. Server which handle large order flow will have a huge FIX traffic whose latency needs to be kept to a minimum. Writing orders to a db or whatever is basically out of the quesion because of the IO time involved. Since QF does have the logs stored if the file system one would imagine that re-loading the order server to the state prior to a core is just a matter of replaying the messages and rebuiding the order collection. This however, is a server problem, not a qf problem. I would vote for writing a small library for reading and even better, replaying these messages. For instance we could create a MessageReplayApplication = which subclasses Application. This classes' thread would read the inbound = log file and invoke fromApp callbacks. Any messages sent by this app would be ignored!!!! This would allow a server to rebuild its state. When done, the main class deletes this playback object and start the real one.... Just a thought anyways. The point is that for some apps we DO need to have not just message recovery but state recovery as well... David -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. --__--__-- _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers End of Quickfix-developers Digest * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * = * *=20 Confidentiality Notice :=20 The information contained in this e-mail message is intended only for = the personal and confidential use of the recipient(s) named above. If the = reader of this message is not the intended recipient or an agent responsible = for delivering it to the intended recipient, you are hereby notified that = you have received this document in error and that any review, = dissemination, distribution, or copying of this message is strictly prohibited. If you = have received this communication in error, please notify = pos...@ca... immediately by e-mail, and delete the original message. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * = * *=20 |
From: David M. <Dav...@mo...> - 2003-04-01 09:01:59
|
Hi Thanks for the replies. Yes, quickfix passes the acceptance test (but not in the multithreaded version!!!). I am getting further on the problem as I now can replicate it easily with a little sample JNI app (nothing to do with quickfix). That is a bit reassuring. As Oren points out, I was using gcc2.95.3 but on linux Redhat 7.3 (which uses gcc 2.96 for everything). I found this problem discussed extensively on the gnu gcc bug list. I am now building gcc 3.2 and will keep you all posted. Thanks for the help David Gene Gorokhovsky wrote: > David, does quickfix pass its own acceptance tests > (build and run in quickfix/test)? > I have found that on Linux there could be subtle > misconfiguartions of the build tools, compiler and > libraries which results in the symptoms similar to > what you describe. > Passing all of the acceptance tests was a good > indication that I found a stable configuration. As a > ray of hope, my company has beedn devloping on > quickfix in both C++ and Java API's on Linux for the > past half a year or so and found it to be generally > stable. > > Gene > > --- David Monheit <Dav...@mo...> > wrote: > > Hi All, > > > > Finally made some progress... I got a server > > program, ie, acceptor > > based appliation, runnig... As I mentioned on my > > last mail, only got it > > to send messages by using sendToTarget(Message, > > SessionID). > > > > When I started working on the client app, initiator > > based application, > > all hell broke loose :-) Basically, it turns out > > that NO application > > works, as it simply aborts (on my home linux box, > > without a core. In the > > office, thankfully, it does core, see listing > > below). Banzai also does > > not work (I see the gui pop up briefly and then it > > dies). > > > > After several hours yesterday, I was able to show > > that if the quickfix > > library throws ANY exception, the app dies. > > Basically this happened > > when I did not set the ReconnectInterval in the > > config file. The docs > > say that this field is defaulted to 30 (and I see > > this from the > > constructors which do set this to 30). The > > onInitialize tries to get > > this value from the dictionary and if it does get > > it, it overrides the > > 30 default. If it does not find it, it catches the > > exception and > > continues!!! THIS CAUSES THE APP TO DIE. Seems > > that someone does not > > like any exceptions thrown even if they are caught. > > > > To prove this, I commented the line out and the code > > then cored > > elsewhere (on getHost() where the code tries to get > > the host with a > > number attached (ie SocketConnectionHost0 ). If it > > does not find it, it > > uses the standard on, ie, SocketConnectionHost ... > > But again, the fact > > that an exception was thrown, blows the program... > > > > Here is the listing of the stack when > > ReconnectInterval is not set... > > > > #0 0x40076b41 in __kill () at __kill:-1 > > -1 __kill: No such file or directory. > > in __kill > > (gdb) where > > #0 0x40076b41 in __kill () at __kill:-1 > > #1 0x4003879b in raise (sig=6) at signals.c:65 > > #2 0x400780c2 in abort () at > > ../sysdeps/generic/abort.c:88 > > #3 0x4035c0a2 in os::abort () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #4 0x403590ac in os::handle_unexpected_exception () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #5 0x4035cb2a in JVM_handle_linux_signal () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #6 0x4035b844 in signalHandler () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #7 0x40038b53 in pthread_sighandler_rt (signo=11, > > si=0xbfe0dc90, > > uc=0xbfe0dd10) at signals.c:121 > > #8 <signal handler called> > > #9 0x4060cd3a in __cplus_type_matcher > > (info=0x8297ef0, > > match_info=0x4c939f54 <FIX::ConfigError > > type_info function>, > > exception_table=0x0) > > from /usr/lib/libstdc++-libc6.1-1.so.2 > > #10 0x4cb6a3bc in __eh_rtime_match > > (rtime=0x4c939f54) > > from > > > /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so > > #11 0x4c9050be in FIX::SocketInitiator::getHost () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #12 0x4c9046f8 in FIX::SocketInitiator::doConnect () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #13 0x4c902428 in FIX::Initiator::connect () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #14 0x4c904653 in FIX::SocketInitiator::onStart () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #15 0x4c9026b6 in FIX::Initiator::start () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #16 0x4c8efb0d in > > Java_org_quickfix_SocketInitiator_doStart () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #17 0x4207412d in ?? () > > #18 0x4206cf93 in ?? () > > #19 0x4206d299 in ?? () > > #20 0x4206cf93 in ?? () > > #21 0x4206a195 in ?? () > > #22 0x402c04f6 in JavaCalls::call_helper () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #23 0x4035b44d in os::os_exception_wrapper () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #24 0x402c0644 in JavaCalls::call () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #25 0x402c85cd in jni_invoke () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #26 0x402d7bcd in jni_CallStaticVoidMethod () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #27 0x08049372 in strcpy () at strcpy:-1 > > #28 0x40064687 in __libc_start_main (main=0x8048c60 > > <strcpy+200>, > > argc=5, ubp_av=0xbffeb054, > > init=0x80488e8, fini=0x804ba0c <strcpy+11892>, > > rtld_fini=0x4000dcd4 > > <_dl_fini>, stack_end=0xbffeb04c) > > > > Here is the listing if I do set ReconnectInterval > > ... > > > > #0 0x40076b41 in __kill () at __kill:-1 > > #1 0x4003879b in raise (sig=6) at signals.c:65 > > #2 0x400780c2 in abort () at > > ../sysdeps/generic/abort.c:88 > > #3 0x4035c0a2 in os::abort () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #4 0x403590ac in os::handle_unexpected_exception () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #5 0x4035cb2a in JVM_handle_linux_signal () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #6 0x4035b844 in signalHandler () > > from > > > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > > > #7 0x40038b53 in pthread_sighandler_rt (signo=11, > > si=0xbfe0dc90, > > uc=0xbfe0dd10) at signals.c:121 > > #8 <signal handler called> > > #9 0x4060cd3a in __cplus_type_matcher > > (info=0x82917a0, > > match_info=0x4060d2c4 <exception type_info > > function>, > > exception_table=0x0) > > from /usr/lib/libstdc++-libc6.1-1.so.2 > > #10 0x4cb6a3bc in __eh_rtime_match > > (rtime=0x4060d2c4) > > from > > > /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so > > #11 0x4c904581 in FIX::SocketInitiator::onInitialize > > () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #12 0x4c9025d2 in FIX::Initiator::start () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #13 0x4c8efb0d in > > Java_org_quickfix_SocketInitiator_doStart () > > from > > > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > > > #14 0x4207412d in ?? () > > #15 0x4206cf93 in ?? () > > #16 0x4206d299 in ?? () > > > === message truncated === > > __________________________________________________ > Do you Yahoo!? > Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! > http://platinum.yahoo.com > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. |
From: Joerg T. <Joe...@ma...> - 2003-04-01 07:34:42
|
Hi Barry, > [...] > The production machine is a very fast dual processor sun box and the > application failed on the initial download of SecurityStatus messages which > proceeds very quickly until the crash. > > Is there a known problem using quickfix on a multi-processor machine? You can check this easily using the Solaris pbind command. First, check the number of processors using psrinfo: $ psrinfo 0 on-line since 10/31/02 15:54:39 ... And then you can specify $ pbind -b 0 <pids> Since bindings are inherited to all created LWPs and processes, using $ pbind -b 0 $$ you bind the current shell and all processes started by that shell. Of course, this is only a fast check (and hopefully workaround), but does not solve the problem. Oren already gave you some hints to solve your problem. Good luck! Jörg > [...] -- 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: Nicholas P. <nic...@sl...> - 2003-04-01 00:31:55
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey All, I am having some trouble with a QuickFIX application I am developing. Unfortunately it requires that I interface with a vendor who uses a bastardized version of FIX. I have created a special XML file for validation of these messages, and two out of the three I have to handle get received and cracked properly. The third doesn't seem to get into the application at all. I have overridden both fromAdmin and fromApp and put logging statements in both. For the other messages I see the log message in fromAdmin, and then fromApp, however for this message I see the log of the message being received that looks like: <20030401-00:11:05, FIX.4.2:US->THEM, incoming> (field=data*field=data*etc...) but neither the fromAdmin or fromApp methods get called, and no other message is logged (such as rejecting due to missing or invalid fields which I have seen when I had the XML messed up, so I don't think that is the problem, but I guess it is possible. I have been over the XML with a fine toothed comb though so I doubt it.) The application then goes into an infinite loop where QuickFIX claims that the next message had a sequence number that was too high and re requests the message that it just dropped, which it drops again. Lather rinse repeat until the processor explodes. The message that I receive contains fields out of order, and fields which print with fieldnum=NOREF, so I suspect it is a problem handling the crappy message from the other vendor, but since QuickFIX receives it they claim that it is my problem to fix. I have set: ValidateFieldsOutOfOrder=N ValidateFieldsHaveValues=N in the config file with no change in behavior. Any thoughts on a cure for this problem. Thanks, - -Nick -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+iN3hR42/Somtp0QRArTAAJwLsxraN8FpGlAnH3AJsJP/wl9UoQCggqIV IzUOnThR+n1roiPuSAgmBvE= =fJKZ -----END PGP SIGNATURE----- |
From: Oren M. <ore...@ya...> - 2003-03-31 22:29:35
|
It is a very bad order entry application. Very bad because no one would actually use it because of the horrible interface. What it allows you to do is send an order to a destination, and then displays the execution (as a pure fix message). You can use it to connect to either the ordermatcher or executor sample projects. Vamsi Krishna <Vam...@ib...> wrote: Can somebody explain in simple words,what is the purpose of example tradeclient. What it does exactly? Vamsi -----Original Message----- From: Oren Miller [mailto:ore...@ya...] Sent: Monday, March 31, 2003 3:58 PM To: Vamsi Krishna; 'Quickfix' Subject: Re: [Quickfix-developers] DEBUG ASSERTION FAILURE at_client really should be removed from the projects. It's not actually used and don't think that it is up to date. I would recommend looking at the projects under the examples directory instead. Vamsi Krishna <Vam...@ib...> wrote: Hi all I am trying to invoke the at_client exe with a config file. I am getting the below error DEBUG ASSERTION FAILURE program dbgheap.c _block_type_is_valid(phead->nblockuse) its an assertion failure.. Did anybody get this problem. I would appreciate if somebody gives solution for this Thanks Krishna ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: CW J. <jav...@ce...> - 2003-03-31 21:42:33
|
Hi Vamsi- It may be worth looking thru the mailing list archives, and taking a peek at the documentation, here: Mailing List Archives: http://quickfix.thoughtworks.com/mailinglists.html Installing QuickFIX: http://quickfix.thoughtworks.com/documentation/install.html Yet More Documentation: http://quickfix.thoughtworks.com/documentation/index.html HTH, Cedrick |
From: Vamsi K. <Vam...@ib...> - 2003-03-31 21:29:42
|
Can somebody explain in simple words,what is the purpose of example tradeclient. What it does exactly? Vamsi -----Original Message----- From: Oren Miller [mailto:ore...@ya...] Sent: Monday, March 31, 2003 3:58 PM To: Vamsi Krishna; 'Quickfix' Subject: Re: [Quickfix-developers] DEBUG ASSERTION FAILURE at_client really should be removed from the projects. It's not actually used and don't think that it is up to date. I would recommend looking at the projects under the examples directory instead. Vamsi Krishna <Vam...@ib...> wrote: Hi all I am trying to invoke the at_client exe with a config file. I am getting the below error DEBUG ASSERTION FAILURE program dbgheap.c _block_type_is_valid(phead->nblockuse) its an assertion failure.. Did anybody get this problem. I would appreciate if somebody gives solution for this Thanks Krishna ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers _____ Do you Yahoo!? Yahoo! <http://rd.yahoo.com/platinum/evt=8162/*http:/platinum.yahoo.com/splash. html> Platinum - Watch CBS' NCAA March Madness, live <http://rd.yahoo.com/platinum/evt=8162/*http:/platinum.yahoo.com/splash. html> on your desktop! |
From: Vamsi K. <Vam...@ib...> - 2003-03-31 21:14:04
|
Hi Is there any documentation for Tradeclient example. Thanks krishna -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Oren Miller Sent: Monday, March 31, 2003 3:58 PM To: Vamsi Krishna; 'Quickfix' Subject: Re: [Quickfix-developers] DEBUG ASSERTION FAILURE at_client really should be removed from the projects. It's not actually used and don't think that it is up to date. I would recommend looking at the projects under the examples directory instead. Vamsi Krishna <Vam...@ib...> wrote: Hi all I am trying to invoke the at_client exe with a config file. I am getting the below error DEBUG ASSERTION FAILURE program dbgheap.c _block_type_is_valid(phead->nblockuse) its an assertion failure.. Did anybody get this problem. I would appreciate if somebody gives solution for this Thanks Krishna ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers _____ Do you Yahoo!? Yahoo! <http://rd.yahoo.com/platinum/evt=8162/*http:/platinum.yahoo.com/splash. html> Platinum - Watch CBS' NCAA March Madness, live <http://rd.yahoo.com/platinum/evt=8162/*http:/platinum.yahoo.com/splash. html> on your desktop! |
From: Oren M. <ore...@ya...> - 2003-03-31 21:11:11
|
There is indeed a known problem with using quickfix on a multiprocessor machine. This is actually a bug with the implementation of STL that is distributed with some versions of gcc. The easiest way to fix this is to install STLPort and configure quickfix with the --stlport option. (or if not using the configure script, put it in your include path) I have encountered the problem you have seen with creating the shared library as well. I can go over some steps you can take for that, but you should probably try building 1.3.2 with stlport first. "Bishop, Barry" <Bar...@gs...> wrote:Hi, I've been developing an application using quickfix 1.3.2 and java running on solaris. I never managed to get the build working correctly and resorted to compiling every source file and linking them into one huge shared object library. Everything seemed to be fine all the way through development and testing until the application was released in to production whereupon it failed after a few seconds with a 'Problem has occured in a thread outside the JVM...' error. The production machine is a very fast dual processor sun box and the application failed on the initial download of SecurityStatus messages which proceeds very quickly until the crash. Is there a known problem using quickfix on a multi-processor machine? I noticed that quickfix 1.4.0 contains a fix for a 'race condition' and so decided to give it a go. However, even though I managed to get configure to work (without the libxml test) the build still doesn't give me a working shared object library. It warns me when linking libquickfix_jni.so that it has not linked to libquickfix as a shared version is not available. Is it possible to make a shared version of this library? Sure enough, the library fails to load in to the JVM. I've resorted to using my old build script which worked with quickfix 1.3.2, but this leads relocation errors at load time (__eh_alloc or __builtin_vec_new or others depending on my tweaks to my build script). I'm pretty desperate now as I've missed a deadline and I have no idea how to get a working library built. I'm not interested in keeping the binaries small or even efficiency. If someone could tell me a simple way to build one gigantic binary linked with everything I'll need I would be most grateful. Surely it can't be that difficult. Ultimately, all we have are two directories of C++ source files that need to be compiled and linked. I've included both my scripts for building the two versions of quickfix I have. Many beers are available for the person who can help. :-) Regards, barry ********************************************************* This is the script I used to build 1.4.0 ********************************************************* #!/bin/ksh gcc=/opt/gnu/bin/gcc # INCLUDE JSEI=/opt/JDK-1.3/j2se/include JSES=/opt/JDK-1.3/j2se/include/solaris GCC1=/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95/2/include GCC2=/opt/gnu/include/g++-3 QUICKFIX_I1=~ QUICKFIX_I2=~/quickfix QUICKFIX_I3=~/quickfix/src/C++ LIBXML_I=/home/bishoba/libxml2-2.4.25/include # LIBS QUICKFIX_L=~/quickfix/lib LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$QUICKFIX_L LIBS='-lsocket -lnsl -lthread -lelf' MORELIBS='-lquickfix -lxml2' gcc -save-temps -G -o libquickfix_jni.so -fexceptions -finline-functions ../java/*.cpp ../C++/*.cpp -lgcc -lstdc++ -lpthread -lxml2 -liberty -lz -D_XOPEN_SOURCE=500 -lnsl -I$JSEI -I$JSES -I$GCC1 -I$GCC2 -I$QUICKFIX_I1 -I$QUICKFIX_I2 -I$QUICKFIX_I3 -I$LIBXML_I -I../../.. -I../../../include -I /home/bishoba -L/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/ -lsocket ********************************************************* This is the script I used to build 1.3.2 ********************************************************* #!/bin/ksh gcc=/opt/gnu/bin/gcc # INCLUDE JSEI=/opt/JDK-1.3/j2se/include JSES=/opt/JDK-1.3/j2se/include/solaris GCC1=/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95/2/include GCC2=/opt/gnu/include/g++-3 QUICKFIX_I1=~ QUICKFIX_I2=~/quickfix QUICKFIX_I3=~/quickfix/src/C++ LIBXML_I=/home/bishoba/libxml2-2.4.25/include # LIBS LIBS='-lsocket -lnsl -lthread -lelf' MORELIBS='-lquickfix -lxml2' gcc -G -o libquickfix_jni.so -fexceptions -finline-functions ../C++/*.cpp ../java/*.cpp -lgcc -lstdc++ -lpthread -lxml2 -liberty -lz -D_XOPEN_SOURCE=500 -lnsl -I$JSEI -I$JSES -I$GCC1 -I$GCC2 -I$QUICKFIX_I1 -I$QUICKFIX_I2 -I$QUICKFIX_I3 -I$LIBXML_I -I../../.. -I../../../include -I /home/bishoba -L/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/ -lsocket ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: Oren M. <ore...@ya...> - 2003-03-31 21:02:45
|
Yes, the fixes are in cvs, and yes we will be doing a 1.4.1 release soon. Should be coming out this week. Joerg Thoennes <Joe...@ma...> wrote:Oren Miller wrote: > We have a new build machine configured with RedHat > linux and gcc 3.2.7. This is in addition to the > Mandrake configuration with pgcc 2.95.3. Build > results are available from the developers page: Hi Oren, there were a couple of issues with the GCC 3.2 compiler (e.g. missing throw clauses) and Java support. I suppose the fixes are already in the CVS repository. Since I do not want to patch the 1.4.0 release by hand, my questions is: Will there be a bugfix release 1.4.1 in the very near future? I would appreciate it very much. Cheers, Joerg -- 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 --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: Oren M. <ore...@ya...> - 2003-03-31 21:02:33
|
Yes, the fixes are in cvs, and yes we will be doing a 1.4.1 release soon. Should be coming out this week. Joerg Thoennes <Joe...@ma...> wrote:Oren Miller wrote: > We have a new build machine configured with RedHat > linux and gcc 3.2.7. This is in addition to the > Mandrake configuration with pgcc 2.95.3. Build > results are available from the developers page: Hi Oren, there were a couple of issues with the GCC 3.2 compiler (e.g. missing throw clauses) and Java support. I suppose the fixes are already in the CVS repository. Since I do not want to patch the 1.4.0 release by hand, my questions is: Will there be a bugfix release 1.4.1 in the very near future? I would appreciate it very much. Cheers, Joerg -- 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 --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: Oren M. <ore...@ya...> - 2003-03-31 21:01:03
|
What version of gcc are you using? Is it 2.96? If so you need to either move down to 2.95.3 or use 3.2. 2.96 is buggy and doesn't handle exceptions correctly. David Monheit <Dav...@mo...> wrote:Hi All, Finally made some progress... I got a server program, ie, acceptor based appliation, runnig... As I mentioned on my last mail, only got it to send messages by using sendToTarget(Message, SessionID). When I started working on the client app, initiator based application, all hell broke loose :-) Basically, it turns out that NO application works, as it simply aborts (on my home linux box, without a core. In the office, thankfully, it does core, see listing below). Banzai also does not work (I see the gui pop up briefly and then it dies). After several hours yesterday, I was able to show that if the quickfix library throws ANY exception, the app dies. Basically this happened when I did not set the ReconnectInterval in the config file. The docs say that this field is defaulted to 30 (and I see this from the constructors which do set this to 30). The onInitialize tries to get this value from the dictionary and if it does get it, it overrides the 30 default. If it does not find it, it catches the exception and continues!!! THIS CAUSES THE APP TO DIE. Seems that someone does not like any exceptions thrown even if they are caught. To prove this, I commented the line out and the code then cored elsewhere (on getHost() where the code tries to get the host with a number attached (ie SocketConnectionHost0 ). If it does not find it, it uses the standard on, ie, SocketConnectionHost ... But again, the fact that an exception was thrown, blows the program... Here is the listing of the stack when ReconnectInterval is not set... #0 0x40076b41 in __kill () at __kill:-1 -1 __kill: No such file or directory. in __kill (gdb) where #0 0x40076b41 in __kill () at __kill:-1 #1 0x4003879b in raise (sig=6) at signals.c:65 #2 0x400780c2 in abort () at ../sysdeps/generic/abort.c:88 #3 0x4035c0a2 in os::abort () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #4 0x403590ac in os::handle_unexpected_exception () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #5 0x4035cb2a in JVM_handle_linux_signal () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #6 0x4035b844 in signalHandler () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #7 0x40038b53 in pthread_sighandler_rt (signo=11, si=0xbfe0dc90, uc=0xbfe0dd10) at signals.c:121 #8 <signal handler called> #9 0x4060cd3a in __cplus_type_matcher (info=0x8297ef0, match_info=0x4c939f54 <FIX::ConfigError type_info function>, exception_table=0x0) from /usr/lib/libstdc++-libc6.1-1.so.2 #10 0x4cb6a3bc in __eh_rtime_match (rtime=0x4c939f54) from /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so #11 0x4c9050be in FIX::SocketInitiator::getHost () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #12 0x4c9046f8 in FIX::SocketInitiator::doConnect () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #13 0x4c902428 in FIX::Initiator::connect () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #14 0x4c904653 in FIX::SocketInitiator::onStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #15 0x4c9026b6 in FIX::Initiator::start () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #16 0x4c8efb0d in Java_org_quickfix_SocketInitiator_doStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #17 0x4207412d in ?? () #18 0x4206cf93 in ?? () #19 0x4206d299 in ?? () #20 0x4206cf93 in ?? () #21 0x4206a195 in ?? () #22 0x402c04f6 in JavaCalls::call_helper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #23 0x4035b44d in os::os_exception_wrapper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #24 0x402c0644 in JavaCalls::call () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #25 0x402c85cd in jni_invoke () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #26 0x402d7bcd in jni_CallStaticVoidMethod () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #27 0x08049372 in strcpy () at strcpy:-1 #28 0x40064687 in __libc_start_main (main=0x8048c60 <strcpy+200>, argc=5, ubp_av=0xbffeb054, init=0x80488e8, fini=0x804ba0c <strcpy+11892>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffeb04c) Here is the listing if I do set ReconnectInterval ... #0 0x40076b41 in __kill () at __kill:-1 #1 0x4003879b in raise (sig=6) at signals.c:65 #2 0x400780c2 in abort () at ../sysdeps/generic/abort.c:88 #3 0x4035c0a2 in os::abort () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #4 0x403590ac in os::handle_unexpected_exception () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #5 0x4035cb2a in JVM_handle_linux_signal () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #6 0x4035b844 in signalHandler () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #7 0x40038b53 in pthread_sighandler_rt (signo=11, si=0xbfe0dc90, uc=0xbfe0dd10) at signals.c:121 #8 <signal handler called> #9 0x4060cd3a in __cplus_type_matcher (info=0x82917a0, match_info=0x4060d2c4 <exception type_info function>, exception_table=0x0) from /usr/lib/libstdc++-libc6.1-1.so.2 #10 0x4cb6a3bc in __eh_rtime_match (rtime=0x4060d2c4) from /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so #11 0x4c904581 in FIX::SocketInitiator::onInitialize () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #12 0x4c9025d2 in FIX::Initiator::start () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #13 0x4c8efb0d in Java_org_quickfix_SocketInitiator_doStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #14 0x4207412d in ?? () #15 0x4206cf93 in ?? () #16 0x4206d299 in ?? () #17 0x4206cf93 in ?? () #18 0x4206a195 in ?? () #19 0x402c04f6 in JavaCalls::call_helper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #20 0x4035b44d in os::os_exception_wrapper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #21 0x402c0644 in JavaCalls::call () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #22 0x402c85cd in jni_invoke () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #23 0x402d7bcd in jni_CallStaticVoidMethod () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #24 0x08049372 in strcpy () at strcpy:-1 #25 0x40064687 in __libc_start_main (main=0x8048c60 <strcpy+200>, argc=5, ubp_av=0xbffec954, init=0x80488e8, fini=0x804ba0c <strcpy+11892>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffec94c) at ../sysdeps/generic/libc-start.c:129 This one dies on the getHost() call... Has anyone seen this before? Did I compile this wrongly? I ended up commenting out loads of code in the library until I got it to go as far as "calling onStart()" in Initiator::start() but never got the "calling thread_join" output... I did get the "doConnect is returning true". Also did not get the "calling onRun()" message. The log file for .events are update fine but the app dies right after that. void Initiator::start() throw ( RuntimeError& ) { onInitialize( m_settings ); int threadid = thread_spawn( &startThread, this ); if ( !threadid ) throw RuntimeError("Unable to spawn thread"); std::cout << "calling onStart()" << std::endl; onStart(); std::cout << "calling thread_join()" << std::endl; thread_join( threadid ); } void* Initiator::startThread( void* p ) { Initiator * pInitiator = static_cast < Initiator* > ( p ); std::cout << "calling onRun()" << std::endl; pInitiator->getApplication().onRun(); pInitiator->stop(); return 0; } bool SocketInitiator::doConnect( const SessionID& s, const Dictionary& d ) { try { std::string address; short port = 0; Log* log = Session::lookupSession( s )->getLog(); getHost( s, d, address, port ); log->onEvent( "Connecting to " + address + " on port " + IntConvertor::convert((unsigned short)port) ); int result = m_connector.connect( address, port ); if ( !result ) { log->onEvent( "Connection failed" ); return false; } log->onEvent( "Connection succeeded" ); m_connections[ result ] = new SocketConnection ( *this, s, result, &m_connector.getMonitor() ); std::cout << "doConnect is returning true" << std::endl; return true; } catch ( std::exception& ) { return false; } } This has got something to do with exception thrwoing under linux... I saw stuff about it in the archives... Any ideas? David -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: Oren M. <ore...@ya...> - 2003-03-31 20:58:22
|
at_client really should be removed from the projects. It's not actually used and don't think that it is up to date. I would recommend looking at the projects under the examples directory instead. Vamsi Krishna <Vam...@ib...> wrote:Hi all I am trying to invoke the at_client exe with a config file. I am getting the below error DEBUG ASSERTION FAILURE program dbgheap.c _block_type_is_valid(phead->nblockuse) its an assertion failure.. Did anybody get this problem. I would appreciate if somebody gives solution for this Thanks Krishna ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers --------------------------------- Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! |
From: Vamsi K. <Vam...@ib...> - 2003-03-31 20:39:24
|
Hi all Does Mysql support of Quickfix means, you can connect to database for outbound messages. Or is it only suitable for logging? Thanks in advance Krishna /-----Original Message----- /From: qui...@li... [mailto:quickfix- /dev...@li...] On Behalf Of Vamsi Krishna /Sent: Sunday, March 30, 2003 11:42 PM /To: 'Quickfix' /Subject: [Quickfix-developers] Initiator / /Hi all / /My FIXCLient needs to poll a database table for messages ( a typical /scenario in Front office) and still maintain a session. / /Can at_client program do that. / /Can somebody give me a lead on this. / /Krishna / / / /------------------------------------------------------- /This SF.net email is sponsored by: /The Definitive IT and Networking Event. Be There! /NetWorld+Interop Las Vegas 2003 -- Register today! /http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en /_______________________________________________ /Quickfix-developers mailing list /Qui...@li... /https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
From: Bishop, B. <Bar...@gs...> - 2003-03-31 19:49:20
|
Hi, I've been developing an application using quickfix 1.3.2 and java running on solaris. I never managed to get the build working correctly and resorted to compiling every source file and linking them into one huge shared object library. Everything seemed to be fine all the way through development and testing until the application was released in to production whereupon it failed after a few seconds with a 'Problem has occured in a thread outside the JVM...' error. The production machine is a very fast dual processor sun box and the application failed on the initial download of SecurityStatus messages which proceeds very quickly until the crash. Is there a known problem using quickfix on a multi-processor machine? I noticed that quickfix 1.4.0 contains a fix for a 'race condition' and so decided to give it a go. However, even though I managed to get configure to work (without the libxml test) the build still doesn't give me a working shared object library. It warns me when linking libquickfix_jni.so that it has not linked to libquickfix as a shared version is not available. Is it possible to make a shared version of this library? Sure enough, the library fails to load in to the JVM. I've resorted to using my old build script which worked with quickfix 1.3.2, but this leads relocation errors at load time (__eh_alloc or __builtin_vec_new or others depending on my tweaks to my build script). I'm pretty desperate now as I've missed a deadline and I have no idea how to get a working library built. I'm not interested in keeping the binaries small or even efficiency. If someone could tell me a simple way to build one gigantic binary linked with everything I'll need I would be most grateful. Surely it can't be that difficult. Ultimately, all we have are two directories of C++ source files that need to be compiled and linked. I've included both my scripts for building the two versions of quickfix I have. Many beers are available for the person who can help. :-) Regards, barry ********************************************************* This is the script I used to build 1.4.0 ********************************************************* #!/bin/ksh gcc=/opt/gnu/bin/gcc # INCLUDE JSEI=/opt/JDK-1.3/j2se/include JSES=/opt/JDK-1.3/j2se/include/solaris GCC1=/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95/2/include GCC2=/opt/gnu/include/g++-3 QUICKFIX_I1=~ QUICKFIX_I2=~/quickfix QUICKFIX_I3=~/quickfix/src/C++ LIBXML_I=/home/bishoba/libxml2-2.4.25/include # LIBS QUICKFIX_L=~/quickfix/lib LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$QUICKFIX_L LIBS='-lsocket -lnsl -lthread -lelf' MORELIBS='-lquickfix -lxml2' gcc -save-temps -G -o libquickfix_jni.so -fexceptions -finline-functions ../java/*.cpp ../C++/*.cpp -lgcc -lstdc++ -lpthread -lxml2 -liberty -lz -D_XOPEN_SOURCE=500 -lnsl -I$JSEI -I$JSES -I$GCC1 -I$GCC2 -I$QUICKFIX_I1 -I$QUICKFIX_I2 -I$QUICKFIX_I3 -I$LIBXML_I -I../../.. -I../../../include -I /home/bishoba -L/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/ -lsocket ********************************************************* This is the script I used to build 1.3.2 ********************************************************* #!/bin/ksh gcc=/opt/gnu/bin/gcc # INCLUDE JSEI=/opt/JDK-1.3/j2se/include JSES=/opt/JDK-1.3/j2se/include/solaris GCC1=/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95/2/include GCC2=/opt/gnu/include/g++-3 QUICKFIX_I1=~ QUICKFIX_I2=~/quickfix QUICKFIX_I3=~/quickfix/src/C++ LIBXML_I=/home/bishoba/libxml2-2.4.25/include # LIBS LIBS='-lsocket -lnsl -lthread -lelf' MORELIBS='-lquickfix -lxml2' gcc -G -o libquickfix_jni.so -fexceptions -finline-functions ../C++/*.cpp ../java/*.cpp -lgcc -lstdc++ -lpthread -lxml2 -liberty -lz -D_XOPEN_SOURCE=500 -lnsl -I$JSEI -I$JSES -I$GCC1 -I$GCC2 -I$QUICKFIX_I1 -I$QUICKFIX_I2 -I$QUICKFIX_I3 -I$LIBXML_I -I../../.. -I../../../include -I /home/bishoba -L/opt/gnu/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/ -lsocket |
From: Gene G. <mus...@ya...> - 2003-03-31 16:33:43
|
David, does quickfix pass its own acceptance tests (build and run in quickfix/test)? I have found that on Linux there could be subtle misconfiguartions of the build tools, compiler and libraries which results in the symptoms similar to what you describe. Passing all of the acceptance tests was a good indication that I found a stable configuration. As a ray of hope, my company has beedn devloping on quickfix in both C++ and Java API's on Linux for the past half a year or so and found it to be generally stable. Gene --- David Monheit <Dav...@mo...> wrote: > Hi All, > > Finally made some progress... I got a server > program, ie, acceptor > based appliation, runnig... As I mentioned on my > last mail, only got it > to send messages by using sendToTarget(Message, > SessionID). > > When I started working on the client app, initiator > based application, > all hell broke loose :-) Basically, it turns out > that NO application > works, as it simply aborts (on my home linux box, > without a core. In the > office, thankfully, it does core, see listing > below). Banzai also does > not work (I see the gui pop up briefly and then it > dies). > > After several hours yesterday, I was able to show > that if the quickfix > library throws ANY exception, the app dies. > Basically this happened > when I did not set the ReconnectInterval in the > config file. The docs > say that this field is defaulted to 30 (and I see > this from the > constructors which do set this to 30). The > onInitialize tries to get > this value from the dictionary and if it does get > it, it overrides the > 30 default. If it does not find it, it catches the > exception and > continues!!! THIS CAUSES THE APP TO DIE. Seems > that someone does not > like any exceptions thrown even if they are caught. > > To prove this, I commented the line out and the code > then cored > elsewhere (on getHost() where the code tries to get > the host with a > number attached (ie SocketConnectionHost0 ). If it > does not find it, it > uses the standard on, ie, SocketConnectionHost ... > But again, the fact > that an exception was thrown, blows the program... > > Here is the listing of the stack when > ReconnectInterval is not set... > > #0 0x40076b41 in __kill () at __kill:-1 > -1 __kill: No such file or directory. > in __kill > (gdb) where > #0 0x40076b41 in __kill () at __kill:-1 > #1 0x4003879b in raise (sig=6) at signals.c:65 > #2 0x400780c2 in abort () at > ../sysdeps/generic/abort.c:88 > #3 0x4035c0a2 in os::abort () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #4 0x403590ac in os::handle_unexpected_exception () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #5 0x4035cb2a in JVM_handle_linux_signal () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #6 0x4035b844 in signalHandler () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #7 0x40038b53 in pthread_sighandler_rt (signo=11, > si=0xbfe0dc90, > uc=0xbfe0dd10) at signals.c:121 > #8 <signal handler called> > #9 0x4060cd3a in __cplus_type_matcher > (info=0x8297ef0, > match_info=0x4c939f54 <FIX::ConfigError > type_info function>, > exception_table=0x0) > from /usr/lib/libstdc++-libc6.1-1.so.2 > #10 0x4cb6a3bc in __eh_rtime_match > (rtime=0x4c939f54) > from > /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so > #11 0x4c9050be in FIX::SocketInitiator::getHost () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #12 0x4c9046f8 in FIX::SocketInitiator::doConnect () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #13 0x4c902428 in FIX::Initiator::connect () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #14 0x4c904653 in FIX::SocketInitiator::onStart () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #15 0x4c9026b6 in FIX::Initiator::start () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #16 0x4c8efb0d in > Java_org_quickfix_SocketInitiator_doStart () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #17 0x4207412d in ?? () > #18 0x4206cf93 in ?? () > #19 0x4206d299 in ?? () > #20 0x4206cf93 in ?? () > #21 0x4206a195 in ?? () > #22 0x402c04f6 in JavaCalls::call_helper () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #23 0x4035b44d in os::os_exception_wrapper () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #24 0x402c0644 in JavaCalls::call () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #25 0x402c85cd in jni_invoke () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #26 0x402d7bcd in jni_CallStaticVoidMethod () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #27 0x08049372 in strcpy () at strcpy:-1 > #28 0x40064687 in __libc_start_main (main=0x8048c60 > <strcpy+200>, > argc=5, ubp_av=0xbffeb054, > init=0x80488e8, fini=0x804ba0c <strcpy+11892>, > rtld_fini=0x4000dcd4 > <_dl_fini>, stack_end=0xbffeb04c) > > Here is the listing if I do set ReconnectInterval > ... > > #0 0x40076b41 in __kill () at __kill:-1 > #1 0x4003879b in raise (sig=6) at signals.c:65 > #2 0x400780c2 in abort () at > ../sysdeps/generic/abort.c:88 > #3 0x4035c0a2 in os::abort () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #4 0x403590ac in os::handle_unexpected_exception () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #5 0x4035cb2a in JVM_handle_linux_signal () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #6 0x4035b844 in signalHandler () > from > /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so > > #7 0x40038b53 in pthread_sighandler_rt (signo=11, > si=0xbfe0dc90, > uc=0xbfe0dd10) at signals.c:121 > #8 <signal handler called> > #9 0x4060cd3a in __cplus_type_matcher > (info=0x82917a0, > match_info=0x4060d2c4 <exception type_info > function>, > exception_table=0x0) > from /usr/lib/libstdc++-libc6.1-1.so.2 > #10 0x4cb6a3bc in __eh_rtime_match > (rtime=0x4060d2c4) > from > /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so > #11 0x4c904581 in FIX::SocketInitiator::onInitialize > () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #12 0x4c9025d2 in FIX::Initiator::start () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #13 0x4c8efb0d in > Java_org_quickfix_SocketInitiator_doStart () > from > /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 > > #14 0x4207412d in ?? () > #15 0x4206cf93 in ?? () > #16 0x4206d299 in ?? () > === message truncated === __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com |
From: Joerg T. <Joe...@ma...> - 2003-03-31 14:50:01
|
Oren Miller wrote: > We have a new build machine configured with RedHat > linux and gcc 3.2.7. This is in addition to the > Mandrake configuration with pgcc 2.95.3. Build > results are available from the developers page: Hi Oren, there were a couple of issues with the GCC 3.2 compiler (e.g. missing throw clauses) and Java support. I suppose the fixes are already in the CVS repository. Since I do not want to patch the 1.4.0 release by hand, my questions is: Will there be a bugfix release 1.4.1 in the very near future? I would appreciate it very much. Cheers, Joerg -- 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: David M. <Dav...@mo...> - 2003-03-31 09:43:28
|
Hi All, Finally made some progress... I got a server program, ie, acceptor based appliation, runnig... As I mentioned on my last mail, only got it to send messages by using sendToTarget(Message, SessionID). When I started working on the client app, initiator based application, all hell broke loose :-) Basically, it turns out that NO application works, as it simply aborts (on my home linux box, without a core. In the office, thankfully, it does core, see listing below). Banzai also does not work (I see the gui pop up briefly and then it dies). After several hours yesterday, I was able to show that if the quickfix library throws ANY exception, the app dies. Basically this happened when I did not set the ReconnectInterval in the config file. The docs say that this field is defaulted to 30 (and I see this from the constructors which do set this to 30). The onInitialize tries to get this value from the dictionary and if it does get it, it overrides the 30 default. If it does not find it, it catches the exception and continues!!! THIS CAUSES THE APP TO DIE. Seems that someone does not like any exceptions thrown even if they are caught. To prove this, I commented the line out and the code then cored elsewhere (on getHost() where the code tries to get the host with a number attached (ie SocketConnectionHost0 ). If it does not find it, it uses the standard on, ie, SocketConnectionHost ... But again, the fact that an exception was thrown, blows the program... Here is the listing of the stack when ReconnectInterval is not set... #0 0x40076b41 in __kill () at __kill:-1 -1 __kill: No such file or directory. in __kill (gdb) where #0 0x40076b41 in __kill () at __kill:-1 #1 0x4003879b in raise (sig=6) at signals.c:65 #2 0x400780c2 in abort () at ../sysdeps/generic/abort.c:88 #3 0x4035c0a2 in os::abort () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #4 0x403590ac in os::handle_unexpected_exception () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #5 0x4035cb2a in JVM_handle_linux_signal () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #6 0x4035b844 in signalHandler () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #7 0x40038b53 in pthread_sighandler_rt (signo=11, si=0xbfe0dc90, uc=0xbfe0dd10) at signals.c:121 #8 <signal handler called> #9 0x4060cd3a in __cplus_type_matcher (info=0x8297ef0, match_info=0x4c939f54 <FIX::ConfigError type_info function>, exception_table=0x0) from /usr/lib/libstdc++-libc6.1-1.so.2 #10 0x4cb6a3bc in __eh_rtime_match (rtime=0x4c939f54) from /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so #11 0x4c9050be in FIX::SocketInitiator::getHost () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #12 0x4c9046f8 in FIX::SocketInitiator::doConnect () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #13 0x4c902428 in FIX::Initiator::connect () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #14 0x4c904653 in FIX::SocketInitiator::onStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #15 0x4c9026b6 in FIX::Initiator::start () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #16 0x4c8efb0d in Java_org_quickfix_SocketInitiator_doStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #17 0x4207412d in ?? () #18 0x4206cf93 in ?? () #19 0x4206d299 in ?? () #20 0x4206cf93 in ?? () #21 0x4206a195 in ?? () #22 0x402c04f6 in JavaCalls::call_helper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #23 0x4035b44d in os::os_exception_wrapper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #24 0x402c0644 in JavaCalls::call () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #25 0x402c85cd in jni_invoke () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #26 0x402d7bcd in jni_CallStaticVoidMethod () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #27 0x08049372 in strcpy () at strcpy:-1 #28 0x40064687 in __libc_start_main (main=0x8048c60 <strcpy+200>, argc=5, ubp_av=0xbffeb054, init=0x80488e8, fini=0x804ba0c <strcpy+11892>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffeb04c) Here is the listing if I do set ReconnectInterval ... #0 0x40076b41 in __kill () at __kill:-1 #1 0x4003879b in raise (sig=6) at signals.c:65 #2 0x400780c2 in abort () at ../sysdeps/generic/abort.c:88 #3 0x4035c0a2 in os::abort () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #4 0x403590ac in os::handle_unexpected_exception () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #5 0x4035cb2a in JVM_handle_linux_signal () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #6 0x4035b844 in signalHandler () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #7 0x40038b53 in pthread_sighandler_rt (signo=11, si=0xbfe0dc90, uc=0xbfe0dd10) at signals.c:121 #8 <signal handler called> #9 0x4060cd3a in __cplus_type_matcher (info=0x82917a0, match_info=0x4060d2c4 <exception type_info function>, exception_table=0x0) from /usr/lib/libstdc++-libc6.1-1.so.2 #10 0x4cb6a3bc in __eh_rtime_match (rtime=0x4060d2c4) from /u/cwscs1_OR/monheit/projects/STLport-4.5.3/lib/libstlport_gcc.so #11 0x4c904581 in FIX::SocketInitiator::onInitialize () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #12 0x4c9025d2 in FIX::Initiator::start () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #13 0x4c8efb0d in Java_org_quickfix_SocketInitiator_doStart () from /a/cwscs1/d/OR/monheit/projects/quickfix/src/java/.libs/libquickfix_jni.so.1.0.0 #14 0x4207412d in ?? () #15 0x4206cf93 in ?? () #16 0x4206d299 in ?? () #17 0x4206cf93 in ?? () #18 0x4206a195 in ?? () #19 0x402c04f6 in JavaCalls::call_helper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #20 0x4035b44d in os::os_exception_wrapper () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #21 0x402c0644 in JavaCalls::call () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #22 0x402c85cd in jni_invoke () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #23 0x402d7bcd in jni_CallStaticVoidMethod () from /ms/dist/msjava/PROJ/sunjdk/1.4.0_01/.exec/@sys/jre/lib/i386/client/libjvm.so #24 0x08049372 in strcpy () at strcpy:-1 #25 0x40064687 in __libc_start_main (main=0x8048c60 <strcpy+200>, argc=5, ubp_av=0xbffec954, init=0x80488e8, fini=0x804ba0c <strcpy+11892>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffec94c) at ../sysdeps/generic/libc-start.c:129 This one dies on the getHost() call... Has anyone seen this before? Did I compile this wrongly? I ended up commenting out loads of code in the library until I got it to go as far as "calling onStart()" in Initiator::start() but never got the "calling thread_join" output... I did get the "doConnect is returning true". Also did not get the "calling onRun()" message. The log file for .events are update fine but the app dies right after that. void Initiator::start() throw ( RuntimeError& ) { onInitialize( m_settings ); int threadid = thread_spawn( &startThread, this ); if ( !threadid ) throw RuntimeError("Unable to spawn thread"); std::cout << "calling onStart()" << std::endl; onStart(); std::cout << "calling thread_join()" << std::endl; thread_join( threadid ); } void* Initiator::startThread( void* p ) { Initiator * pInitiator = static_cast < Initiator* > ( p ); std::cout << "calling onRun()" << std::endl; pInitiator->getApplication().onRun(); pInitiator->stop(); return 0; } bool SocketInitiator::doConnect( const SessionID& s, const Dictionary& d ) { try { std::string address; short port = 0; Log* log = Session::lookupSession( s )->getLog(); getHost( s, d, address, port ); log->onEvent( "Connecting to " + address + " on port " + IntConvertor::convert((unsigned short)port) ); int result = m_connector.connect( address, port ); if ( !result ) { log->onEvent( "Connection failed" ); return false; } log->onEvent( "Connection succeeded" ); m_connections[ result ] = new SocketConnection ( *this, s, result, &m_connector.getMonitor() ); std::cout << "doConnect is returning true" << std::endl; return true; } catch ( std::exception& ) { return false; } } This has got something to do with exception thrwoing under linux... I saw stuff about it in the archives... Any ideas? David -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. |
From: Vamsi K. <Vam...@ib...> - 2003-03-31 04:42:20
|
Hi all My FIXCLient needs to poll a database table for messages ( a typical scenario in Front office) and still maintain a session. Can at_client program do that. Can somebody give me a lead on this. Krishna |
From: Vamsi K. <Vam...@ib...> - 2003-03-31 04:33:52
|
Hi all I am trying to invoke the at_client exe with a config file. I am getting the below error DEBUG ASSERTION FAILURE program dbgheap.c _block_type_is_valid(phead->nblockuse) its an assertion failure.. Did anybody get this problem. I would appreciate if somebody gives solution for this Thanks Krishna |
From: David M. <Dav...@mo...> - 2003-03-28 15:06:56
|
Hi Starting the debate of earlier threads again... IMHO a client app could either try to keep the state of the world (SOW) itself of delegate it to something else which then uses different methods for dispersing this info. A client app could go to a db to get known orders and status on startup, connect to a pub/sub system and request the current SOW or whatever. A server, however, specially something like an order manager must keep track of its orders EVEN through a core !!! As Oren mentioned in some earlier thread, this presents a problem. Server which handle large order flow will have a huge FIX traffic whose latency needs to be kept to a minimum. Writing orders to a db or whatever is basically out of the quesion because of the IO time involved. Since QF does have the logs stored if the file system one would imagine that re-loading the order server to the state prior to a core is just a matter of replaying the messages and rebuiding the order collection. This however, is a server problem, not a qf problem. I would vote for writing a small library for reading and even better, replaying these messages. For instance we could create a MessageReplayApplication which subclasses Application. This classes' thread would read the inbound log file and invoke fromApp callbacks. Any messages sent by this app would be ignored!!!! This would allow a server to rebuild its state. When done, the main class deletes this playback object and start the real one.... Just a thought anyways. The point is that for some apps we DO need to have not just message recovery but state recovery as well... David -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. |
From: David M. <Dav...@mo...> - 2003-03-28 14:47:50
|
Hi all, Coming along in QF. I saw some old threads which experienced this exact problem, ie, QF for Java has some problem finding the right session. Here is the scoop: There are 3 overrides to Session.sendToTarget a) sendToTarget(Message) b) sendToTarget(Message, SessionID) c) sendToTarget(Message, SenderCompID (string), SenderTargetID (string)) It turns out that no matter what I tried with c, I ALWAYS got SessionNotFound!!! I also noticed that if I set the following in the cfg file: SenderCompID=OrderEngine TargetCompID=monheit I got back a sessionID of "FIX.4.0:OrderEngine->monheit" on the C++ program, ie, executor. When I ran my order entry program in Java with a cfg of: SenderCompID=monheit TargetCompID=OrderEngine the sessionID was "FIX.4.0: monheit->OrderEngine" !!! Note the space in there!!!! The way I got it to work is by using override b, and sending the SessionID which I got on the order... I did not try method a yet. Need to have a look at why this is. Regards David |
From: Vitor C. <vc...@hi...> - 2003-03-28 10:38:03
|
Hi Jac, Are you trying to expose the objects in quickfix_net_debug.dll as COM objects? If not check to see if your quickfix .net project isn't by mistake enabling the registration of the dll as a COM server. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Jacob Steyn Sent: sexta-feira, 28 de Mar=E7o de 2003 8:59 To: qui...@li... Subject: [Quickfix-developers] COM Error when trying to initialize acceptor HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
From: Jacob S. <ja...@pe...> - 2003-03-28 10:23:35
|
Hi Vitor Thanks. Im not trying to expose them. Using the default quickfix_net_debug.dll in 1.4.0 and just referencing it in my .net solution which doesnt register in COM. -----Original Message----- From: Vitor Castro [mailto:vc...@hi...] Sent: 28 March 2003 11:27 To: Jacob Steyn; qui...@li... Subject: RE: [Quickfix-developers] COM Error when trying to initialize acceptor Hi Jac, Are you trying to expose the objects in quickfix_net_debug.dll as COM objects? If not check to see if your quickfix .net project isn't by mistake enabling the registration of the dll as a COM server. -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Jacob Steyn Sent: sexta-feira, 28 de Mar=E7o de 2003 8:59 To: qui...@li... Subject: [Quickfix-developers] COM Error when trying to initialize acceptor HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
From: Jacob S. <ja...@pe...> - 2003-03-28 08:59:12
|
HI All I get this error when in C# I try to start the socketacceptor. An unhandled exception of type 'QuickFix.ConfigError' occurred in = quickfix_net_debug.dll Additional information: Could not initialize COM Any Ideas? Thanks Jac |