That 10% happens on specific calls or randomly?
If the CPU usage is too high node won't be able to answer but it still accept
incoming connections. Also happens if there's a huge leak and memory
consumption is too high as well.
Start by monitoring those processes and check CPU usage and
Yeah that's true, get your team together and choose whatever they feel more
comfortable with.
About tests, usually I have more integration/rest tests than unit with mock.
On May 24, 2014, at 5:21 PM, // ravi ravi-li...@g8o.net wrote:
On May 24, 2014, at 8:55 AM, Jake jp021...@gmail.com
The same rules that you follow for other languages, mainly dynamic ones like
ruby python groovy.
- separation of concerns
- well structured and small methods, using either OO or a functional style
- a lot of testing, unit, integration, etc
- pair programming
- learn to not make callback hell,
Some notes:
- why you're not getting the error on insert? It's just if (!err)
- what's the difference between the one that works and the one that doesn't? Is
your req.body.whatever sanitized? Inserting stuff and querying like that might
be risky.
Try to log what you're trying to insert. And
+unsubscr...@googlegroups.comjavascript:_e(%7B%7D,'cvml','nodejs%2bunsubscr...@googlegroups.com');
.
For more options, visit https://groups.google.com/groups/opt_out.
--
Bruno Fuster
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing
You can waterfall two waterfalls
function createWaterfall(commands) {
return function(callback) {
Async.waterfall(commands, callback);
}
}
var waterfalls = [createWaterfall(readCommands),
createWaterfall(writeCommands)];
Async.waterfall(waterfalls, function(err) {
//final result
unstable
* unsure whether i can use it in node 0.8.22
Thanks again.
On Tue, Dec 10, 2013 at 3:57 AM, Bruno Fuster brunofus...@gmail.comwrote:
Ps: use process.on uncaughtException and the server will not crash
Be careful with that :)
On Dec 9, 2013, at 9:01 PM, ming hseum...@gmail.com
It's probably because some callback is being called twice and you are trying to
send a response twice.
That problem is not easy to find, though.
Increase your log level and make sure that you have proper logging and
request/response logging. When that error occurs, check which requests came
Ps: that error is not a node.js version issue
Don't even bother trying to upgrade or downgrade
On Dec 9, 2013, at 9:01 PM, ming hseum...@gmail.com wrote:
Hi,
i'm running a node application which crashes probably once a week due to an
uncaught Can't render headers ... exception. The
Ps: use process.on uncaughtException and the server will not crash
Be careful with that :)
On Dec 9, 2013, at 9:01 PM, ming hseum...@gmail.com wrote:
Hi,
i'm running a node application which crashes probably once a week due to an
uncaught Can't render headers ... exception. The
.
For more options, visit https://groups.google.com/groups/opt_out.
--
Bruno Fuster
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs
11 matches
Mail list logo