Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 4 of 4 total |
Out of memory errors on the server |
Mon, Jul 17 2006 12:00 AM | Permanent Link |
Oliver Bock | The other day I had a DBISAM server process running out of memory
(because a memory-hogging statistics program was also in use on that machine). Unfortunately the exception raised was DBISAM Engine Error # 11279 An unknown error ('Out of memory') occurred with the connection to the database server at 'base', please check the server log. Other than search for the string 'Out of memory', is there a good way to identify this exception? Presumably it was once a EOutOfMemory exception, that got converted to EDBISAMEngineError when it travelled over the client/server link. EDISAMEngineError goes to madExcept, which isn't appropriate because I cannot fix this problem, the user can. Therefore a more normal (and less threatening) error box is appropriate. Oliver |
Mon, Jul 17 2006 8:51 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Oliver,
<< The other day I had a DBISAM server process running out of memory (because a memory-hogging statistics program was also in use on that machine). Unfortunately the exception raised was DBISAM Engine Error # 11279 An unknown error ('Out of memory') occurred with the connection to the database server at 'base', please check the server log. Other than search for the string 'Out of memory', is there a good way to identify this exception? Presumably it was once a OutOfMemory exception, that got converted to EDBISAMEngineError when it travelled over the client/server link. >> Correct. The only way to ID it is via the error message. It is such a rare exception that we didn't translate it into an actual error code for DBISAM. << EDISAMEngineError goes to madExcept, which isn't appropriate because I cannot fix this problem, the user can. Therefore a more normal (and less threatening) error box is appropriate. >> Well, it's actually a fatal exception for DBISAM because it will cause whatever DBISAM is attempting to fail, and that could be pretty serious in certain cases. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jul 27 2006 9:28 PM | Permanent Link |
Oliver Bock | Tim Young [Elevate Software] wrote:
> << EDISAMEngineError goes to madExcept, which isn't appropriate because I > cannot fix this problem, the user can. Therefore a more normal (and less > threatening) error box is appropriate. >> > > Well, it's actually a fatal exception for DBISAM because it will cause > whatever DBISAM is attempting to fail, and that could be pretty serious in > certain cases. Are you suggesting that Out of Memory might corrupt DBISAM and cause problems with subsequent queries? Oliver |
Fri, Jul 28 2006 10:04 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Oliver,
<< Are you suggesting that Out of Memory might corrupt DBISAM and cause problems with subsequent queries? >> No, I'm suggesting that an out of memory error might subsequently result in nothing but out of memory errors, thus causing the application/server to fail completely if the situation doesn't change in terms of available memory. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |