Hi,

I have received this error message a few times now this year on a clients
dbisam server. (Running DBISam 4.25)

It seems to happen only when the DBISam server has been running for some
time (ie, a month or more) non stop, and is easilly fixed by restarting the
DBISam server service.

Is there anything that I could be doing in my application that could cause
this. (ie, I know that not freeing certain tables / components correctly can
leave them in memory), but I also thought that if this was the case, after
the program exits (or the server terminates the connection) - any memory
used on the server for that session should also be free'd at this time. (ie,
basically foolproofing any problems that I might create . I was just
wanting to confirm this.

The other thought I had was a possible memory leak within the server, but
after searching the newsgroups, and not seeing many other replies to this -
I don't believe that this is probable.

The server itself wasn't out of memory. (Only 1GB out of 4 used in total on
a MS Windows 2003 Standard server). I don't know exactily how much DBISam
was using (as the service memory usage doesn't show in the task manager
processes), but the overall memory of the system appeared to drop roughly
512mb when I stopped and restarted the service.)

Does anyone know what else could have possibly caused this?

Thanks & Regards

Adam.

Hi Adam,

Can you see anything in the eventlog, kind of "not enough memory" or
something like that?

I am not sure if this could be the case, but please look at this link from
MS:

http://support.microsoft.com/kb/126962


Regards,
Hüseyin


"Adam H." <ahairsub4@pleaseREMOVEme.jvxp.com> skrev i en meddelelse
news:481EDE11-6BA6-44EC-823C-1A1A47AB1E95@news.elevatesoft.com...
> Hi,
>
> I have received this error message a few times now this year on a clients
> dbisam server. (Running DBISam 4.25)
>
> It seems to happen only when the DBISam server has been running for some
> time (ie, a month or more) non stop, and is easilly fixed by restarting
> the DBISam server service.
>
> Is there anything that I could be doing in my application that could cause
> this. (ie, I know that not freeing certain tables / components correctly
> can leave them in memory), but I also thought that if this was the case,
> after the program exits (or the server terminates the connection) - any
> memory used on the server for that session should also be free'd at this
> time. (ie, basically foolproofing any problems that I might create . I
> was just wanting to confirm this.
>
> The other thought I had was a possible memory leak within the server, but
> after searching the newsgroups, and not seeing many other replies to
> this - I don't believe that this is probable.
>
> The server itself wasn't out of memory. (Only 1GB out of 4 used in total
> on a MS Windows 2003 Standard server). I don't know exactily how much
> DBISam was using (as the service memory usage doesn't show in the task
> manager processes), but the overall memory of the system appeared to drop
> roughly 512mb when I stopped and restarted the service.)
>
> Does anyone know what else could have possibly caused this?
>
> Thanks & Regards
>
> Adam.

Adam,

<< I have received this error message a few times now this year on a clients
dbisam server. (Running DBISam 4.25)

It seems to happen only when the DBISam server has been running for some
time (ie, a month or more) non stop, and is easilly fixed by restarting the
DBISam server service. >>

More than likely the server's address space is getting fragmented.  Are you
using the default DBISAM memory manager (dbisammm.pas) with the server still
?  If so, then you may want to consider switching it to using FastMM
instead.  That may help with the situation.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> << I have received this error message a few times now this year on a
> clients dbisam server. (Running DBISam 4.25)
>
> It seems to happen only when the DBISam server has been running for some
> time (ie, a month or more) non stop, and is easilly fixed by restarting
> the DBISam server service. >>
>
> More than likely the server's address space is getting fragmented.  Are
> you using the default DBISAM memory manager (dbisammm.pas) with the server
> still ?  If so, then you may want to consider switching it to using FastMM
> instead.  That may help with the situation.

Thanks for your reply...

I'm using the default dbsrvr.exe file that comes with the installation (ie,
no recompiles). I shall try recompiling with FastMM and see how I go.

Thanks & Regards

Adam.

Adam,

<< I'm using the default dbsrvr.exe file that comes with the installation
(ie, no recompiles). I shall try recompiling with FastMM and see how I go.
>>

Just so you know, I haven't been able to reproduce any fragmentation issues
here with the DBISAM memory manager.  However, we have had success with
FastMM fixing issues like this with other installations with very heavy
usage, so that is why I mentioned trying it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Just so you know, I haven't been able to reproduce any fragmentation
> issues here with the DBISAM memory manager.  However, we have had success
> with FastMM fixing issues like this with other installations with very
> heavy usage, so that is why I mentioned trying it.

Thanks for that. I shall give it a try and see how we go.

Best Regards

Adam.