hn Lilley
>
> Data Management Chief Architect, Redpoint Global Inc.
>
> 888 Worcester Street, Suite 200 Wellesley, MA 02482
>
> *M: *+1 7209385761 <+1%207209385761> | john.lil...@redpointglobal.com
>
> *From:* Clebert Suconic
> *Sent:* Friday, November 11, 2022 8:1
al.com<mailto:john.lil...@redpointglobal.com>
From: John Lilley
Sent: Saturday, November 12, 2022 9:58 AM
To: users@activemq.apache.org
Subject: RE: Multi-threaded consumers in AMQ classic vs Artemis
*** [Caution] This email is from an external source. Please use caution
responding, opening at
Sent: Friday, November 11, 2022 8:19 AM
To: users@activemq.apache.org
Subject: Re: Multi-threaded consumers in AMQ classic vs Artemis
*** [Caution] This email is from an external source. Please use caution
responding, opening attachments or clicking embedded links. ***
The thread pool on the cl
The thread pool on the client is just for executors and other shared
threads.
Like if you have a MessageListener, the client will call an
executor.execute(); when a listener is called.
So if you have multiple connections on your client (from different
connection factories) we wouldn't be creat
Greetings,
We are using AMQ/Artemis to build a set of RPC-style services. We discovered
that Artemis (by default) uses a global thread pool for all consumers, whereas
AMQ classic created a new thread every time we make a consumer and call
setMessageListener(). At least I think that’s what hap
