A user had a problem with a roxie query that was taking a very long time to respond. Eventually it responded with an out of memory error which would have provided information about which activity was causing the problem.
Unfortunately, when testing the query from within the esp interface, the request timed out before the error message could be displayed. This made it very tricky for the user to diagnose the issue.
Consider adding an option to not time out the esp request, and/or provide information that the request had timed out.
(I ran the query via testsocket and got back the error response.)