I think removing it is a good idea and dont expect removing it now would actually be a big issue, however given it has been there for so long I also dont see that it urgently needs to go away now. Anyone that doesnt want it there already has simple ways to prevent it being there, so I'd probably just remove it in a 3.0 personally (neednt be all that far away either, i.e relatively speaking there's not much time diff overall). Perhaps just raise a Jira to track the task? At least anyone following those would see the intent.
On Wed, 7 Aug 2024 at 04:43, Clebert Suconic <[email protected]> wrote: > > I just realized we still create the following acceptor on every server we > start: > > > <!-- HornetQ Compatibility Acceptor. Enables HornetQ Core > and STOMP for legacy HornetQ clients. --> > > <acceptor > name="hornetq">tcp://0.0.0.0:5445?anycastPrefix=jms.queue.;multicastPrefix=jms.topic.;protocols=HORNETQ,STOMP;useEpoll=true</accept > > > > > And I think we should stop. 61616 would still respond to HornetQ > protocol. It just don't make sense (for a few. years already .. don't > know how we missed) to keep this acceptor. > > > I think we should switch the defaults on the CLI create to have it off > by default, and add a new parameter as --enable-hornetq-acceptor. > > -- > Clebert Suconic > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > For further information, visit: https://activemq.apache.org/contact > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
