Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SesssionProxy cannot hook the first Logon Response Message #481

Open
yung2004 opened this issue Apr 16, 2023 · 1 comment
Open

SesssionProxy cannot hook the first Logon Response Message #481

yung2004 opened this issue Apr 16, 2023 · 1 comment

Comments

@yung2004
Copy link

yung2004 commented Apr 16, 2023

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.

@yung2004 yung2004 changed the title SessionWriter create from followerSession() not update the session sequence SesssionProxy cannot hook the first Logon Response Message Apr 17, 2023
@pcdv
Copy link
Contributor

pcdv commented Feb 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants