You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
xwm1992
changed the title
Global flow control is not work in MessageTransferTask
[Bug] Global flow control is not work in MessageTransferTask
Dec 16, 2021
xwm1992
pushed a commit
to xwm1992/EventMesh
that referenced
this issue
Dec 27, 2021
* modify:optimize flow control in downstreaming msg
* modify:optimize stategy of selecting session in downstream msg
* modify:optimize msg downstream,msg store in session
* modify:fix bug:not a @sharable handler
* modify:downstream broadcast msg asynchronously
* modify:remove unneccessary interface in eventmesh-connector-api
* modify:fix conflict
* modify:add license in EventMeshAction
* modify:fix global flow control problem
closeapache#461
* modify:optimize flow control in downstreaming msg
* modify:optimize stategy of selecting session in downstream msg
* modify:optimize msg downstream,msg store in session
* modify:fix bug:not a @sharable handler
* modify:downstream broadcast msg asynchronously
* modify:remove unneccessary interface in eventmesh-connector-api
* modify:fix conflict
* modify:add license in EventMeshAction
* modify:fix global flow control problem
close#461
Bug Report
Describe the bug
The global flow control is not work,because the current logic exist problem.
The wrong way:
In this way, the send thread releases the token immediately after obtaining it.
The right way:
Current in
MessageTransferTask.java
:Current code in EventMesh is same with the wrong way.
The text was updated successfully, but these errors were encountered: