db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kal?n <mka...@apache.org>
Subject [OJB] Issue #OJB200 modified
Date Sun, 15 Aug 2004 23:22:09 GMT
You can view the issue detail at the following URL:



Issue ID
 OJB200 (We are frequently getting the close statement exceptions and some times it is causing
the deadlock.)

Modified by
 Martin Kalén
 mkalen (mkalen@apache.org)

The following modifications were made to this issue:

Status changed from "New" to "Closed"
Resolution set to "Invalid"

This looks like database locks to me. OJB cannot help you with lock synchronization semantics,
if you are getting deadlocks from trying to update rows concurrently you must review your
lock strategy/DDL. 

Please provide enough example code (at least platform settings, descriptor repository and
relevant code snippets) to reproduce this with OJB if you want to re-open this issue.

This message is automatically generated by the Scarab
issue tracking system.  For more information:

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message