Thread: [Fwd: Re: [Quickfix-developers] stopping initiator hangs application]
Brought to you by:
orenmnero
|
From: tony w. <ton...@ya...> - 2006-04-07 18:08:35
|
Oren, I recently switched to calling logout before stop, thinking this was a cleaner method. I will switch back to just calling stop. Unfortunately I'm using the Express Editions of VS, which doesn't allow me to compile quickfix, due to a atlthunk.lib issue, it seems I need a full copy of VS to compile quickfix. Due to this I can not step into the debugger to find out where exactly it is hanging inside of quickfix. The only thing I can currently see is that it hangs when I call stop. Tony Oren Miller wrote: > First off, stop will call the logout method on all the sessions, so > there is no need to do so yourself (though it wouldn't hurt anything if > you did). Also, stop already has the following loop: > > for( int second = 1; second <= 10 && isLoggedOn(); ++second ) > process_sleep( 1 ); > > The only place I can think where it would block is when it joins on the > thread. Can you verify that this is where you the library is freezing? > > --oren > > On Apr 7, 2006, at 9:06 AM, Tony Weston wrote: > >> QuickFIX Documentation: >> http://www.quickfixengine.org/quickfix/doc/html/index.html >> QuickFIX Support: http://www.quickfixengine.org/services.html >> >> Hi Dave, >> >> Unfortunately, it hangs on the stop call so it will never reach the >> while loop that waits for the logout. I'm not currently waiting for a >> logout before calling stop, so putting this wait in after I call >> logout and before I call stop may fix the problem for me. >> >> Thank you, >> Tony >> >> Dave Linaker wrote: >>> Hi Tony, >>> Rather than calling logout and then stop (stop will logout anyway), have >>> you tried calling stop and then waiting for the logout to complete? e.g: >>> //stop the initiator >>> initiator.stop(); >>> //wait for logout >>> while(initiator.isLoggedOn()) >>> Thread.Sleep(500); >>> //continue... >>> Cheers >>> Dave >>> -----Original Message----- >>> From: qui...@li... >>> [mailto:qui...@li...] On Behalf Of >>> tony weston >>> Sent: 06 April 2006 19:43 >>> To: qui...@li... >>> Subject: [Quickfix-developers] stopping initiator hangs application >>> Hello, >>> I've been using quickfix with great success, although I've came across a >>> problem when trying to stop an initiator in VB .Net 2. When I call >>> "stop" my application will frequently hang on this call. I've tried >>> with version 1.11.1 and with using the automated builds for VS 8 under >>> the developers section of the website, both having the same results. >>> I'm also passing a value of "True" when calling the stop method to force >>> close, but it still occasionally hangs. Before calling stop I call >>> logout on my open session. Is there something that I'm doing >>> incorrectly or another way to get around this problem? >>> Thank you, >>> Tony >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language >> that extends applications into web and mobile media. Attend the live >> webcast >> and join the prime developer group breaking into this new coding >> territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> Quickfix-developers mailing list >> Qui...@li... >> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >> > > |
|
From: Oren M. <or...@qu...> - 2006-04-07 18:20:48
|
Tony, You need to download the Microsoft Platform SDK. See the December 31 entry on this page( http://www.geometrictools.com/ KnownProblems.html ). It gives instructions on how to work around the atlthunk.lib issue. I have tried this and have been able to succesfully compile QuickFIX with Visual Studio Express. --oren On Apr 7, 2006, at 1:09 PM, tony weston wrote: > Oren, > > I recently switched to calling logout before stop, thinking this was a > cleaner method. I will switch back to just calling stop. > > Unfortunately I'm using the Express Editions of VS, which doesn't > allow > me to compile quickfix, due to a atlthunk.lib issue, it seems I need a > full copy of VS to compile quickfix. Due to this I can not step into > the debugger to find out where exactly it is hanging inside of > quickfix. > The only thing I can currently see is that it hangs when I call stop. > > Tony > > Oren Miller wrote: >> First off, stop will call the logout method on all the sessions, >> so there is no need to do so yourself (though it wouldn't hurt >> anything if you did). Also, stop already has the following loop: >> for( int second = 1; second <= 10 && isLoggedOn(); ++second ) >> process_sleep( 1 ); >> The only place I can think where it would block is when it joins >> on the thread. Can you verify that this is where you the library >> is freezing? >> --oren >> On Apr 7, 2006, at 9:06 AM, Tony Weston wrote: >>> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/ >>> doc/html/index.html >>> QuickFIX Support: http://www.quickfixengine.org/services.html >>> >>> Hi Dave, >>> >>> Unfortunately, it hangs on the stop call so it will never reach >>> the while loop that waits for the logout. I'm not currently >>> waiting for a logout before calling stop, so putting this wait in >>> after I call logout and before I call stop may fix the problem >>> for me. >>> >>> Thank you, >>> Tony >>> >>> Dave Linaker wrote: >>>> Hi Tony, >>>> Rather than calling logout and then stop (stop will logout >>>> anyway), have >>>> you tried calling stop and then waiting for the logout to >>>> complete? e.g: >>>> //stop the initiator >>>> initiator.stop(); >>>> //wait for logout >>>> while(initiator.isLoggedOn()) >>>> Thread.Sleep(500); >>>> //continue... >>>> Cheers >>>> Dave >>>> -----Original Message----- >>>> From: qui...@li... >>>> [mailto:qui...@li...] On >>>> Behalf Of >>>> tony weston >>>> Sent: 06 April 2006 19:43 >>>> To: qui...@li... >>>> Subject: [Quickfix-developers] stopping initiator hangs application >>>> Hello, >>>> I've been using quickfix with great success, although I've came >>>> across a >>>> problem when trying to stop an initiator in VB .Net 2. When I call >>>> "stop" my application will frequently hang on this call. I've >>>> tried >>>> with version 1.11.1 and with using the automated builds for VS 8 >>>> under >>>> the developers section of the website, both having the same >>>> results. >>>> I'm also passing a value of "True" when calling the stop method >>>> to force >>>> close, but it still occasionally hangs. Before calling stop I call >>>> logout on my open session. Is there something that I'm doing >>>> incorrectly or another way to get around this problem? >>>> Thank you, >>>> Tony >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by xPML, a groundbreaking >>> scripting language >>> that extends applications into web and mobile media. Attend the >>> live webcast >>> and join the prime developer group breaking into this new coding >>> territory! >>> http://sel.as-us.falkag.net/sel? >>> cmd=lnk&kid=110944&bid=241720&dat=121642 >>> _______________________________________________ >>> Quickfix-developers mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >>> > > |
|
From: tony w. <ton...@ya...> - 2006-04-07 20:55:13
|
Oren,
Thank you, I'm now able to compile both quickfix.lib and
quickfix_net.dll Unfortunately I'm not able to get much more info since
I can't step into quickfix.lib. The Call Stack lists this as the new
hanging point:
void stop( bool force )
{ QF_STACK_TRY
m_pUnmanaged->stop( force );
QF_STACK_CATCH
}
Beyond this the call stack only lists this line "[Managed To Native
Transition]", which I am unable to step into.
Tony
Oren Miller wrote:
> Tony,
>
> You need to download the Microsoft Platform SDK. See the December 31
> entry on this page( http://www.geometrictools.com/KnownProblems.html ).
> It gives instructions on how to work around the atlthunk.lib issue. I
> have tried this and have been able to succesfully compile QuickFIX with
> Visual Studio Express.
>
> --oren
>
> On Apr 7, 2006, at 1:09 PM, tony weston wrote:
>
>> Oren,
>>
>> I recently switched to calling logout before stop, thinking this was a
>> cleaner method. I will switch back to just calling stop.
>>
>> Unfortunately I'm using the Express Editions of VS, which doesn't allow
>> me to compile quickfix, due to a atlthunk.lib issue, it seems I need a
>> full copy of VS to compile quickfix. Due to this I can not step into
>> the debugger to find out where exactly it is hanging inside of quickfix.
>> The only thing I can currently see is that it hangs when I call stop.
>>
>> Tony
>>
>> Oren Miller wrote:
>>> First off, stop will call the logout method on all the sessions, so
>>> there is no need to do so yourself (though it wouldn't hurt anything
>>> if you did). Also, stop already has the following loop:
>>> for( int second = 1; second <= 10 && isLoggedOn(); ++second )
>>> process_sleep( 1 );
>>> The only place I can think where it would block is when it joins on
>>> the thread. Can you verify that this is where you the library is
>>> freezing?
>>> --oren
>>> On Apr 7, 2006, at 9:06 AM, Tony Weston wrote:
>>>> QuickFIX Documentation:
>>>> http://www.quickfixengine.org/quickfix/doc/html/index.html
>>>> QuickFIX Support: http://www.quickfixengine.org/services.html
>>>>
>>>> Hi Dave,
>>>>
>>>> Unfortunately, it hangs on the stop call so it will never reach the
>>>> while loop that waits for the logout. I'm not currently waiting for
>>>> a logout before calling stop, so putting this wait in after I call
>>>> logout and before I call stop may fix the problem for me.
>>>>
>>>> Thank you,
>>>> Tony
>>>>
>>>> Dave Linaker wrote:
>>>>> Hi Tony,
>>>>> Rather than calling logout and then stop (stop will logout anyway),
>>>>> have
>>>>> you tried calling stop and then waiting for the logout to complete?
>>>>> e.g:
>>>>> //stop the initiator
>>>>> initiator.stop();
>>>>> //wait for logout
>>>>> while(initiator.isLoggedOn())
>>>>> Thread.Sleep(500);
>>>>> //continue...
>>>>> Cheers
>>>>> Dave
>>>>> -----Original Message-----
>>>>> From: qui...@li...
>>>>> [mailto:qui...@li...] On Behalf Of
>>>>> tony weston
>>>>> Sent: 06 April 2006 19:43
>>>>> To: qui...@li...
>>>>> Subject: [Quickfix-developers] stopping initiator hangs application
>>>>> Hello,
>>>>> I've been using quickfix with great success, although I've came
>>>>> across a
>>>>> problem when trying to stop an initiator in VB .Net 2. When I call
>>>>> "stop" my application will frequently hang on this call. I've tried
>>>>> with version 1.11.1 and with using the automated builds for VS 8 under
>>>>> the developers section of the website, both having the same results.
>>>>> I'm also passing a value of "True" when calling the stop method to
>>>>> force
>>>>> close, but it still occasionally hangs. Before calling stop I call
>>>>> logout on my open session. Is there something that I'm doing
>>>>> incorrectly or another way to get around this problem?
>>>>> Thank you,
>>>>> Tony
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by xPML, a groundbreaking scripting
>>>> language
>>>> that extends applications into web and mobile media. Attend the live
>>>> webcast
>>>> and join the prime developer group breaking into this new coding
>>>> territory!
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
>>>>
>>>> _______________________________________________
>>>> Quickfix-developers mailing list
>>>> Qui...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>>>>
>>
>>
>
>
|
|
From: Dale W. <wil...@oc...> - 2006-04-07 18:20:58
|
Hi, Tony, If you copy the ATL header files from VC7 into the VC8 include directory I think you can build QF with VC8-express (I'm not at work today so I can't check the details.) Dale tony weston wrote: > QuickFIX Documentation: > http://www.quickfixengine.org/quickfix/doc/html/index.html > QuickFIX Support: http://www.quickfixengine.org/services.html > > Oren, > > I recently switched to calling logout before stop, thinking this was a > cleaner method. I will switch back to just calling stop. > > Unfortunately I'm using the Express Editions of VS, which doesn't allow > me to compile quickfix, due to a atlthunk.lib issue, it seems I need a > full copy of VS to compile quickfix. Due to this I can not step into > the debugger to find out where exactly it is hanging inside of quickfix. > The only thing I can currently see is that it hangs when I call stop. > > Tony > > Oren Miller wrote: >> First off, stop will call the logout method on all the sessions, so >> there is no need to do so yourself (though it wouldn't hurt anything >> if you did). Also, stop already has the following loop: >> >> for( int second = 1; second <= 10 && isLoggedOn(); ++second ) >> process_sleep( 1 ); >> >> The only place I can think where it would block is when it joins on >> the thread. Can you verify that this is where you the library is >> freezing? >> >> --oren >> >> On Apr 7, 2006, at 9:06 AM, Tony Weston wrote: >> >>> QuickFIX Documentation: >>> http://www.quickfixengine.org/quickfix/doc/html/index.html >>> QuickFIX Support: http://www.quickfixengine.org/services.html >>> >>> Hi Dave, >>> >>> Unfortunately, it hangs on the stop call so it will never reach the >>> while loop that waits for the logout. I'm not currently waiting for >>> a logout before calling stop, so putting this wait in after I call >>> logout and before I call stop may fix the problem for me. >>> >>> Thank you, >>> Tony >>> >>> Dave Linaker wrote: >>>> Hi Tony, >>>> Rather than calling logout and then stop (stop will logout anyway), >>>> have >>>> you tried calling stop and then waiting for the logout to complete? >>>> e.g: >>>> //stop the initiator >>>> initiator.stop(); >>>> //wait for logout >>>> while(initiator.isLoggedOn()) >>>> Thread.Sleep(500); >>>> //continue... >>>> Cheers >>>> Dave >>>> -----Original Message----- >>>> From: qui...@li... >>>> [mailto:qui...@li...] On Behalf Of >>>> tony weston >>>> Sent: 06 April 2006 19:43 >>>> To: qui...@li... >>>> Subject: [Quickfix-developers] stopping initiator hangs application >>>> Hello, >>>> I've been using quickfix with great success, although I've came >>>> across a >>>> problem when trying to stop an initiator in VB .Net 2. When I call >>>> "stop" my application will frequently hang on this call. I've tried >>>> with version 1.11.1 and with using the automated builds for VS 8 under >>>> the developers section of the website, both having the same results. >>>> I'm also passing a value of "True" when calling the stop method to >>>> force >>>> close, but it still occasionally hangs. Before calling stop I call >>>> logout on my open session. Is there something that I'm doing >>>> incorrectly or another way to get around this problem? >>>> Thank you, >>>> Tony >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by xPML, a groundbreaking scripting >>> language >>> that extends applications into web and mobile media. Attend the live >>> webcast >>> and join the prime developer group breaking into this new coding >>> territory! >>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >>> >>> _______________________________________________ >>> Quickfix-developers mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >>> >> >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Quickfix-developers mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
|
From: Kbo K. <kbo...@gm...> - 2008-04-16 14:12:51
|
Hi all, Is there any update to this issue? I've just come across the same problem, and this is the latest post I could find... Thanks in advance, Kbo |