Node cannot re-join cluster after restart if ASYM_ENCRYPT used in JGroups stack
Issue
- With two servers running in a domain, at the first startup the 2nd node joins the cluster successfully.
After restarting any node in the cluster, via the CLI, the node is no longer able to re-join the cluster.- If
ASYM_ENCRYPTis commented out from the JGroups stack, in the domain.xml, the restart works i.e. node successfully joins
- If
JGroups snippet
<subsystem xmlns="urn:jboss:domain:jgroups:4.0">
<channels default="ee">
<channel name="ee" stack="tcpping"></channel>
</channels>
<stacks>
<stack name="tcpping">
.. .. ..
<protocol type="VERIFY_SUSPECT"></protocol>
<protocol type="ASYM_ENCRYPT">
<property name="encrypt_entire_message">true</property>
<property name="sym_keylength">128</property>
<property name="sym_algorithm">AES/ECB/PKCS5Padding</property>
<property name="asym_keylength">512</property>
<property name="asym_algorithm">RSA</property>
</protocol>
<protocol type="pbcast.NAKACK2"></protocol>
<protocol type="UNICAST3"></protocol>
<protocol type="pbcast.STABLE"></protocol>
<protocol type="AUTH">
<property name="auth_class">org.jgroups.auth.MD5Token</property>
<property name="auth_value">change_it_soon</property>
<property name="token_hash">MD5</property>
</protocol>
<protocol type="pbcast.GMS"></protocol>
.. .. ..
</stack>
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.0.0 -> 7.0.8
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
