Space: Apache Connectors Framework (https://cwiki.apache.org/confluence/display/CONNECTORS)
Page: FAQ (https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ)
Comment: https://cwiki.apache.org/confluence/display/CONNECTORS/FAQ?focusedCommentId=25200277#comment-25200277
Comment added by Nicolas Max:
---------------------------------------------------------------------
thanks
nicolas
In reply to a comment by Karl Wright:
Derby has a huge number of threads waiting on being able to modify or update a number of table
rows. Meanwhile, one thread seems to be alive and is updating hop count data.
My suspicion is that there is indeed a bug in Derby, but it's the hopcount logic's intensive
use of database access that exacerbates the problem. I suspect that jobs that do not deal
with hopcount at all will not fail readily.
In any case, you can easily change the Quick-Start's properties.xml file to use PostgreSQL
instead. The online build-and-deploy doc explains how.
Change your notification preferences: https://cwiki.apache.org/confluence/users/viewnotifications.action
|