Configure broker to check for expired messages every second in tests

[jeanouii]

Very simple test to valid expiration is serialized with HTTP protocol.
The test simply sends a message with TTL 100ms and waits 30s for the message to show up in the DLQ.
Unfortunately the broker side check happens every 30s, so on fast nodes, the receive returns before the broker actually sends the message to the DLQ.
Adding a policy to speed up the move to the DLQ. The test should also run way faster.

[cshannon]

LGTM, as a side note we really need to work on our configuration as it's such a pain to do simple stuff like this.

I've had discussions with @jbonofre and @mattrpav already about some options (we are planning to remove Spring or make it optional at least in AMQ 7) and for the embedded side of configuration like in our unit tests, using a builder pattern makes the most sense and I think would greatly improve things so hopefully we can work towards that soon.

[jbonofre]

Yes, that's clearly planned for ActiveMQ 7. We should use a configuration aggregator that clearly list and document all configurations.
Also the default configuration should be probably reviewed (again for AMQ 7 as it's potentially breaking change for users).

[jeanouii]

I agree that Spring does not bring much to us. But we have to deal with dependency updates, cve, etc.

Having a broker that we can build with a builder pattern, like it's been done on other projects I've been involved in, would be neat and helpful.

[jbonofre]

@jeanouii that's the PoC I started 😄

[jeanouii]

Loolks like it's green!

[jbonofre]

That's super nice !