Re: We still experience DIRMINA-1006 despite using 2.0.13

Hi, have you been able to find a cause for that? Yes, we could test a nightly! Tnx, Buddy Am 29.02.2016 um 19:46 schrieb Emmanuel Lécharny: > Le 28/02/16 18:00, Buddy Butterfly a écrit : >> Hi, >> >> if I understand it correct, you are telling me that there

Re: We still experience DIRMINA-1006 despite using 2.0.13

run - Create a new selector. Selected is 0, delta = 0 What would be a workaround? Tnx a lot! Buddy Am 28.02.2016 um 11:33 schrieb Emmanuel Lécharny: > Le 27/02/16 18:08, Buddy Butterfly a écrit : >> Obviously netty fixed this with a workaround. > > Thanks for

Re: We still experience DIRMINA-1006 despite using 2.0.13

Obviously netty fixed this with a workaround. Am 27.02.2016 um 18:06 schrieb Buddy Butterfly: > > This bug from netty seesm to be related: > > https://github.com/netty/netty/issues/3857 > > Am 27.02.2016 um 17:38 schrieb Buddy Butterfly: >> Am 26.02.2016 um 13:03 s

Re: We still experience DIRMINA-1006 despite using 2.0.13

This bug from netty seesm to be related: https://github.com/netty/netty/issues/3857 Am 27.02.2016 um 17:38 schrieb Buddy Butterfly: > Am 26.02.2016 um 13:03 schrieb Emmanuel Lécharny: >> Le 26/02/16 12:07, Buddy Butterfly a écrit : >>> Hi, >>> >>> we still e

Re: We still experience DIRMINA-1006 despite using 2.0.13

Am 26.02.2016 um 13:03 schrieb Emmanuel Lécharny: > Le 26/02/16 12:07, Buddy Butterfly a écrit : >> Hi, >> >> we still experience isse DIRMINA-1006. We have an RFID device that >> rejects connections when connection limit is reached. Our mina client >> thread t

We still experience DIRMINA-1006 despite using 2.0.13

Hi, we still experience isse DIRMINA-1006. We have an RFID device that rejects connections when connection limit is reached. Our mina client thread then goes into 100% cpu usage. Any idea if the patch maybe did not cover the all situations? Cheers, Buddy