> 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 compatibility and just adding a new
one. In any case, the long story short is that the new parameter was added
to support use-cases where your application was pressing on the limits of
the global thread pool and was also using a very low (or zero)
consumerWindowSize. I would categorize this as a very rare use-case. The
default flow-control thread-pool size of 10 should cover 99% of use-cases.

> Is there anything to the jms -> jakarta client change other than the
package and dependency names?

No.


Justin

[1] https://issues.apache.org/jira/browse/ARTEMIS-4522

On Wed, Mar 13, 2024 at 1:45 PM John Lilley
<john.lil...@redpointglobal.com.invalid> wrote:

> 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 honestly I cannot
> remember why we thought this was necessary.  Can someone explain or point
> me to a page that shows the defaults and talks about why you’d want to
> change this?
>
>
>
> PS: Is there anything to the jms -> jakarta client change other than the
> package and dependency names?  It seems like the same/same replacement of
> other javax dependencies like jaxb-api.
>
>
>
> Thanks
>
> John
>
>
>
>
>
>
>
> [image: rg] <https://www.redpointglobal.com/>
>
> John Lilley
>
> Data Management Chief Architect, Redpoint Global Inc.
>
> 34 Washington Street, Suite 205 Wellesley Hills, MA 02481
>
> *M: *+1 7209385761 <+1%207209385761> | john.lil...@redpointglobal.com
>
> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is
> confidential and is intended solely for the use of the individual(s) to
> whom it is addressed. If you believe you received this e-mail in error,
> please notify the sender immediately, delete the e-mail from your computer
> and do not copy, print or disclose it to anyone else. If you properly
> received this e-mail as a customer, partner or vendor of Redpoint, you
> should maintain its contents in confidence subject to the terms and
> conditions of your agreement(s) with Redpoint.
>

Reply via email to