This one time, at band camp, Wiener, Ed said:
WE>I have encountered a frustrating record locking problem in an enterprise Java
application (DB: SQL Server 2000) with Castor JDO 0.9.4
WE>running under Windows 2000 Advanced Server.
WE>
WE>The exception that occurs is org.exolab.castor.jdo.LockNotGrantedException, which
suggests that there is a transaction that is initiated
WE>but not committed. I have checked all JDO methods that access the table where the
exception occurs, but it appears that all transactions
WE>are initiated and committed properly.
WE>
WE>Additionally, this exception is thrown only after 10-12 hours have elapsed since
the last time the Weblogic 7.0 Server process has been
WE>restarted and occurs on only 1 of the 2 servers on which the application is
resident; despite the fact that both servers are running identical
WE>copies of the application, this exception does not occur on the 2nd server.
WE>
WE>Is there any way to check for the presence of a lock and to disable it in Java?
The table in question contains only 1 record.
WE>
WE>Thank you in advance!
Edward,
This is going to be a very tough problem to troubleshoot/reproduce
if it only occurs every 10-12 hours. Here's a wild guess - is this a
multi-threaded application where two clients could be accessing the same
object(s) and causing a locking issue?
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
