-
Bug
-
Resolution: Done
-
Major
-
None
-
8.0.0.Beta
-
None
In EAP 7.4 adding connector in messaging-activemq subsystem requires reload to be created but it could be referenced from other parts of messaging-activemq subsystem (for example in configuration of core bridge) without server being reloaded. This has changed in EAP 8 and now server must be reloaded before it's used in other parts of messaging-activemq subsystem.
CLI example on EAP 8 without reload:
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/http-connector=connector:add(endpoint=http-acceptor,socket-binding=messaging) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/bridge=bridge:add(static-connectors=[connector],queue-name=jms.queue.SourceQueue, forwarding-address=jms.queue.TargetQueue) { "outcome" => "failed", "failure-description" => "WFLYMSGAMQ0106: The bridge bridge didn't deploy.", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} }
CLI example on EAP 8 with reload:
[standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/http-connector=connector:add(endpoint=http-acceptor,socket-binding=messaging) { "outcome" => "success", "response-headers" => { "operation-requires-reload" => true, "process-state" => "reload-required" } } [standalone@localhost:9990 /] :reload { "outcome" => "success", "result" => undefined } [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/bridge=bridge:add(static-connectors=[connector],queue-name=jms.queue.SourceQueue, forwarding-address=jms.queue.TargetQueue) {"outcome" => "success"}
- is related to
-
WFLY-18237 Adding a connector shouldn't require to reload
-
- Closed
-
- relates to
-
EAPDOC-1386 Documentation updates for JBEAP-25310
-
- Closed
-
- mentioned on
