[
https://issues.jboss.org/browse/AS7-5904?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on AS7-5904:
----------------------------------------------
Ladislav Thon <lthon(a)redhat.com> made a comment on [bug
901178|https://bugzilla.redhat.com/show_bug.cgi?id=901178]
Verified on EAP 6.1.0.ER3.
Given that we (EAP clustering QA) didn't file this bug, I've just verified the
presence of the patch. If Radim wants to verify this himself, I'm of course fine with
that :-)
CLONE - JGroups startup before ISPN startup causes HotRod connector
startup fail
--------------------------------------------------------------------------------
Key: AS7-5904
URL:
https://issues.jboss.org/browse/AS7-5904
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.3.Final (EAP)
Reporter: Radim Vansa
Assignee: Paul Ferraro
Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
HotRod connector startup often fails in JDG 6.1.0.ER2. This is caused by early
initialization of the JGroups stack, where the node can join cluster sooner than
Infinispan is properly initialized, specifically sooner than the JGroupsTransport class
initializes the JGroups channel and related RPC dispatcher.
In some early phase of startup each node with HotRod connector inserts data with key
nodeName/clusterName into __hotRodTopologyCache (this is a replicated one). The
PutKeyValueCommand is broadcasted to all nodes in the cluster, including the node which
joined the cluster but where the Infinispan has not started yet. As there is no RPC
dispatcher on the destination node, the message gets discarded, but source node requesting
GET_ALL reponses waits for the response for 4 minutes (default timeout) and then gets an
exception failing the HotRod connector.
--
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