You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Clebert Suconic <cl...@gmail.com> on 2016/10/04 19:46:25 UTC

Re: Artemis Core client-side threading

Just like in JMS, a ClientSession (or any object used within) is
supposed to belong to a thread.


if you have multiple threads, use multiple sessions.. or synchronize the use.


It's possible that some stuff was moved. it's hard to keep javadocs
and the docs in sync when methods like these are mentioned.

On Wed, Sep 28, 2016 at 2:58 AM, Marko Asplund <ma...@gmail.com> wrote:
> How does the Artemis client-side threading model work, especially with
> regard to thread safety?
> Can ClientSession and ClientProducer instances be safely shared across
> threads?
> It seems like MessageHandler thread pool size can be configured via
> ServerLocator.
>
> I've been reading the "Thread management" chapter in Artemis docs in
> https://activemq.apache.org/artemis/docs/1.4.0/thread-pooling.html.
>
> The document doesn't appear to be in sync with the API docs (wrt.
> ServerLocator + ClientSessionFactory).
> Based on the API docs it looks like the thread pool size mutators have been
> moved from ClientSessionFactory to ServerLocator.
>
> marko



-- 
Clebert Suconic