You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to implement the SessionProxy to capture FIX Session Message (how to implement replicate to standby node) . However, it found the first FIX Logon Reply Message cannot be reached in SessionProxy.
It makes the archive on Online and Standby node not completely in sync.
The text was updated successfully, but these errors were encountered:
yung2004
changed the title
SessionWriter create from followerSession() not update the session sequence
SesssionProxy cannot hook the first Logon Response Message
Apr 17, 2023
It looks like the Framer can send some Logon and Logout messages on its own without going through SessionProxy. Which makes sense since the Framer exists at Engine level and the SessionProxy exists at Library level. But I'm not sure how to address this. Maybe it is possible to make the Framer fully passive?
In my case, I use InitialAcceptedSessionOwner#SOLE_LIBRARY but it looks like in case of a library timeout in engine, the engine acquires the session and allows itself to send Heartbeat or Logout without going through the library.
I tried to implement the SessionProxy to capture FIX Session Message (how to implement replicate to standby node) . However, it found the first FIX Logon Reply Message cannot be reached in SessionProxy.
It makes the archive on Online and Standby node not completely in sync.
The text was updated successfully, but these errors were encountered: