Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

Server does not receive notification of last message. #1

Closed
DJGosnell opened this issue Aug 10, 2016 · 2 comments
Closed

Server does not receive notification of last message. #1

DJGosnell opened this issue Aug 10, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@DJGosnell
Copy link
Member

Postmaster will sometimes not be signaled from the session inbox due to being called at the same moment as the reading loop completes and the dictionary still contains the inbox instance. This has the effect of the inbox retaining inbox bytes and the postmaster does not know about it so they remain unpressed until another write from the client to the server.

DJGosnell added a commit that referenced this issue Aug 11, 2016
Started work on refactoring to remove time lag referenced in issue #1
DJGosnell added a commit that referenced this issue Aug 11, 2016
@DJGosnell
Copy link
Member Author

Fixed in recent commits.

DJGosnell added a commit that referenced this issue Sep 8, 2016
Finally fixed long standing bug for issue #1.
@DJGosnell DJGosnell reopened this Sep 16, 2016
@DJGosnell
Copy link
Member Author

Issue still exists.

@DJGosnell DJGosnell added this to the 1.0 milestone Sep 16, 2016
@DJGosnell DJGosnell added the bug label Sep 16, 2016
@DJGosnell DJGosnell self-assigned this Sep 16, 2016
DJGosnell added a commit that referenced this issue Sep 18, 2016
… SmartThreadPool threads.

Fixed issue #1 hopefully for good.
Added configurations to limit the concurrent execution threads for the Rpc client & server.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant