InstantDB Project
About InstantDB
Project Mail Lists
Short History
Reporting Bugs
Screen Shots
3rd Party Examples

CVS Repositories

Who We Are
News, Articles & Events
Getting Involved
Contact Us

Case Studies
On The Edge! -NEW-
Commercial Vendors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: InstantDB: Synchronized Servlets

The only time you'd want to use the RmiJdbc driver is when accessing the
same InstantDB database using two or more Java Virtual Machine
processes.  You should have no problem accessing the same database from
within the same JVM.  If you're running two servlets in one instance of
Enhydra, for example, you won't run into any issues using the same
InstantDB database.


Steve Carton wrote:
> Thom,
> I guess I'm a little surprised by that.  I would
> have thought if I created a synchronized, static
> method encapsulating my IDB action, since statics
> are shared by all servlet instances, it would
> prevent a collision.
> Steve
> ----- Original Message -----
> From: "Thom Nelson" <>
> To: <>
> Sent: Tuesday, March 20, 2001 5:34 PM
> Subject: Re: InstantDB: Synchronized Servlets
> | Hi Steve,
> |
> | This will not work, because you will still have
> different instances of
> | instantdb running against the same database
> files.  This will inevitably
> | result in corrupted data, since much of
> instantdb's state is cached in
> | memory.  This isn't a threading issue; instantdb
> works fine with
> | multiple threads, just not multiple VMs.
> |
> | Thom
> |
> | Steve Carton wrote:
> | >
> | > I'm wondering if I can achieve the same effect
> as the RmiJdbc server from a
> | > servlet if I encapsulate the JDBC code in
> synchronized methods?
> | >
> | > Anyone try that?
> | >
> | > Steve Carton
To unsubscribe from this mailing list, send email to
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at