Thanks
I have this in my code:
config.getFilterChain().addLast("executor",
new ExecutorFilter(new ThreadPoolExecutor(50, 400, 5 * 60 + 100,
TimeUnit.SECONDS, new LinkedBlockingQueue<Runnable>())));
Also, I have
set acceptor.getDefaultConfig().setThreadModel(ThreadModel.MANUAL), beside
this executor I have another thread pool that actually executed tasks. I
suppose that ExecutorFilter, the first one, is for Worker that reads/writes
messages in MINA? Is this an architecture you suggested? Is there any
difrence if the second pool is not implemented as ExecutorFilter ?
Thanks
Zlaja
On Sat, Jun 29, 2013 at 7:40 PM, Julien Vermillard <[email protected]>wrote:
> Separated thread pool for those long I/O task is a good idea.
> As jon stated, executor filter can match too.
>
> --
> Julien Vermillard :::: http://people.apache.org/~jvermillard/
>
>
> On Fri, Jun 28, 2013 at 10:28 PM, Jon <[email protected]> wrote:
> > You could have used the executor filter to do this. All depends on the
> lengths you want to go through for difference performance profiles.
> >
> > Sent from my iPhone
> >
> > On Jun 28, 2013, at 1:11 PM, Zlatko Josic <[email protected]>
> wrote:
> >
> >> Hi,
> >>
> >> We created server based on MINA framework. Every request has logic that
> >> writes to database.
> >> We creates separated thread pool for these taks.
> >> This means that MINA's worker thread pool submits taks to our pool where
> >> they are executed.
> >> Is this good approach ?
> >>
> >> Thanks
> >>
> >> Zlaja
>
