|
From: Tommy H. <Tom...@Bo...> - 2007-04-27 16:40:46
|
Alex, The SenderCompID is a listed attribute and appears editable, but I have not attempted to change this as it is assigned in the "Settings" file and we have no need to change it on the fly. Regarding management... make sure you have made necessary code changes depending on your version of Java as described in the user manual. The "jconsole" application is in the java installation "bin" subdirectory. Just run it (you do not need any parameters). It would probably be best if you run it on the same machine as your FIX application under the same user. The process ID will be listed and all you have to do is select it and click "connect". You can also run it remotely, but you will probably need to open firewall ports. I hope that helps. -Tommy On Apr 27, 2007, at 5:12 AM, Alex McGlashan wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hi Tommy, > > I was interested to read your note below about updating session > attributes on the fly. Does this include new SenderCompID values? > Could you describe the process for starting the console and connecting > in a bit more detail? > > Thanks in advance, > Alex > > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of > Tommy Hannon > Sent: 26 April 2007 17:54 > To: qui...@li... > Subject: Re: [Quickfixj-users] newbie questions > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > I just started developing with QuickFIX/J last week and am totally > delighted with the ease of use (kinda of like switching to a Mac). > > Most everything you need to manage the "grunt-work" of the protocol > is handled using the "Setting" file as described in the user manual. > Session level stuff, Logon/Logout, heartbeats, resends, all are > handled "under-the-hood" and need not be handled at your application > level code. IMHO, the greatest benefit to new users is the > management extensions. > > Just add a few lines of code to a Java 1.5 codebase and a system > property on the command line; start "jconsole" and connect! (Be sure > to start the console using the same user as your application if > running locally) From there the session attributes page is a real > help. you can view or update values on-the-fly. Go to the > "Operations" tab and you can reset, disconnect, logon, or logoff > individual sessions. > > In general this product is very is easy to use, almost beyond > belief. My suggestion would be to check out the "Creating Your > Application", "Receiving Messages" and "Sending Messages" sections of > the user manual paying attention to the "Most Type Safe" approach. > > Good luck! > > -Tommy > > On Apr 26, 2007, at 10:46 AM, Toli Kuznets wrote: > >> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ >> QuickFIX/J Support: http://www.quickfixj.org/support/ >> Robert, >> >>> 1.) We plan on connecting to 4 end-points, so I have 4 sessions >>> in my >>> configuration file...is there a benefit to using the >>> ThreadedSocketInitiator as opposed to just the SocketInitiator? >> >> This is a classic trade-off. if you need all your incoming >> messages to >> be processed in order they are coming in across all connections, then >> use the regular SocketInitiator. >> If the 4 connections are totally unrelated then you can process them >> concurrently using the ThreadedSocketInitiator >> >>> >>> 2.) If one of our end-point's connection goes down indefinitely, >>> are >>> the remaining 3 sessions ok? Say one of the 4 end-points goes down >>> momentarily and then goes back up, will the engine reconnect or do I >>> have to bring the entire engine down and reconnect all 4 sessions? >> >> QFJ should reconnect to the lost connection when it comes back u and >> renegotiate a logon. >> there area various timeout settings you can tweak to modify the >> timeout behaviour. >> >>> 3.) Examples of the custom Initiator classes have a 'System.in' >>> statement waiting for a user to hit a key on the keyboard to exit >>> the >>> engine. If we want to put this process in the background, this >>> isn't a >>> feasible design obviously...so I was curious what people are >>> doing to >>> build an engine that can be set as a background process and then >>> when >>> brought back to the foreground, how is the engine being stopped >>> elegantly so the appropriate logout and disconnect procedures occur? >>> >> >> I'd be intersted to hear how others approach this problem as well. >> For >> now, we create the socket initiator and FIX listenrers in Spring, and >> then the main thread just goes to sleep (we do a new >> Semaphore(0).wait()). The OMS is then killed by pressing Ctrl-C if >> you >> run it on the console, or with an /etc/init.d script wrapping a 'kill >> -9' on our virtual appliance. Here's the code for reference: >> http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/oms/ >> src/main/java/org/marketcetera/oms/OrderManagementSystem.java#L59 >> >> >> -- >> Toli Kuznets >> http://www.marketcetera.com: Open-Source Trading Platform >> download.run.trade. >> >> --------------------------------------------------------------------- >> - > >> --- >> This SF.net email is sponsored by DB2 Express >> Download DB2 Express C - the FREE version of DB2 express and take >> control of your XML. No limits. Just data. Click to get it now. >> http://sourceforge.net/powerbar/db2/ >> _______________________________________________ >> Quickfixj-users mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfixj-users >> > > > ---------------------------------------------------------------------- > -- > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > Eurobase International Limited and its subsidiaries (Eurobase) are > unable to exercise control over the content of information in E- > Mails. Any views and opinions expressed may be personal to the > sender and are not necessarily those of Eurobase. Eurobase will not > enter into any contractual obligations in respect of any part of > its business in any E-mail. > > Privileged / confidential information may be contained in this > message and /or any attachments. This E-mail is intended for the > use of the addressee(s) only and may contain confidential > information. If you are not the / an intended recipient, you are > hereby notified that any use or dissemination of this communication > is strictly prohibited. If you receive this transmission in error, > please notify us immediately, and then delete this E-mail. > > Neither the sender nor Eurobase accepts any liability whatsoever > for any defects of any kind either in or arising from this E-mail > transmission. E-Mail transmission cannot be guaranteed to be secure > or error-free, as messages can be intercepted, lost, corrupted, > destroyed, contain viruses, or arrive late or incomplete. Eurobase > does not accept any responsibility for viruses and it is your > responsibility to scan any attachments. > > Eurobase Systems Limited is the main trading company in the > Eurobase International Group; registered in England and Wales as > company number 02251162; registered address: Essex House, 2 County > Place, Chelmsford, Essex CM2 0RE, UK. > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |