If what is happening is the new requests are being fired before the previous event finished, make sure the previous request has finished before calling again. I haven't really tested the code below but it should point you in the right direction. Use setTimeout and recursion instead of setInterval. Obviously this solution doesn't give you sharp one second intervals if for some reason they are required (more like one second plus the request cycle that is down to network conditions of the user) but I assume you just need a face paced refresh and strict timing is not crucial.
Still I second the comments above, that 1 second http request interval is risky and a bit abusive to both browser and server, and so there should be a really good reason to use it.
$(document).ready(function() {
function refresh(){
$.get('some_page.html', function (data) {
$('#some_div').html(data);
// call itself recursively
setTimeout(refresh, 1000);
});
};
// init
refresh();
});