[
https://issues.apache.org/jira/browse/SCB-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442163#comment-16442163
]
ASF GitHub Bot commented on SCB-503:
------------------------------------
coveralls commented on issue #657: [SCB-503]Fix stateful access problem and
resource leak issue related to WeighedResponseTimeRule
URL:
https://github.com/apache/incubator-servicecomb-java-chassis/pull/657#issuecomment-382318550
[](https://coveralls.io/builds/16573156)
Coverage increased (+0.009%) to 87.449% when pulling
**c612977f1a76180143b4a149847189cd4dba0426 on liubao68:config** into
**41049be9d9b41d32fbdf4e12f613d6e85ab21301 on apache:master**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> When using WeighedResponseTimeRule, there are some initialize and stateless
> access problems
> -------------------------------------------------------------------------------------------
>
> Key: SCB-503
> URL: https://issues.apache.org/jira/browse/SCB-503
> Project: Apache ServiceComb
> Issue Type: Bug
> Reporter: liubao
> Assignee: liubao
> Priority: Major
>
> 1. When creating WeighedResponseTimeRule, it will call loadbalance get all
> service lists. And when running, it also starts a deamon to maintain states
> and also call loadbalance get all service lists. So any state access to
> 'invocation' will cause problem.
> Any filter rules will avoid to use invocation for stateful filters.
>
> 2. when change WeighedResponseTimeRule to RoundRobin, it's deamon task is not
> destroyed and may cause resource leak if change laodbalance rule from to this
> frequently.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
