Re: [Quickfix-developers] JVM Access voilation.
Brought to you by:
orenmnero
From: Oren M. <ore...@ya...> - 2003-05-14 16:44:19
|
It's automatic. There is a configuration setting called RecconectInterval that you can set per session. It think the default is 20 or 30 seconds. When it reconnects and succesfully logs on you will get another onLogon. File logs don't go away until you delete them. I imagine many people may use cron to do a daily backup and cleanup of that path. If you don't want logs just don't pass a Logger into the Initiator constructor. It isn't required, but you will likely want it for troubleshooting. pc....@ta... wrote: Hi, Thanks for the reply. Couldn't see in the documentation how it handled. If the connection is lost I receive the "onLogout" callback, if I leave my onRun() loop running, and continue as normal will the engine reconnect by itself and send me another "OnLogon" when connected successfully? What sort of timeout, reconnect periods does it use? Also I was wondering when are the "FileLogPath" files cleaned up? or do they continue to grow. I tried omitting the parameter to turn them off, but got another ACCESS_VOILATION. Cheers Phil. > Well, this sounds like a problem, but I would also ask you why you are going through this process. QuickFIX handles reconnects for you, why are you trying to manually duplicate this behavior? > >pc....@ta... wrote:Hi, > >I using the quickfix engine via the quickfixjar -> JNI route. During testing I have been receiving access voilations when trying to perform reconnect to a fix engine server, when the connection is lost. > >The basic procedure is when the connection is lost, I destroy my Initiator fix class (only fix class referenced), sleep 30 seconds then attempt a reconnect. During testing I receive an "Access Voialtion" after the "third" reconnect attempt, this seems fairly consistent. > >As stated I believe I am clearing down my "initiator class" when the connection is lost, and recreating new the next time around. > >Below is the access voilatoin stack, same all the time. > >An unexpected exception has been detected in native code outside the VM. >Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x1001cb2d >Function name=(N/A) >Library=XXXXXXXXXX\Lib\quickfix\quickfix_jni.dll > >NOTE: We are unable to locate the function name symbol for the error >just occurred. Please refer to release documentation for possible >reason and solutions. > > > >Current Java thread: >at org.quickfix.SocketInitiator.destroy(Native Method) >at org.quickfix.SocketInitiator.finalize(Unknown Source) >at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) >at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:86) >at java.lang.ref.Finalizer.access$100(Finalizer.java:17) >at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:163) > > > > > >Thanks in advance. > >Phil. > >_________________________________ >Email: pc....@ta... > > >-------------------- >talk21 your FREE portable and private address on the net at http://www.talk21.com > > > >------------------------------------------------------- >Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara >The only event dedicated to issues related to Linux enterprise solutions >www.enterpriselinuxforum.com > >_______________________________________________ >Quickfix-developers mailing list >Qui...@li... >https://lists.sourceforge.net/lists/listinfo/quickfix-developers > > >--------------------------------- >Do you Yahoo!? >The New Yahoo! Search - Faster. Easier. Bingo. _________________________________ Email: pc....@ta... -------------------- talk21 your FREE portable and private address on the net at http://www.talk21.com --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. |