On Tuesday 14 April 2009 09:29:11 [email protected] wrote: > > Those of you who do not see this error, you lucked out--closer/better > > connections to various servers involved. You would not notice such a > > wordaround. > > Maybe you should file a bug. If the error is triggered by bad > connections increasing some timeouts might help
This bug has been filed, closed, etc., and timeouts recommended. I did get some improvement with a ridicultous timeout and multiple retries. For a while. There was a period when this was not a problem, then it came back. IF there be no timeout problem, then the workaround I propose will simply not get exercised. However, having the alternative could be a better solution, since the timeouts and retries do not always solve it but "smaller" accesses (to single servers?) do seem to work more consistantly when needed. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
