hello,

has anyone working examples of multiple threads sharing the same DbEnv
to write and read to a database (in my case an XmlContainer)?

I am trying to do that from a servlet engine, and have no success
until now: I must close and open my XmlContainer for each transaction,
and it is extremely slow.

thanks a lot,

Stan.

In article <89910ac4.0309250049.143dbd89 (AT) posting (DOT) google.com>, Stan Pinte wrote:
Can't you just have a DbEnv for each thread? I can see how sharing the
DbEnv across threads won't work, unless you wrap it all in synchronized
sections, but multiple DbEnvs on one database must be possible. If not,
I don't see how BDB/xml can be used in servlets at all.

--
Emiliano

See docs for DbEnv.open method.
You can pass in DB_THREAD as part of the flags param.





Emiliano <nospam (AT) iris-advies (DOT) nl> wrote

Stan Pinte wrote:
Yes, I've done it - I specify:

Db.DB_PRIVATE

Because I have a single JVM (with multiple threads) accessing the databases.

For Java, Db.DB_THREAD is assumed as a default so you shouldn't need to
specify it explicitly.

In this case, I suspect you are losing (it's being GC'd) the reference
to the DbEnv instance - where do you keep the DbEnv reference?

Dan.