Hello again, ok after digging some more its clear that the E_AGAIN or E_WOULDBLOCK error means that there are no connections available to open. That makes no sense because i opened 20 connections in a row, but only the first 6 are handled and then the following 6 and so on.
What could possibly delay the notification of new incoming connecions until another one is handled? On 05.09.2013 13:04, Benjamin Zeller wrote: > Hello, > > not sure if i just ran into a bug or if i do something wrong: > > Basically i have a QTcpServer accepting connections, after a connection > comes in a QTcpSocket is created and pushed to a workerthread to handle > it (moveToThread). > > But after 6 connections the QTcpServer stops accepting connections > (seems to be releated to receiving a EAGAIN error) until the first 6 > are served (but i openend 20 connections at once from my testcode). > > Then it continues with the next 6 and i'm pretty sure the mainloop is > not blocked, because when i pause with the debugger its always waiting > inside exec(). > > This happens on Linux, i did not test yet with other operating systems. > > Anyone ran into something similar? > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest