[
https://issues.jboss.org/browse/JGRP-2152?page=com.atlassian.jira.plugin....
]
Richard Achmatowicz edited comment on JGRP-2152 at 1/16/17 10:54 AM:
---------------------------------------------------------------------
I re-ran my first test, this time using JGroups 3.6.12 with the current master version of
Wildfly (11.0.0.Alpha1) and the same CDIFailoverTestCase now passes, along with all the
other clustering tests.
I attach the log as
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output-clean.txt
So, it looks as though the fix in 3.6.12 for [1] works with Wildfly. I will be also adding
a basic security test to the Wildfly testuite to catch such basic errors in future.
I'll provide the link here when completed.
I'll now run the same test with 10.1.0.Final to check that the issue is fixed there
too.
was (Author: rachmato):
I re-ran my first test, this time using JGroups 3.6.12 with the current master version of
Wildfly (11.0.0.Alpha1) and the same CDIFailoverTestCase now passes, along with all the
other clustering tests.
I attach the log as
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output-clean.txt
So, it looks as though the fix in 3.6.12 for [1] works with Wildfly. I will be also adding
a basic security test to the Wildfly testuite to catch such basic errors in future.
I'll provide the link here when completed.
ASYM_ENCRYPT failure on Wildfly 10.1.0
--------------------------------------
Key: JGRP-2152
URL:
https://issues.jboss.org/browse/JGRP-2152
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.10
Reporter: Matt Wringe
Assignee: Bela Ban
Fix For: 4.0, 3.6.13
Attachments: hawkular-metrics-1.log, hawkular-metrics-2.log,
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output-clean.txt,
org.jboss.as.test.clustering.cluster.cdi.CdiFailoverTestCase-SYNC-tcp-output.txt,
standalone.xml
Using ASYM_ENCRYPT on Wildfly 10.1.0 seems to be broken.
I am using the parameters for ASYM_ENCRYPT specified in
http://www.jgroups.org/manual/index.html#Security
Note: running with SYM_ENCRYPT doesn't cause any issues and it works fine with my
setup. Its only ASYM_ENCRYPT which is currently failing.
Note: running this on EAP fails in a similar manner.
Eg:
<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>
If I run a single instance, then I don't see any problems appear in the logs. Its
when I start a second instance that I start to see errors about unrecognised ciphers and
timeouts.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)