[Boost-users] [asio] async write handler is not called until the socket is not closed

Subject: [Boost-users] [asio] async write handler is not called until the socket is not closed
From: Roman Shmelev (rshmelev_at_[hidden])
Date: 2009-04-30 03:52:05

Hi!

I've got very strange problem - handler passed to async_write is not
called in time.
What I mean - it is called only when socket is closed - then handler
is invoked many times.
Sometimes it is so, sometimes everything is fine.
The main thing is that traffic exists. I mean - async writes get
completed. I call io_service.run() in proper time, etc.
Another moment - the first two times the handler is invoked, but not more.

As I guess, the problem is somewhere in my code.
But I ask you to point to probable reasons of such behaviour that
breaks asio rules..