Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 3.4.3.Final
Affects Version/s: 3.4.1.Final
Component/s: Subsystem Configuration
Labels:
None

Steps to Reproduce:
Hide

Run the EAP server

bin/standalone.sh -c standalone-full-ha.xml

Go to Configuration -> Messaging (ActiveMQ) -> Server -> Clustering and press view or http://127.0.0.1:9990/console/index.html#messaging-server-clustering;server=default

When discovery group is selected click on add button

Fill the name in form and click on add

After this error appear
Show
Run the EAP server bin/standalone.sh -c standalone-full-ha.xml Go to Configuration -> Messaging (ActiveMQ) -> Server -> Clustering and press view or http://127.0.0.1:9990/console/index.html#messaging-server-clustering;server=default When discovery group is selected click on add button Fill the name in form and click on add After this error appear
Git Pull Request:
https://github.com/hal/console/pull/499, https://github.com/hal/console/pull/500

When trying create new discover group on messaging server this error appear [1]. To create discover group it's needed specify socket-binding or Jgroup cluster. When this attribute not specified the discovery group can't be created. Web console have only name attribute and one of these so the creating new fail.

When JBEAP-4530 was updated to not need only name the web console did not include this change.

[1]

Failed to add resource test, cause: "WFLYCTL0155: 'socket-binding' may not be null"

clones

JBEAP-23042 Messaging ActiveMQ server can't creat discovery group in web console

Verified

is incorporated by

WFLY-15894 Upgrade HAL to 3.4.4.Final

Resolved

WFLY-15917 Upgrade HAL to 3.4.4.Final

Closed

Assignee:: Tomas Hofman

Reporter:: Tomas Hofman

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/01/12 11:14 AM

Updated:: 2022/01/13 11:38 AM

Resolved:: 2022/01/12 7:31 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates