Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8407005
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 9, 20262026-06-09T23:16:10+00:00 2026-06-09T23:16:10+00:00

After some time I tried working with node.js and socket.IO again, but it didn’t

  • 0

After some time I tried working with node.js and socket.IO again, but it didn’t work as expected:

My setup

  1. Downloaded node.js from github and compiled it on my external webserver running on debian squeeze
  2. Created a directory for the node.js project
  3. Added socket.io locally with npm
  4. Created socketIO_server.js and just added this single line of code:

    var socketIO = require('socket.io').listen(8000);
    
  5. Started the socketIO_server.js and console log says “info – socket.io started”

  6. Opening http://domain.tld:8000 gives the message “welcome to socket.io”

The Problem

When I try to access the client library by http://domain.tld:8000/socket.io/socket.io.js it gives also the message “welcome to socket.io”, but the console log shows “served static content /socket.io.js”. I have no idea why this happens!
I though the nginx server running parallel causes this problem but stopping the server didn’t change anything.

Thanks for reading and help!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-09T23:16:11+00:00Added an answer on June 9, 2026 at 11:16 pm

    This is caused by a commit made to the EventEmitter lib of nodejs in a recent change. I’ve opened an issue on socket.io.

    https://github.com/LearnBoost/socket.io/issues/987

    UPDATE

    This issue has been fixed as of socket.io 0.9.12

    Fix:
    https://github.com/LearnBoost/socket.io/blob/0.9.12/lib/manager.js#L116

    Commit:
    https://github.com/LearnBoost/socket.io/commit/0d3313f536d0231932dd6617db449a071f5bc03a


    Can not serve socket.io.js when listening on port. (node 0.9.1-pre, socket.io 0.9.9)

    Due to a recent commit to node, you can no longer splice out event listeners. This causes socket.io to display the welcome message when trying to access the socket.io.js client file as the original event listener does not get removed.

    Example breakage:

    var socketIO = require('socket.io').listen(8000);
    

    This breaks due to the way node 0.9.1-pre changed the way you can access listeners for the EventEmitter lib.

    nodejs commit that breaks socket.io

    Make EventEmitter.listeners(event) return a copy of the listeners array instead
    of the array itself.

    EventEmitter.prototype.listeners = function(type) {
       if (!isArray(this._events[type])) {
         this._events[type] = [this._events[type]];
       }        
    -  return this._events[type];   
    +  return this._events[type].slice(0);
    };
    

    https://github.com/joyent/node/commit/20e12e4be37f394672c001fdb9b05c0275731901#L1R245

    Relative socket.io code:

    // reset listeners
    this.oldListeners = server.listeners('request').splice(0);
    

    https://github.com/LearnBoost/socket.io/blob/master/lib/manager.js#L115

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have my java-written application being killed after some time of work. Java application
After working on a page for quite some time, the customer now decided that
After working for some time with SVN I decided to try git with my
After some time researching and trying different things I still cannot get my @ExceptionHandler
I am getting after some time unrecognized selector sent to instance exception. When i
Possible Duplicate: how to hide a div after some time period? i need to
I want to have an operation(Task) to be Scheduled after some time OR Based
Here I need to call a javascript function first and after some time I
I want to achieve an effect where a close button appears after some time
After spending some time wireframing my ideas, I want to start building my rails

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.