Modify

Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#5124 closed Bugs (fixed)

EMFILE handling

Reported by: olafvdspek@… Owned by: chris_kohlhoff
Milestone: Boost 1.47.0 Component: asio
Version: Boost 1.45.0 Severity: Problem
Keywords: Cc:

Description

What is the recommended way to handle EMFILE on accept? The chat server example returns from the handler without doing a new accept, which means the server won't accept any new connections after hitting EMFILE. This is undesirable. I've just been bitten by this myself.

Would it be possible for Asio itself to handle this situation gracefully?

http://think-async.com/Asio/boost_asio_1_4_7/doc/html/boost_asio/example/chat/chat_server.cpp

Attachments (0)

Change History (3)

comment:1 Changed 6 years ago by anonymous

  • Component changed from None to asio
  • Owner set to chris_kohlhoff

comment:2 Changed 6 years ago by chris_kohlhoff

  • Resolution set to fixed
  • Status changed from new to closed

As of release branch [72428], examples have been updated to treat accept failures as non-fatal.

comment:3 Changed 6 years ago by Olaf van der Spek <olafvdspek@…>

Thanks. You might also want to use boost::make_shared instead of new.

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain chris_kohlhoff.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.