mapbox/tilelive-mapnik — Issue #24: lockingcache and socket is not writable
Author: ianshward
Created: 2012-01-27 18:44:15+00:00
State: open

@kkaefer I'm doing some load testing against TileMill, listening on socket instead of port (not sure this is important, though). What I've run into is this error, which kills the tile server. One clue is that if I increase the lifetime of objects in the locking cache to a long time or so, like 1 hour, the error stops occurring.

My load testing is against one map, using siege w/ a urls file in internet mode, so it randomly chooses urls to hit from that file.

```plain

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Socket is not writable
at Socket._writeOut (net.js:391:11)
at Socket.write (net.js:377:17)
at ServerResponse._writeRaw (http.js:392:28)
at ServerResponse._send (http.js:372:15)
at ServerResponse.write (http.js:622:16)
at ServerResponse.end (http.js:682:16)
at ServerResponse.send (/home/ianward/www/tilemill/node_modules/bones/node_modules/express/lib/response.js:108:8)
at /home/ianward/www/tilemill/servers/Tile.bones:83:17
at Function. (/home/ianward/www/tilemill/node_modules/tilelive-mapnik/lib/mapnik.js:313:9)
at /home/ianward/www/tilemill/node_modules/tilelive-mapnik/lib/lockingcache.js:60:26
```