-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
Running unsecured EAP 7.0.0 DR9 in standalone mode with standalone-full-ha profile
Can not create cluster connection in subsystem, messaging, defulat, clustering, connecitons. Connection-ref in creation window is form EAP 6 and now it is connection-name.
Unexpected HTTP response: 500
Request
{
"cluster-connection-address" => "jms",
"connector-ref" => "http-connector",
"discovery-group-name" => "dg-group1",
"forward-when-no-consumers" => false,
"use-duplicate-detection" => false,
"address" => [
("subsystem" => "messaging-activemq"),
("server" => "default"),
("cluster-connection" => "test")
],
"operation" => "add"
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0155: connector-name may not be null",
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
- clones
-
JBEAP-990 Can not create messaging clustering connection
-
- Closed
-