Bug 1018827

Summary: Misleading error message when no discovery-group-name nor static-connectors are set in core bridge
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Martin Svehla <msvehla>
Component: Web ConsoleAssignee: Heiko Braun <hbraun>
Status: CLOSED EOL QA Contact: Pavel Jelinek <pjelinek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: brian.stansberry, hbraun, hpehl, jkudrnac, msvehla
Target Milestone: DR0   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:46:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Svehla 2013-10-14 13:27:16 UTC
Description of problem:
When adding new core bridge, user is required to set one of discovery group or static connector. When the user tries to create new bridge in Profile -> Messaging -> Connections _> Bridges in console, but doesn't add any of those two attributes, the error message shown in notification message is:

Internal Server Error
{
    "outcome" => "failed",
    "failure-description" => "JBAS014704: '' is an invalid value for parameter discovery-group-name. Values must have a minimum length of 1 characters",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

However, when trying to create such bridge in CLI, user gets more descriptive error:
{
    "outcome" => "failed",
    "failure-description" => "JBAS011651: Operation must include parameter static-connectors or parameter discovery-group-name",
    "rolled-back" => true,
    "response-headers" => {"process-state" => "reload-required"}
}

Please show a same error in notification message in console. The one it's showing now might lead the user to think she needs to set discovery-group-name attribute.


Version-Release number of selected component (if applicable):
EAP 6.2.0.ER5

Comment 1 Brian Stansberry 2013-10-14 14:40:11 UTC
Can you post the CLI command(s) you used? That may be helpful for the console guys as they can compare the operations they generate to the working CLI equivalents.

Comment 2 Martin Svehla 2013-10-15 08:50:02 UTC
In CLI client:

cd /subsystem=messaging/hornetq-server=default/bridge
./test-bridge:add(queue-name=test.Queue,forwarding-address=forward.Queue)

results in
{
    "outcome" => "failed",
    "failure-description" => "JBAS011651: Operation must include parameter static-connectors or parameter discovery-group-name",
    "rolled-back" => true
}

Comment 3 Heiko Braun 2014-07-03 12:16:33 UTC
I have improved the form validation to respect the constraints.

Comment 6 Pavel Jelinek 2014-11-26 09:30:37 UTC
Should this still remain in POST state?

Comment 7 Jakub Cechacek 2014-12-09 15:29:51 UTC
Form validation is still not present in DR12. Only the error message displayed in notification center now matches the one from CLI. 

Without the validation, it is kind of a half-baked fix.