The combination of setExclusiveCreate and removeDatabase causes a problem?

Mark Hayes · *nix forums beginner Joined: 27 May 2005 Posts: 35

Ron Cohen · *nix forums beginner Joined: 28 Feb 2005 Posts: 1

"Takuya Murata" <takusi@gmail.com> wrote in message
news:1109569178.325889.59500@o13g2000cwo.googlegroups.com...

Takuya Murata · *nix forums beginner Joined: 28 Feb 2005 Posts: 1

I might have found a bug of Berkeley DB JE 1.7.1.

This is a very quirky procedure, but

1. Attemp to open an existing database with setAllowCreate and
setExclusiveCreate both being true.
2. The attempt fails (since setExclusiveCreate is turn on.)
3. Open an existing database this time with setExclusiveCreate both
being false.
4. Close it
5. Call removeDatabase to remove this database.
6. And I got a LockExpire exception, which I don't think is a correct
behavior.

I used transactions throughtout the procedure. I carefully checked my
code and couldn't find any problem. After modifying the code so that
(1) happens only if there is no database with the name yet, I have the
problem gone.

(I am just posting this before I forget it)

Google