I had spoken a while back about this problem (clients timing out when scanners do not return with a row yet: search for "A possible bug in the scanner. "
I am trying to fix the problem in the next few days: our system is a little crippled without the fix (We use filters in scans and the bug crops up during filters that return sparse sets.). JD, can you let me know the status of the recentmost patch attached (31/Mar/10)? Thank you Vidhya
