-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Inbox.Receive always gives an ArgumentOutOfRangeException #1694
Comments
This is actual place where error occurs. It looks like measuring time left based on scheduler's monotonic clock isn't free of issues - my guess (unconfirmed) is that time resolution unit for monotonic clock is millisecond. Other question is: do we really have to put non-zero requirement on scheduler delay? @akkadotnet/core ? |
The InboxActor should reply a Status.Failure immediately if the delay is <= 0. The inbox default-timeout is 5s, to get this error, the timeout have to be set to 0s which would make the Inbox useless. @Oipo Did you change the default-timeout in the App.Config of your test application? |
@JeffCyr I've been using the following config. I didn't even know that there's a default-timeout option, let alone change it. |
I can reproduce the issue if I set the inbox timeout to 0s. This issue can also occur with the default setting (5s) if the InboxActor is jammed and can't process the message before the receive timeout. I'll create a Pull Request to address this issue, but there is still something weird with your system (either a 0s timeout or a jammed InboxActor). |
PR #1702 |
You're right that there's something else going on, I cannot reproduce the issue with just one instance running. As soon as a second one (the remote in /remoteactor) connects, the inbox shows the issue in my first post. Pardon me for not giving a proper test case. Thanks for the fix though. |
#1694 Added safe check in InboxActor when receive timeout is already expired
The following code always gives an exception on akka 1.0.6.
The text was updated successfully, but these errors were encountered: