|
We are getting a 6602 error when downloading large emails in our application. I'm wondering if it's an issue of the client and server (using ADS 11) not communicating for too long during the download. The server has a client timeout set for 120 seconds, but I'd expect a different error for that? Also, I've read about the max_timeouts setting for the ads.ini file, but I don't understand the exact interactions that are going on and what to change. The program runs in the main thread and continues to communicate with the ADS while a thread downloads the email. The thread creates its own connection to the server. Would long downloads cause this issue? The call stacks suggest that it's the main thread that is getting the error. |
|
max_timeouts means the client will wait max_timeouts*15 sec before throwing this error. Increasing this value (client side ads.ini file) might solve your issue. Here's a KB item that deals with this: http://devzone.advantagedatabase.com/dz/content.aspx?Key=17&RefNo=070919-1945 |
|
This error continues to plague me at multiple sites. I haven't messed with the ads.ini settings yet, but there must be some reason I've started getting the errors at sites that never did before. I'm using Delphi XE7 and the latest FireDAC that came with it. My question is, what is the consequence of getting a 6602 error exactly? Can I trap it and continue on? How can I cause the error to occur on purpose to test it? What's the best way to gracefully handle this exception in my application to keep the end users from being annoyed? ( I don't mean to ask how to program around exceptions, I mean what should I do for this particular error when it happens ). Thanks. |