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? > > 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! Project responsible is over the top :-(. >> >> We saw 4 lines of this type: >> >> Line 41771: 2016-02-28 01:52:01,147 [ NioProcessor-2358] WARN >> ing.AbstractPollingIoProcessor$Processor run - Create a >> new selector. Selected is 0, delta = 0 >> >> Line 71754: 2016-02-28 04:27:14,918 [ NioProcessor-3238] WARN >> ing.AbstractPollingIoProcessor$Processor run - Create a >> new selector. Selected is 0, delta = 0 >> >> Line 74744: 2016-02-28 06:52:45,293 [ NioProcessor-4054] WARN >> ing.AbstractPollingIoProcessor$Processor run - Create a >> new selector. Selected is 0, delta = 0 >> >> Line 87830: 2016-02-28 17:24:35,806 [ NioProcessor-7346] WARN >> ing.AbstractPollingIoProcessor$Processor run - Create a >> new selector. Selected is 0, delta = 0 > > So clearly something else is wrong. If we were looping because the > select() exits immediately with no socket being active, we would have > way more of such messages. Here, it happens only from time to time. > > Now, reading teh various links you have provided, I wonder if the > problem is not in the JDK code itself... > > I'll investigate more tonite. > > Would you be ready to test a nightly build if I provide one ? > > Thanks ! > >