[
https://issues.apache.org/jira/browse/SHINDIG-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
GuoJiaqing updated SHINDIG-1877:
--------------------------------
Description:
I create some customized features (for example, feature A, feature B and
feature C) and want to register them into shindig. But by mistake, there is
dependency loop problem in these features (it means, for example feature A
depends on feature B, feature B depends on feature C and feature C depends on
feature A).
When starts server, I found shindig can't be started and there is not any error
message/log which could tell me what happened.
After some research, I found this is because FeatureRegistry can't handle
dependency loop correctly when it tries to complete dependency node graph for
loaded feature node. If there is dependency loop in the loaded features, the
process will be in dead loop without any error message/log.
So, I create a patch to resolve this problem. FeatureRegistry should do
dependency loop check before completing dependency node graph for every feature
node.
was:
I create some customized features (for example, feature A, feature B and
feature C) and want to register them into shindig. But by mistake, there is
dependency loop problem in these features (it means, for example feature A
depends on feature B, feature B depends on feature C and feature C depends on
feature A).
When starts server, I found shindig can't be started and there is not any error
message/log which could tell me what happened.
After some research, I found this is because FeatureRegistry can't handle
dependency loop correctly when it tries to complete dependency node graph for
every feature node. If there is dependency loop in the loaded features, the
process will be in dead loop without any error message/log.
So, I create a patch to resolve this problem. FeatureRegistry should do
dependency loop check before completing dependency node graph for every feature
node.
> FeatureRegistry can't handle dependency loop correctly.
> -------------------------------------------------------
>
> Key: SHINDIG-1877
> URL: https://issues.apache.org/jira/browse/SHINDIG-1877
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Affects Versions: 2.5.0-beta4
> Reporter: GuoJiaqing
> Priority: Minor
>
> I create some customized features (for example, feature A, feature B and
> feature C) and want to register them into shindig. But by mistake, there is
> dependency loop problem in these features (it means, for example feature A
> depends on feature B, feature B depends on feature C and feature C depends on
> feature A).
> When starts server, I found shindig can't be started and there is not any
> error message/log which could tell me what happened.
> After some research, I found this is because FeatureRegistry can't handle
> dependency loop correctly when it tries to complete dependency node graph for
> loaded feature node. If there is dependency loop in the loaded features, the
> process will be in dead loop without any error message/log.
> So, I create a patch to resolve this problem. FeatureRegistry should do
> dependency loop check before completing dependency node graph for every
> feature node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
