Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-03-10 Thread Buddy Butterfly
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 will be no >> sultion for it? > >

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-29 Thread 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 will be no > sultion for it? Did I say that ??? > Or did I get it wrong. Probably... I'm just trying to see what could be the root cause. > This problem strikes > us heavily!

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-28 Thread Buddy Butterfly
Hi, if I understand it correct, you are telling me that there will be no sultion for it? Or did I get it wrong. I am lost. This problem strikes us heavily! Project responsible is over the top :-(. We saw 4 lines of this type: Line 41771: 2016-02-28 01:52:01,147 [ NioProcessor-2358]

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-28 Thread Emmanuel Lécharny
Le 27/02/16 18:08, Buddy Butterfly a écrit : > Obviously netty fixed this with a workaround. Thanks for the interesting analysis and pointers. It seems that in some case, we are still looping on the select(). Can you do one more thing to confirm that it's teh real problem ? Set the log to WARN,

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-27 Thread Buddy Butterfly
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 schrieb Emmanuel Lécharny:

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-27 Thread 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 schrieb Emmanuel Lécharny: >> Le 26/02/16 12:07, Buddy Butterfly a écrit : >>> Hi, >>> >>> we still experience isse DIRMINA-1006. We have

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-27 Thread 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 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

Re: We still experience DIRMINA-1006 despite using 2.0.13

2016-02-26 Thread 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 then goes into 100% cpu usage. Any idea if the patch maybe > did not cover the all situations?

We still experience DIRMINA-1006 despite using 2.0.13

2016-02-26 Thread Buddy Butterfly
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