Description of problem:
Issue warning to user when she tries to set address-settings dead letter address and/or expiry address to non-existent destination in CLI client.
Version-Release number of selected component (if applicable):
EAP 6.2.0.ER3, HornetQ 2.3.8.Final
See #1014095 for related discussion.
Proper link: bug 1014095
I am not sure how we can fix this in the messaging component. HornetQ does not provide a way to tell if an address exists or not in their management API.
Once they add this, we can provide some checks when the user sets them in the address-settings.
I'm working on the implementation and there's a side effect on this.
the DLQ and Expiry are deployed through address settings which are using matching algorithms.
I'm implementing a listener on the address settings to verify it any time the settings have changed.
If you have a wrong address, it will throw the log.warn every time the settings are changed. Say if you deploy a new element all the queues will be validated again.
So, if you deploy a wrong address... say.. IDONTExist.. and later you deploy AD1.. AD2... AD3.. say 5 minutes apart... IDONTEXIST will be logged 3 times.
Anyone sees a problem on this approach?
Never mind, I will add a check and only throw the exception once for a given address
I meant the log.warn
Does that mean that if the user changes address-settings in WildFly's CLI client, she will only see the warn message in server log or are we gonna be able to get the warning to CLI client as well?
While I would prefer warning in CLI client too, if that's too much hassle I'm ok with it just being in the server log. In that case I would close this bug, since there won't be any work necessary on integration side, and we'll move this under bug 1014095
I'm doing it at the server's log...
I'm adding a method that Jeff can use to make it on the CLI.
@Clebert, awesome, thanks