activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mtaylor <...@git.apache.org>
Subject [GitHub] activemq-artemis pull request: Allow configurable size for client ...
Date Tue, 15 Dec 2015 16:12:34 GMT
Github user mtaylor commented on the pull request:

    https://github.com/apache/activemq-artemis/pull/263#issuecomment-164811933
  
    Injecting the globalPool is the same as injecting the local pool on each ServerLocator...
 I can also add the ability to inject a global pool on the ActiveMQClient to make it simpler?
 The current API manages thread pools at the server locator level.  e.g. setThreadPoolMaxSize(final
int threadPoolMaxSize), I've extended that to allow a local pool to be injected also.  The
next step for me was to use this pool injection in the RA.  Changing the global pool imo adds
more complexity... what happens when the globalThreadPool is changed after a client is already
initialized?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message