Andrew,
I took a look at the web page and I am pretty sure there is something
else going on.
We have a very effective deadlock avoidance system which does work.
The one thing it won't do is catch client-side deadlocks (caused by
coding errors). I am not saying that is the case here, just pointing
out that it would be better to work with us on our support list
([EMAIL PROTECTED]) to determine the cause before saying that it
is the database that is deadlocking.
What is the "JavaOPENBASEJDBCAdaptor.framework"? Can you explain the
architecture? Is it opening multiple database connections which may
be accessed by a single thread?
If you send us details via [EMAIL PROTECTED] we will be happy to
help you resolve whatever is happening. We have some pretty high-
volume websites which do millions of transactions a day, and we have
not seen a problem with deadlocks. So I am sure there is an
explanation.
- Scott
On Jan 17, 2007, at 11:31 PM, Andrew Lindesay wrote:
Hello;
I'm not sure if I mentioned this before, but one of my projects was
having deadlock problems with high-volume writes out of a WOA into
OPENBASE. I developed a subclassed adaptor for this -- so if
anybody is interested in this, I put something in the wiki about it...
http://en.wikibooks.org/wiki/Programming:WebObjects/
Database_Compatibility_and_Comparisons/OpenBase#Deadlocks
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
