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
Another Bug In DataWriter #1116
Comments
Hi Samira, Thanks for reporting. Could you please explain how you managed to detect this bug? Did you experience it or did you analyze the code? Do you run hundreds of tests? Do you have a particular hardware? I ask this because I personally have never experienced this one bug. I will make sure that |
Hi Stephane, I have a testing tool that injects delays for the messages to simulate the real delays that may happen in a concurrent environment (when the program run on different machines or in different environment). However, it respects all the semantics of actor programs and Akka library. This tool is still under development; I will release it when it gets ready. Regards, |
I just pushed a fix. Could you try it out? |
Sure. I will try it and let you know if I have the same problem. However, On Tue, Apr 30, 2013 at 4:16 PM, Stephane Landelle <notifications@github.com
|
np, thanks a lot. I'll try to cut a new release for 1.4 next week and ship it. |
It seems that it has been resolved now. Thanks for fixing. On Tue, Apr 30, 2013 at 4:26 PM, Stephane Landelle <notifications@github.com
|
Cool, thanks for your prompt feedback! |
We discussed about reordering of records in the log file in issue #1088. But it seems that
the problem is more serious than just reordering the records in the
DataWriter
. Because of reordering of the messages sent from actions toTerminator
andDataWriter
, it is possible that theDataWriter
receives ascenarioMessage
after theFlush
message, If that happens, an exception is thrown indicating that theDataWriter
cannot accept thescenarioMessage
. The reason is that after receiving theFlush
message, theDataWriter
goes touninitialized
state.The text was updated successfully, but these errors were encountered: