Node.js Chat Demo on Heroku

4 minute read

STOP! If you’re just getting started with Node.js and/or Heroku, then go read James Ward’s excellent Getting Started with Node.js on The Cloud, then come back here… Heroku’s announcement of the public beta of their new ‘Celadon Cedar’ stack, including Node.js support, inspired me to try out Ryan Dahl’s Node Chat demo server on Heroku. Getting it up and running was very straightforward - I went to GitHub, forked Ryan’s node_chat project to my own account and grabbed the source:

ppatterson-ltm:tmp ppatterson$ git clone git://
Cloning into node_chat...
remote: Counting objects: 183, done.
remote: Compressing objects: 100% (72/72), done.
remote: Total 183 (delta 117), reused 168 (delta 110)
Receiving objects: 100% (183/183), 50.07 KiB, done.
Resolving deltas: 100% (117/117), done.

Now I could create my Heroku app...

ppatterson-ltm:tmp ppatterson$ cd node_chat/
ppatterson-ltm:node_chat ppatterson$ heroku create --stack cedar node-chat
Creating node-chat2... done, stack is cedar | [email protected]:node-chat.git
Git remote heroku added

...and add the couple of files that Heroku needs to run a Node.js app (see the [excellent Heroku docs]( for more info):

ppatterson-ltm:node_chat ppatterson$ echo "web: node server.js" > Procfile
ppatterson-ltm:node_chat ppatterson$ echo "{ \"name\": \"node-chat\", \"version\": \"0.0.1\" }" > package.json
ppatterson-ltm:node_chat ppatterson$ git add .
ppatterson-ltm:node_chat ppatterson$ git commit -m "Heroku-required files" Procfile package.json
[master a7617af] Heroku-required files
2 files changed, 2 insertions(+), 0 deletions(-)
create mode 100644 Procfile
create mode 100644 package.json

Now everything is ready to deploy:

ppatterson-ltm:node_chat ppatterson$ git push heroku master
Counting objects: 187, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (67/67), done.
Writing objects: 100% (187/187), 50.40 KiB, done.
Total 187 (delta 118), reused 182 (delta 117)

-----> Heroku receiving push
-----> Node.js app detected
-----> Vendoring node 0.4.7
-----> Installing dependencies with npm 1.0.8

Dependencies installed
-----> Discovering process types
Procfile declares types -> web
-----> Compiled slug size is 2.9MB
-----> Launching... done, v4 deployed to Heroku

To [email protected]:node-chat2.git
* [new branch]      master -> master
ppatterson-ltm:node_chat ppatterson$ heroku ps
Process       State               Command
------------  ------------------  ------------------------------
web.1         starting for 3s     node server.js
ppatterson-ltm:node_chat ppatterson$ heroku ps
Process       State               Command
------------  ------------------  ------------------------------
web.1         up for 6s           node server.js
ppatterson-ltm:node_chat ppatterson$ heroku open

And, just like that, my chat server is up and running and I see it in my browser. It all works nicely - I can hit the URL from a couple of browsers and see all the chat messages going back and forth. Only one problem, though - I'm seeing errors when the chat server is idle: [![](images/node-chat1.png "node_chat - first attempt")](images/node-chat1.png) A look at the logs reveals that connections are timing out.

2011-06-14T19:10:44+00:00 app[web.1]:  Hi there
2011-06-14T19:10:44+00:00 heroku[router]: GET dyno=web.1 queue=0 wait=0ms service=6ms bytes=16
2011-06-14T19:10:44+00:00 heroku[router]: GET dyno=web.1 queue=0 wait=0ms service=3520ms bytes=102
2011-06-14T19:10:53+00:00 app[web.1]:  Now I can talk to myself - woo hoo!
2011-06-14T19:10:53+00:00 heroku[router]: GET dyno=web.1 queue=0 wait=0ms service=2ms bytes=16
2011-06-14T19:10:53+00:00 heroku[router]: GET dyno=web.1 queue=0 wait=0ms service=9185ms bytes=128
2011-06-14T19:10:53+00:00 heroku[router]: GET dyno=web.1 queue=0 wait=0ms service=9203ms bytes=128
2011-06-14T19:11:24+00:00 heroku[router]: Error H12 (Request timeout) -> GET dyno=web.1 queue= wait= service=30000ms bytes=
2011-06-14T19:11:24+00:00 heroku[router]: Error H12 (Request timeout) -> GET dyno=web.1 queue= wait= service=30000ms bytes=

So what's up? The answer is in the [Heroku docs for the new HTTP 1.1 stack](

> The routing stack will terminate connections after 60 seconds on inactivity. If your app sends any data during this window, you will have a new 60 second window. This allows long-polling and other streaming data response.

From the logs, it looks like the connection is being dropped after only 30 seconds, but, no matter, the principle is the same - I need to periodically send some data to keep the connections open. The solution I settled on was having each client set a 20 second timer after it starts its long poll; on the timer firing the client sends a 'ping' message (effectively an empty message) to the server, which, in turn, forwards the ping to all attached clients, causing them to cancel their ping timers and iterate around the long polling loop. Normal chat traffic also causes the timer to be cancelled, so the pings are only sent during periods of inactivity. [You can see the diffs here]( Now my chat server stays up for hours without an error: [![](images/node-chat2.png "node_chat - working now")](images/node-chat2.png) If you [grab my fork from GitHub](, you'll see I also added message persistence, using [Brian Carlson's node-postgres module]( - mostly because I just wanted to see how easy it was to access PostgreSQL from Node.js on Heroku. The answer? [Trivially easy]( :-) As Jeffrey mentions in the comments, apart from those code changes, I also needed to add the 'pg' module in package.json and the shared-database addon. The new package.json looks like this:

  "name": "node-chat",
  "version": "0.0.1",
  "dependencies": {
    "pg": "0.5.0"

The command to install the shared-database addon is:

heroku addons:add shared-database

Disclosure - [I am a employee](, so I'm definitely a little biased in favor of my Heroku cousins, but, I have to say, I remain hugely impressed by Heroku. It. Just. Works.



Jeffrey Noh

Very cool. There’s not many articles out there about using heroku and node. I found this helpful.

I’m trying to understand the pinging. So once a client pings the server, the server in turn pings all other clients. This is so that all the ping timers are in sync? Why do they have to be in sync?

Also, I wanted to get your thoughts about the timeout. It seems like because of this ping workaround, it’s not truly longpolling. It seems like a place in between a timer based ajax poll and true longpolling.

Finally, you should update the line

‘echo “{ "name": "node-chat", "version": "0.0.1" }” > package.json’

to include the pg package and mention somewhere in the article to make sure to have the shared_database addon.

Thanks again for this.

Pat Patterson

Hi Jeffrey - the pinging is just to stop Heroku from closing the HTTP connection on a timeout - see I’ve seen this elsewhere with long-polling - in the Bayeux protocol, the server can periodically send an empty response, which causes the client to close the HTTP connection and send a new request.

You’re absolutely right about the pg package in package.json. I’ll go fix that right now, and mention the shared_database addon.

Thanks for taking the time to comment!


When I try to run it locally, I’m getting these errors:

“Error: Cannot find module ‘/home/euridice/node_modules/pg/lib/native/../../build/default/binding’ at Function.Module._resolveFilename (module.js:338:15) at Function.Module._load (module.js:280:25) at Module.require (module.js:364:17) at require (module.js:380:17) at Object. (/home/euridice/node_modules/pg/lib/native/index.js:16:13) at Module._compile (module.js:456:26) at Object.Module._extensions..js (module.js:474:10) at Module.load (module.js:356:32) at Function.Module._load (module.js:312:12) at Module.require (module.js:364:17) “

Leave a Comment

Your email address will not be published. Required fields are marked *