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

Software
Downloads
Documentation
CVS Repositories
Roadmap
License

About Enhydra.org
Who We Are
News, Articles & Events
Getting Involved
Contact Us

Community
Demos
Contributions
Resources
Case Studies
On The Edge! -NEW-
Commercial Vendors

Michael

> We're experiencing a problem using a combination of InstantDB and RmiJdbc.
> After sometime the database becomes unresponsive.  This can occur when the
> system sits idle or when there is heavy use of the system.  To fix the
> problem, we have to shut the database (RmiJdbc) down and restart it.

RmiJdbc is a relatively simple program with no active components (i.e. it
only does things when it's told to). I wonder if a network connection could
time out when idle?

> I'm contacting you to see if you have ever had anyone mention similar
> problems.

I think I have heard of this happening before. I hope you don't mind, but
I've posted this response to the instantdb news group. Maybe someone else
out there can offer some more helpful suggestions.

Regards

Pete

--

Peter Hearty                         peter.hearty@lutris.com
Lutris Technologies (UK)        http://www.lutris.com
----- Original Message -----
From: "Michael Connick" <mpconnick@denaliproject.com>
To: <peter.hearty@lutris.com>
Sent: Tuesday, September 19, 2000 9:03 PM
Subject: InstantDB & RmiJdbc


>
> Peter:
>
> We're experiencing a problem using a combination of InstantDB and RmiJdbc.
> After sometime the database becomes unresponsive.  This can occur when the
> system sits idle or when there is heavy use of the system.  To fix the
> problem, we have to shut the database (RmiJdbc) down and restart it.
>
> We have also been using InstantDB directly in our standalone product, and
> have experienced no problems there.  This makes me think RmiJdbc is the
> problem.
>
> The problem occurs on a number of different server platforms (Windows NT,
> Linux, Novell).  I've managed to rule out:
>
> - platform
> - excessive memory usage
> - JDK/JRE version or vendor
>
> This leads me to believe there might be something related to either
RmiJdbc
> and threads or RmiJdbc causing a database lock of some sort to occur.
>
> I'm contacting you to see if you have ever had anyone mention similar
> problems.
>
> --
> Michael Connick
> The Denali Project, L.L.C.
> mpconnick@denaliproject.com
> 1-877-347-1629 ext. 218
> 1-517-347-1629 (fax)
> www.denaliproject.com
>
>
>

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
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 owner-instantdb@enhydra.org.