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

It seems to me that there is a deadlock bug in instantdb.  I am using a
webapp that has been used successfully on both PostgreSQL and on MSSQL.
When switching to InstandDB it very often hangs, and a thread dump
invariably reveals that at leas one thread is hanging in lockTable().

Note that these are SELECT statements, that should definitely not hang under
any circumstances, as opposed to UPDATE statements, which of course must
hang or fail if the table is locked.

The relevant part of the thread dump follows:


 at java.lang.Object.wait(Native Method)
 at java.lang.Object.wait(Object.java:424)
 at org.enhydra.instantdb.db.Table.lockTable(Table.java:1746)
 at org.enhydra.instantdb.db.Database.lockTables(Database.java:918)
 at org.enhydra.instantdb.db.SQLProg.compile_select(SQLProg.java:1196)
 at org.enhydra.instantdb.db.SQLProg.execute(SQLProg.java:223)
 at org.enhydra.instantdb.jdbc.idbStatement.execute(idbStatement.java:235)
 at
org.enhydra.instantdb.jdbc.idbStatement.executeQuery(idbStatement.java:91)
 at
com.handpoint.util.db.ConnectionContainer.executeQuery(ConnectionContainer.j
ava:275)
 at
com.handpoint.infopoint.DatabaseEncapsulator.isLockedForUser(DatabaseEncapsu
lator.java:1752)
 ...


Any comments, fixes or workarounds really appreciated.


Magnus Torfason,
handPoint
ICELAND

-----------------------------------------------------------------------------
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.