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

PersistentScottyEngine.notifyProcessorPoolsOnResponse without effect when using PersistentLockManager #60

Closed
austermann opened this issue May 24, 2016 · 1 comment

Comments

@austermann
Copy link
Contributor

coppers PersistentLockManageruses org.copperengine.core.persistent.PersistentScottyEngine.notify(Response<?>, Connection) to notify the engine about its responses.
In turn notify(Response<?>, Connection) is called from outside of copper, so it does not know when the transaction is commited, thus it cannot notify the processor pools. If it would, it would maybe be too early to read the new data due to transaction isolation.

@austermann
Copy link
Contributor Author

We will introduce a new method org.copperengine.core.PersistentProcessingEngine.notifyProcessorPools() which will be called by the PersistentLockManager.

austermann pushed a commit that referenced this issue May 24, 2016
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

1 participant