I'm not sure I'd categorize this as a bug necessarily. Folks may actually be relying on the existing behavior to notify them when something is configured improperly. In other words, it's a feature that the broker doesn't start when the divert's filter is incorrect. If the filter is incorrect and the broker starts then folks may not notice that the divert isn't actually working.
If we want to change this behavior I think we'd have to do it in the next major version (i.e. 3.0). Justin On Mon, Dec 23, 2024 at 9:57 AM Alexander Milovidov <milovid...@gmail.com> wrote: > Hi Team, > > Recently I have mentioned that ActiveMQ Artemis fails to start if it has an > incorrect filter in the divert configuration. It logs an AMQ224006 Invalid > filter error and does not start. > Expected behavior: server does not create a divert and start successfully. > For example, if invalid filter is specified in the queue configuration, it > does not lead to a non-operating state of the server. > > Is it an issue? I have not found a Jira, can I create it? > > > -- > Regards, > Alexander >
