I fixed my earlier reported problem with transaction deadlock (two
transactions running concurrently, one reads, the other writes). It
wasn't really a deadlock, but a veeeeeeeeery long timeout, viz.
Long.MAXValue milli seconds.
Here's the diff. Please commit to CVS.
Index: ObjectLock.java
===================================================================
RCS file: /cvs/castor/castor/src/main/org/exolab/castor/persist/ObjectLock.java,v
retrieving revision 1.24
diff -u -r1.24 ObjectLock.java
--- ObjectLock.java 2001/05/16 00:27:05 1.24
+++ ObjectLock.java 2001/08/28 14:41:55
@@ -689,7 +689,7 @@
throw e;
}
- long endtime = timeout<0? System.currentTimeMillis() + timeout*1000:
Long.MAX_VALUE;
+ long endtime = timeout>0? System.currentTimeMillis() + timeout*1000:
+Long.MAX_VALUE;
while ( true ) {
// Repeat forever until lock is acquired or timeout
try {
--
Holger Krug
[EMAIL PROTECTED]
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
