[pybsddb] BDB 5 specific queue locking failure: Lock table is out of available object entries

[Jesus Cea]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/08/12 14:40, Dmitry Dvoinikov wrote:
> I've encountered a problem, and while I'm almost certain it is the
> Berkeley DB problem, not bsddb3's, but it manifests in my Python
> program and I post it here in hope that some of you BDB wizards out
> there could further isolate the problem and possibly report it.
> 
> Anyway, the scenario is as follows:
> 
> 1. Push more records to a queue than you have lockers/objects. This
> fails and it's expected. 2. As the transaction has been aborted,
> the queue should still be empty. 3. Now try to create a cursor on
> the queue and first it. Surprisingly, this fails and the error is

If you drop the DB_PRIVATE, let the program to finish and do
"/usr/local/BerkeleyDB.5.3/bin/db_stat -c" on the environment, you
will see:

"""
[..]
8192	Current number of lock objects allocated
[..]
"""

So, looks like Berkeley DB is leaking the locks, even when the
transaction is aborted.

Please, report to Oracle Berkeley DB team.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBUBvqU5lgi5GaxT1NAQI9fAQAlFz5r3dTSRO9L+vDLWFK/zExmvcCiGde
VvWHybHssCi7BmagciiC9n3yBkwTdUlqYYgX+aJSEDYV4fzsDsADpVcDhXvqbgYG
VQspe7F6LE4RBLSO+/Iw0wm6ntlJavu4Y76A0HDDzPrMUKLhVu3E3UI3+k9581ne
Zfo1oCNVaOI=
=YPeH
-----END PGP SIGNATURE-----