Hi Frédéric,
Sorry for getting back to you late. I was busy implementing JMX
integration. I bet you will like it. I will also look forward to
your feed back ;)
On Nov 23, 2007 5:10 PM, Frédéric Brégier <[EMAIL PROTECTED]> wrote:
> Now in trunk, NioSocketConnector and NioSocketAcceptor
> use Si
Hi Trustin,
Well you go so fast !! I didn't download again trunk right now (but will !).
In fact, I was probably not enough precise.
Let me say it again, because I feel like I mixed two things.
I agree NewThreadExecutor was a "simple" pool of thread since it was not
(until few hours) a real pool of
On Nov 23, 2007 3:06 PM, Trustin Lee <[EMAIL PROTECTED]> wrote:
> Hi Frédéric,
>
> On Nov 23, 2007 7:53 AM, Frédéric Brégier <[EMAIL PROTECTED]> wrote:
> > Hi Maarten,
> >
> > Correct me if I am missing something.
> > dispose() seems to release all ressources from the IoService (or
> > connector),
Hi Frédéric,
On Nov 23, 2007 7:53 AM, Frédéric Brégier <[EMAIL PROTECTED]> wrote:
> Hi Maarten,
>
> Correct me if I am missing something.
> dispose() seems to release all ressources from the IoService (or connector),
> so when you don't need anymore the
> connector.
> setWorkerTimeout() was inten
Hi Maarten,
Correct me if I am missing something.
dispose() seems to release all ressources from the IoService (or connector), so
when you don't need anymore the
connector.
setWorkerTimeout() was intend to release one thread only inside the pool of
threads after the specified timeout
after no
Hello Frederic,
try connector.dispose();
http://mina.apache.org/report/trunk/apidocs/org/apache/mina/common/IoService.html#dispose()
Maarten
On Nov 22, 2007 6:53 PM, Frédéric Brégier <[EMAIL PROTECTED]> wrote:
> Hi Trustin and all !
> In the past in trunk (6 month ago) we had :
> connector.set
