[
https://issues.jboss.org/browse/WFLY-5290?page=com.atlassian.jira.plugin....
]
Kabir Khan commented on WFLY-5290:
----------------------------------
I was going to add a test to check the theory, but it seems that
AliasResourceTestCase.testAliasedResourceAndAttributeReadWriteFromAliased() already does
an add for /aliased=model (in addCore()), which then gets translated to /core=model, and
the add succeeds.
It has been a while since I last looked, but the problem to me appears to be in
SimpleAliasEntry. I also see this infinite loop using standalone-ha.xml when doing
/subsystem=jgroups/stack=tcp/transport=TRANSPORT:read-resource. The address returned by
AliasStepHandler's call to SimpleAliasEntry.convertToTargetAddress() is the same as
what is passed in. AliasStepHandler then adds a step for the 'real address'.
However, since that 'real address' is still the original alias address, that step
then resolves to AliasStepHandler again, and on and on it goes.
Adding JGroups stack seems to freeze the UI
-------------------------------------------
Key: WFLY-5290
URL:
https://issues.jboss.org/browse/WFLY-5290
Project: WildFly
Issue Type: Bug
Components: Clustering, Domain Management
Reporter: Jan Kašík
Assignee: Paul Ferraro
Priority: Critical
Fix For: 10.0.0.CR2
Adding new JGroups stack with randomly chosen (non existing) socket binding name results
in web console freeze.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)