Details
-
Bug
-
Resolution: Done
-
Major
-
10.0.0.Final
-
None
Description
Say I take EAP 6.4 default standalone-full.xml and add a discovery group like this:
<subsystem xmlns="urn:jboss:domain:messaging:1.4"> <hornetq-server> ... <discovery-groups> <discovery-group name="my-discovery-group"> <group-address>224.0.1.105</group-address> <group-port>56789</group-port> </discovery-group> </discovery-groups> ... </hornetq-server> </subsystem>
This is the only change I make to the configuration file. Then I try to migrate the messaging subsystem, expecting a migration warning that I should use the socket-binding attribute.
The warning appears indeed:
[standalone@localhost:9999 /] /subsystem=messaging:migrate
{
"outcome" => "success",
"result" => {"migration-warnings" => [
"WFLYMSG0084: Can not migrate attribute group-address from resource [
(\"subsystem\" => \"messaging-activemq\"),
(\"server\" => \"default\"),
(\"discovery-group\" => \"my-discovery-group\")
]. Use instead the socket-binding attribute to configure this discovery-group.",
"WFLYMSG0084: Can not migrate attribute group-port from resource [
(\"subsystem\" => \"messaging-activemq\"),
(\"server\" => \"default\"),
(\"discovery-group\" => \"my-discovery-group\")
]. Use instead the socket-binding attribute to configure this discovery-group."
]}
}
But the resource addresses in the warning are wrong. They refer to the messaging-activemq subsystem, which clearly isn't what I'm migrating from, it's what I'm migrating to.
I understand from the code that the DMR structure of the old subsystem model is very close to the structure of the new subsystem model, which is why these warning are produced on an already translated structure, but it generates wrong warnings.
Attachments
Issue Links
- clones
-
-
- Verified
-
