Home/ Questions/Q 933221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T20:47:43+00:00

I’ve made a simple dummy server/dummy client program using IOCP for some testing/profiling purpose.

  • 0

I’ve made a simple dummy server/dummy client program using IOCP for some testing/profiling purpose. (And I also wanted to note that I’m new to asynchronous network programming)

It looks like the server works well with original client, but when the dummy client tries to connect to the server with ConnectEx function, IOCP Worker thread still gets blocked by GetQueuedCompletionStatus function and never returns result while the server succeeds in accepting the connection.

What is the problem and/or the reason, and how should I do to solve this problem?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Even after you associate your accepted socket to IOCP, your worker thread will remain blocked on GetQueuedCompletionStatus untill you post an “unlocking” completion event.
    Completion events for receive/write operation wo’nt be sent by the system unless you “unlock” your new socket.
    For details ckeck the source code of Push Framework http://www.pushframework.com It is a C++ network application framework using IOCP.
    The “unlocking” trick exists in the “IOCPQueue” class.

    • 0