[JBoss JIRA] (ISPN-2371) The global component registry sometimes fails to start components injected on the fly
8:38 a.m.
Dan Berindei created ISPN-2371:
----------------------------------
Summary: The global component registry sometimes fails to start components
injected on the fly
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in incoming
CacheTopologyControlCommands. Since these commands are broadcasted to the entire cluster,
a node can receive them before it had finished starting its global component registry.
--
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
7 a.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2371:
-------------------------------------
do we have a workaround for this or is this causing random startup failures?
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
5:55 a.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2371:
------------------------------------
We would work around this by forcing the registration of the ClusterTopologyManager and
the LocalTopologyManager on startup, similar to the way it's done for Transport in the
GlobalComponentRegistry constructor:
{noformat}
getOrCreateComponent(Transport.class);
{noformat}
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
7:43 a.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-2371:
-----------------------------------
Actually I have found this problem several times (or if I may suspect it from a long time
of no activity in logs preceded by "Ignoring consistent hash update X for cache X,
the local cache manager is not running" messages. Should I try to provide more logs
from builds failed due to this issue?
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
9:14 p.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2371:
--------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
7:31 a.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2371:
-------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1423
Pull request with the workaround only, please leave the bug open.
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
4:25 a.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2371:
-------------------------------------
[~dan.berindei]pull request is now integrated.
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
8:07 p.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2371:
--------------------------------
Fix Version/s: 6.0.0.Final
(was: 5.2.0.Final)
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 6.0.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
8:07 p.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2371:
--------------------------------
Priority: Major (was: Critical)
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 6.0.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
8:09 p.m.
[
https://issues.jboss.org/browse/ISPN-2371?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2371:
-------------------------------------
[~dan.berindei]moved this to 6.0 and downgraded the priority given that we have a
workaround integrated.
The global component registry sometimes fails to start components
injected on the fly
-------------------------------------------------------------------------------------
Key: ISPN-2371
URL: https://issues.jboss.org/browse/ISPN-2371
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta1
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 6.0.0.Final
If a global component is used by an incoming command, it could be created before the
component registry is in the "running" state, yet after it has started invoking
the components' start methods.
If this happens, the component's start method(s) will never be invoked - neither
"inline", in ACR.registerComponentInternal, nor in the regular startup procedure
(ACR.internalStart).
Specifically, the problem ocurred with LocalTopologyManager, which is injected in
incoming CacheTopologyControlCommands. Since these commands are broadcasted to the entire
cluster, a node can receive them before it had finished starting its global component
registry.
--
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
4719
days inactive
4745
days old
infinispan-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Dan Berindei (JIRA) -
Mircea Markus (JIRA)
-
Radim Vansa (JIRA)