Re: ActiveMQClient.setGlobalThreadPoolProperties

> Can someone explain or point me to a page that shows the defaults and talks about why you’d want to change this? This parameter was added via ARTEMIS-4522 [1] and it was my mistake to modify the existing setGlobalThreadPoolProperties method rather than keeping the existing one for backwards comp

ActiveMQClient.setGlobalThreadPoolProperties

Greetings, We recently upgraded the client and changed JMS to Jakarta. In doing so I noticed that ActiveMQClient.setGlobalThreadPoolProperties() has another argument for he flow-control thread pool size. We are currently calling this as ActiveMQClient.setGlobalThreadPoolProperties(1000,5) but

Artemis management console stops responding with exceptions in io.hawt.web.auth.AuthenticationFilter

Hi Team, We have ActiveMQ Artemis server in the test environment, and sometimes management console of this server becomes unresponsive. Users report that they get connection timeout when opening web page of management console. At the same time broker is working, messages are sent/consumed. When