incubator-connectors-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Connectors Framework > How to Build and Deploy ManifoldCF
Date Tue, 05 Oct 2010 19:05:00 GMT
Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS)
Page: How to Build and Deploy ManifoldCF (https://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+ManifoldCF)
Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+ManifoldCF?focusedCommentId=23339985#comment-23339985

Comment added by Farzad:
---------------------------------------------------------------------

I opened a ticket,https://issues.apache.org/jira/browse/CONNECTORS-111.  So I did a bit more
experimenting, and it seems to be caused the first time I run. First time after a new install.
 I restarted the job and it ended sucessfully.   

In reply to a comment by Karl Wright:
The code is not executing inside transaction at this point, so it is puzzling how Derby could
wind up throwing persistent locks across statements, which is what you need to do to cause
deadlock to occur.  The only possibility I can think of is that there's a bug in
the ManifoldCF Derby database implementation class that's causing transactions to persist. 
The only other alternative is a bug in Derby itself.

I can find this if it happens enough to trigger the deadlock regularly. How often does this
happen to you?  I have never seen it before myself.

In any case, please do open a Jira ticket, since this is certainly the wrong forum for problems
of this kind.

Karl\\

Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action

Mime
View raw message