clientEatRequestBodyHandler:

265 views
Skip to first unread message

Maher Kassem

unread,
Feb 12, 2011, 4:14:55 AM2/12/11
to lusca-users
Hi everyone,

I am getting A LOT of these in my cache.log, and im not quite sure
why. This topic may have been discussed on the discussion board a few
months back, but I am not sure my situation is the same. lusca 14809.
I am peering 2 caches as siblings.

2011/02/11 23:24:26| clientEatRequestBodyHandler: FD 747: no more data
left in socket; but request header says there should be; aborting for
now


Regards,

Adrian Chadd

unread,
Feb 24, 2011, 11:42:39 AM2/24/11
to lusca...@googlegroups.com
It means that the server said X bytes would be available, but < X bytes were actually made available before the socket was closed.

This used to cause a leak. I now log a message and abort the connection.

It's there at debug level 1 right now so you have something to correlate potentially weird POST behaviour against if you are seeing said potentially weird POST behaviour.



Adrian


--
You received this message because you are subscribed to the Google Groups "lusca-users" group.
To post to this group, send email to lusca...@googlegroups.com.
To unsubscribe from this group, send email to lusca-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/lusca-users?hl=en.


Reply all
Reply to author
Forward
0 new messages