Nelson Sproul - 02/Jun/06 03:25 PM Changed the queue code so that timeouts can be assigned on a per-queue basis; now for command queues, I am setting an infinite timeout, the assumption being that if the server and/or driver don't have commands for me to execute, this is no cause for worry

Paul Hammant - 02/Jun/06 05:16 PM Actually my thought was not so much about the time of the time out, but the way it appears in the console of the proxy-server. We may know that stacktraces are sometimes expected, but the ordinary user might think its an issue and symptomatic of buggy software - ph

Nelson Sproul - 02/Jun/06 05:29 PM Yes, I understand, but my thinking in looking at this problem is that the timeouts which provoke those stack traces are not indicative of a real problem. Resetting the timeout to be infinite -- i.e., turning it off -- will make it impossible for these timeouts to recur, and I think eliminate the problem of the attendant stack traces alarming our users.