RE: [Quickfix-users] QuickFIX/J 1.0.0 Beta 3 Released
Brought to you by:
orenmnero
From: Kimpton, C \(Chris\) <Chr...@ra...> - 2006-02-22 08:47:15
|
Hi Steve, Nope - its largely the same config file I used for the JNI version: [DEFAULT] ConnectionType=3Dinitiator HeartBtInt=3D20 FileStorePath=3Dorder-store StartTime=3D00:01:00 EndTime=3D21:55:00 UseDataDictionary=3DY DataDictionary=3D../config/FIX42.xml SocketConnectHost=3Dlocalhost SocketConnectPort=3D4430 #failover SocketConnectHost1=3Dlocalhost SocketConnectPort1=3D543 ReconnectInterval=3D10 ResetOnDisconnect=3DN ResetOnLogout=3DN ValidateFieldsOutOfOrder=3DN CheckLatency=3DN FileLogPath=3Dfixlogs-orders SocketNodelay=3DY [SESSION] BeginString=3DFIX.4.2 SenderCompID=3Dxxx TargetCompID=3Dyyy =20 Thanks, Chris -----Original Message----- From: Steve Bate [mailto:sb...@sm...]=20 Sent: 22 February 2006 08:36 To: Kimpton, C (Chris); qui...@li... Subject: RE: [Quickfix-users] QuickFIX/J 1.0.0 Beta 3 Released Hi Chris, It should work the same as the JNI version. Are you setting startDay and endDay in your settings?=20 Steve Bate Smart Trade Technologies Phone: +33 4 42 90 03 97 http://www.smart-trade.net/ > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of=20 > Kimpton, C (Chris) > Sent: Wednesday, February 22, 2006 9:17 AM > To: qui...@li... > Subject: RE: [Quickfix-users] QuickFIX/J 1.0.0 Beta 3 Released >=20 > QuickFIX Documentation:=20 > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html >=20 > Hi, >=20 > Are the session schedules working ok? >=20 > I had an initiator running last night with this config: >=20 > [DEFAULT] > ... > StartTime=3D00:01:00 > EndTime=3D21:55:00 > ... >=20 > But it did not logout at 21:55 - whereas the jni version has worked=20 > previously. >=20 > Thanks, > Chris >=20 > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of Steve > Bate > Sent: 17 February 2006 09:33 > To: qui...@li...; > qui...@li... > Subject: [Quickfix-users] QuickFIX/J 1.0.0 Beta 3 Released >=20 > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html >=20 > The Beta 3 version of QuickFIX/J is now available. I strongly=20 > recommend upgrading. I believe the MINA-based networking code is a=20 > significant improvement. >=20 > You can download the release at SourceForge. >=20 > http://tinyurl.com/apr6r >=20 > New Features and Improvements: >=20 > * QuickFIX JNI 1.11.0 compatibility (except MSSQL, PostgreSQL=20 > stores) > * Converted network code to MINA (Netty removed) > * Converted non-session logging to SLF4J (Commons Logging removed) > * SLF4J log category names can use SessionID-based patterns > * ScreenLogFactory can be configured to filter heartbeat messages > * New CompositeLogFactory supports use of multiple Logs > (for example, screen and file/jdbc) > * JdbcLog tables names are configurable > * Failover support for acceptors. > * Message component code generation and support in FieldMap. > * Updated third party libraries to latest versions. > * Standard FIX XML files can be loaded from quickfix.jar > * DataDictionary setting is optional, default dictionary inferred > from session BeginString. > * Improved DataDictionary error checking. > * Time zones can be specified for session schedules > * Added options for specifying resend ranges > =20 > Bug Fixes: >=20 > * Bug #147 QuoteRequestRejectReason missing 2 values > * Bug #148 toAdmin called incorrectly (Message.isAdmin() bug) >=20 > I'd like to thank Toby Shepheard and John Hensley for their=20 > contributions in this release. Smart Trade continues to provide the=20 > CruiseControl continuous integration server and also allows me to=20 > spend some time on QuickFIX at work (so I actually have something=20 > slightly resembling a social life). > Also, thanks to Oren Miller for project management tool support. I=20 > appreciate it. >=20 > My intention is for this to be the last beta release before the 1.0.0=20 > final version. As always, if you have problems or find bugs, please=20 > enter them into the bug tracker at quickfixengine.org. The more=20 > details you can provide, the better (unless the cause of the problem=20 > is very obvious). >=20 > I've also created a category about QuickFIX/J on my personal blog. You > can subscribe to an RSS feed for only this category if you'd like.=20 > I'll be posting a series of tips, examples and status updates on=20 > experiments I've been doing with QuickFIX/J, Spring Framework, ESB,=20 > JMX, JMS, and related technologies. I currently have an entry with=20 > some simple ideas for using extended settings in QuickFIX/J settings=20 > files. In the near future, I'll be posting information on how to use=20 > some of the new features in QuickFIX/J like the extended logging=20 > capabilities, acceptor failover, and the new message component=20 > classes. The URL for the blog category is... >=20 > http://blog.technoetic.com/categories/quickfixj/feed/ >=20 > I also recommend taking advantage of the consulting and training=20 > resources listed on the QuickFIX web site. In particular, training is=20 > one of those investments that pays for itself in saved time and=20 > headaches. OCI is a top training company and we are very fortunate as=20 > a community to have them providing QuickFIX and QuickFIX/J training. >=20 > Steve Bate > Smart Trade Technologies > Phone: +33 4 42 90 03 97 > http://www.smart-trade.net/ >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that=20 > makes searching your log files as easy as surfing the web. DOWNLOAD=20 > SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users > _____________________________________________________________ >=20 > This email (including any attachments to it) is confidential, legally=20 > privileged, subject to copyright and is sent for the personal=20 > attention of the intended recipient only. If you have received this=20 > email in error, please advise us immediately and delete it. You are=20 > notified that disclosing, copying, distributing or taking any action=20 > in reliance on the contents of this information is strictly=20 > prohibited. Although we have taken reasonable precautions to ensure no > viruses are present in this email, we cannot accept responsibility for > any loss or damage arising from the viruses in this email or=20 > attachments. We exclude any liability for the content of this email,=20 > or for the consequences of any actions taken on the basis of the=20 > information provided in this email or its attachments, unless that=20 > information is subsequently confirmed in writing. If this email=20 > contains an offer, that should be considered as an invitation to=20 > treat. > _____________________________________________________________ >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files for problems? Stop! Download the new AJAX=20 > search engine that makes searching your log files as easy as=20 > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Quickfix-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-users >=20 _____________________________________________________________ This email (including any attachments to it) is confidential, legally pri= vileged, subject to copyright and is sent for the personal attention of t= he intended recipient only. If you have received this email in error, ple= ase advise us immediately and delete it. You are notified that disclosing= , copying, distributing or taking any action in reliance on the contents = of this information is strictly prohibited. Although we have taken reason= able precautions to ensure no viruses are present in this email, we canno= t accept responsibility for any loss or damage arising from the viruses i= n this email or attachments. We exclude any liability for the content of = this email, or for the consequences of any actions taken on the basis of = the information provided in this email or its attachments, unless that in= formation is subsequently confirmed in writing. If this email contains an= =20offer, that should be considered as an invitation to treat. _____________________________________________________________ |