Subject | lock manager out of room Why? |
---|---|
Author | William L. Thomson Jr. |
Post date | 2002-10-02T22:47:41Z |
Recently an app that is still in development started returning the
following error while using the C API.
lock manager out of room
For some reason I could connect to the DB, but when I tried to call
isc_dsql_prepare I would get the above error?
The only thing that made the error go away, was to stop and restart
Firebird. Which is rather strange since Firebird has been up and running
non-stop now since the last kernel upgrade, a month or two back.
I am not sure what caused this, but I think it was a Java connection
pool that was being tested on a development server. I left a few
services running on the development server, after office hours. The next
day that servers logs were full of errors. My public server was unable
to connect/communicate with the db server due to my development server
beating the crap out of my db server all night long. Now once I shut
down the development server's services and restarted a few on the public
server all was well. I did not have to restart Firebird at that time.
I did have to restart Firebird to get my C++ client app using the C API
to start working again, and stop returning the
lock manager out of room error.
So is there an API method I can call, if and when I run into this error
again? Or is there anything I can do, aside from stopping and starting
Firebird?
What exactly does lock manager out of room mean? I looked at the docs I
have as part of the Borland media pack (release version of the IB6.0
beta docs) but could not find that error, nor a description of it.
I know the db server had allot of free ram, free disk space, and the
processor was less than 5% usage. So what room was the lock manager
looking for? I did not look in the /tmp directory, but I do not think it
was full?
If it matters I am using Firebird 1.0 and most of the time, lovin it. ;)
--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone 707.766.9509
Fax 707.766.8989
http://www.obsidian-studios.com
following error while using the C API.
lock manager out of room
For some reason I could connect to the DB, but when I tried to call
isc_dsql_prepare I would get the above error?
The only thing that made the error go away, was to stop and restart
Firebird. Which is rather strange since Firebird has been up and running
non-stop now since the last kernel upgrade, a month or two back.
I am not sure what caused this, but I think it was a Java connection
pool that was being tested on a development server. I left a few
services running on the development server, after office hours. The next
day that servers logs were full of errors. My public server was unable
to connect/communicate with the db server due to my development server
beating the crap out of my db server all night long. Now once I shut
down the development server's services and restarted a few on the public
server all was well. I did not have to restart Firebird at that time.
I did have to restart Firebird to get my C++ client app using the C API
to start working again, and stop returning the
lock manager out of room error.
So is there an API method I can call, if and when I run into this error
again? Or is there anything I can do, aside from stopping and starting
Firebird?
What exactly does lock manager out of room mean? I looked at the docs I
have as part of the Borland media pack (release version of the IB6.0
beta docs) but could not find that error, nor a description of it.
I know the db server had allot of free ram, free disk space, and the
processor was less than 5% usage. So what room was the lock manager
looking for? I did not look in the /tmp directory, but I do not think it
was full?
If it matters I am using Firebird 1.0 and most of the time, lovin it. ;)
--
Sincerely,
William L. Thomson Jr.
Support Group
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone 707.766.9509
Fax 707.766.8989
http://www.obsidian-studios.com