Document that you can only listen on an already closed socket #11685

Activity

1. gibfahn

   added

   docIssues and PRs related to Node.js documentation.Issues and PRs related to Node.js documentation.

   good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.

   netIssues and PRs related to the net subsystem.Issues and PRs related to the net subsystem.

   on Mar 4, 2017
2. joyeecheung commented on Mar 5, 2017

   

   joyeecheung

   on Mar 5, 2017

   Member

   More actions

   Since listen() is overloaded it might help even more to point out what happens if you call listen() on different stuff multiple times..

   Also I think listen() doesn't actually raise an error when you try to listen on an unbound handle?

   👍React with 👍1Reacted by Gibson Fahnestock
3. eduardbme commented on Mar 5, 2017

   

   eduardbme

   on Mar 5, 2017

   Contributor

   More actions

   will do
4. gibfahn commented on Mar 5, 2017

   

   gibfahn

   on Mar 5, 2017

   MemberAuthor

   More actions

   @eduardbcom if you're going to fix this (either in #8419 or a separate PR) then if you could add the Fixes: line to the commit and link to it from here that'd be great!

   Fixes: https://github.com/nodejs/node/issues/11685#issuecomment-284221748
   
5. mcollina

   closed this as completedin b24e269on Sep 4, 2017
6. addaleax

   added a commit that references this issue on Sep 5, 2017

   net: multiple listen() events fail silently

   ...

   8d129c3
7. sjarmak

   added a commit that references this issue on Jul 27, 2026

   net: multiple listen() events fail silently

   ...

   b24e269