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

Another Bug In DataWriter #1116

Closed
samira-t opened this issue Apr 30, 2013 · 7 comments
Closed

Another Bug In DataWriter #1116

samira-t opened this issue Apr 30, 2013 · 7 comments
Assignees
Milestone

Comments

@samira-t
Copy link

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 to Terminator and DataWriter, it is possible that the DataWriter receives a scenarioMessage after the Flush message, If that happens, an exception is thrown indicating that the DataWriter cannot accept the scenarioMessage. The reason is that after receiving the Flush message, the DataWriter goes to uninitialized state.

@slandelle
Copy link
Member

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 ScenarioMessages can't be lost. However, I wonder if we can really have a design where we can guarantee that we don't lose RequestMessages.

@ghost ghost assigned slandelle Apr 30, 2013
@samira-t
Copy link
Author

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,
Samira

@slandelle
Copy link
Member

I just pushed a fix. Could you try it out?

@samira-t
Copy link
Author

Sure. I will try it and let you know if I have the same problem. However,
it might not in the next few days since I am a bit busy now.

On Tue, Apr 30, 2013 at 4:16 PM, Stephane Landelle <notifications@github.com

wrote:

I just pushed a fix. Could you try it out?


Reply to this email directly or view it on GitHubhttps://github.com//issues/1116#issuecomment-17254671
.

@slandelle
Copy link
Member

np, thanks a lot. I'll try to cut a new release for 1.4 next week and ship it.

slandelle pushed a commit that referenced this issue Apr 30, 2013
@samira-t
Copy link
Author

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

wrote:

np, thanks a lot. I'll try to cut a new release for 1.4 next week and ship
it.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1116#issuecomment-17255281
.

@slandelle
Copy link
Member

Cool, thanks for your prompt feedback!

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

No branches or pull requests

2 participants