Initiator hangs if stopping a second time #620
Replies: 3 comments · 1 reply
-
|
@ackleymi really need guidance here, tried recreating the initiator after stopping it but that's giving me a duplicate session id error so it's really not clear what's the proper way to do this with library now? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I am on v0.9.0 and facing the exact same issue, |
Beta Was this translation helpful? Give feedback.
-
|
I'm on the latest version v0.9.4 and also running into this issue. After the initiator has been stopped once and restarted, the second call to Stop hangs forever. |
Beta Was this translation helpful? Give feedback.
-
|
It seems like the best course of action here is to create a new initiator instance after each |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, we upgraded quickfix from 0.6.0 to 0.7.0 and seeing that calling
Stopon the initiator hangs the second time.Our app has a single initiator which we use for the entire app lifecycle, when we get a goodnight message we stop the initiator and then call
Startwhen the new day starts.So this worked with 0.6.0 but hangs with 0.7.0 at the end of the second day.
We tracked this break to this PR,
session.Stopis basically ignored on the second time, and we hang here:quickfix/initiator.go
Line 147 in 3bf2b87
This is because the session is not stopped and stays running.
It's unclear to me whether this is a bug, or if we're not utilizing the initiator correctly and the break is intentional? Are we only supposed to call
Start/Stoponce and recreate it each time?cc @ackleymi @shipa998
Beta Was this translation helpful? Give feedback.
All reactions