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.

Sign up for GitHub

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

Jump to bottom

AbstractWire.tryMoveToEndOfQueue no longer behaving as expected #64

Closed
JerryShea opened this issue Jan 24, 2018 · 3 comments
Closed

AbstractWire.tryMoveToEndOfQueue no longer behaving as expected #64

JerryShea opened this issue Jan 24, 2018 · 3 comments
Assignees
@RobAustin

Comments

@JerryShea
Copy link
Contributor

the "fast path" is no longer being invoked and so we can't take advantage of this optimisation any more
@RobAustin
Copy link
Contributor

Thanks for raising this, can you tell me why the fast path is no longer invoked ?

@JerryShea
Copy link
Contributor Author

This is actually a problem in queue - see OpenHFT/Chronicle-Queue#426

@hft-team-city
Copy link
Collaborator

Released in Chronicle-Wire-2.20.101, BOM-2.20.134

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RobAustin RobAustin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@RobAustin @hft-team-city @JerryShea