Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>io_service</code> is never returning because there is always work in the <code>io_service</code>. When <a href="http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/reference/basic_socket_acceptor/close/overload1.html" rel="nofollow"><code>acceptor::close()</code></a> is invoked, the <code>acceptor</code>'s asynchronous accept operations will be cancelled immediately. The handlers for these cancelled operations will be passed the <code>boost::asio::error::operation_aborted</code> error.</p> <p>In the current code, the problem is the result of a new asynchronous accept operation always being initiated, even if the <code>acceptor</code> has been closed. Thus, work is always being added to the <code>io_service</code>.</p> <pre><code>void start_accept(){ // If the acceptor is closed, handle_accept will be ready to run with an // error. acceptor_.async_accept(..., handle_accept); } void handle_accept(const system::error_code&amp; error){ if(!error) { connection-&gt;start(); } // Always starts a new async accept operation, even if the acceptor // has closed. start_accept(); } void handle_stop(){ acceptor_.close(); } </code></pre> <p>The Boost.Asio examples prevents this from occurring checking if <code>acceptor_</code> has been closed in the <code>handle_accept</code> call. If the <code>acceptor_</code> is no longer open, then the handler returns early without adding more work to the <code>io_service</code>.</p> <p>Here is the relevant snippet from from the <a href="http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/example/http/server/server.cpp" rel="nofollow">HTTP Server 1</a> example:</p> <pre><code>void server::handle_accept(const boost::system::error_code&amp; e) { // Check whether the server was stopped by a signal before this completion // handler had a chance to run. if (!acceptor_.is_open()) { return; } if (!e) { connection_manager_.start(new_connection_); } start_accept(); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POboost::asio io_service doesn't return after stop()
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USTanner Sansbury
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThat sounds good but even after those changes the io_service still doesn't return. When I try to debug whats happening when handle_stop() is called the whole program just quits either after calling acceptor_.close() or printf() (same problem I described above). Just for testing purposes I only used one server object but the problem still occurs, even if nothing happened yet (no clients connected). Oh and the handlers are also not called when calling acceptor_.close() from what I can tell.
      singulars
      1. PO
      1. USuser2047610
    2. CO@user2047610: It sounds as though you are invoking undefined behavior in code that is not posted. Based on the calls, I would suggest verifying that the `TcpConnection` instance is outliving all of the handlers to which it is bound. Make sure it is publicly inheriting from `enable_shared_from_this<TcpConnection>` and that the instance is bound to handlers with `boost::bind` by `shared_from_this()` instead of `this`.
      singulars
      1. PO
      1. USTanner Sansbury
    3. COBut when I do this he throws an exception "tr1::bad_weak_ptr" probably due to use of shared_from_this() in the async call from the signal_set in the constructor of TcpServer, how can I solve that?
      singulars
      1. PO
      1. USuser2047610
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload