Community
Participate
Working Groups
Build Identifier: I20100608-0911 If I had change the workflow as in the tutorial described it get the following error message if I try to start the web crawler by the JConsole interface: Error during executeCrawl of DataSourceId 'web': org.eclipse.smila.connectivity.deltaindexing.DeltaIndexingException: data source web is already locked by another session Reproducible: Always Steps to Reproduce: 1. Work on the tutorial. 2. Start the web crawler by JConsole
The bug can be narrowed. In the config file QueueWorkerListenerConfig the first rule must be changed by the tutorial. If the number threads still remains 4 the error message is shown. It seeams that a thread problem exists. Error entry in config file: <Rule Name="ADD Rule" WaitMessageTimeout="10" Threads="4"> <Source BrokerId="broker1" Queue="SMILA.connectivity"/> <Condition>Operation='ADD' and NOT(DataSourceID LIKE 'web%')</Condition> <Task> <Process Workflow="AddPipeline"/> </Task> </Rule>
Hi Nils, thank you for the feedback and welcome to eclipse smila. The error messages: org.eclipse.smila.connectivity.deltaindexing.DeltaIndexingException: data source web is already locked by another session applies to a bundle that is necessary for the crawling process. The amount of listener-threads should have no impact to this locking problem. A database entry seems to be locked. Can you describe how you get to this status? For a fresh new start please delete your workspace folder (it will erased all database including the index). I will also daniel as CC, maybe it has some relevance to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=302634. Thanks in advance for your effort Sebastian
I can reproduce this problem. I will fix that in the next upcoming days
Ups, i am sorry, i had the wrong bug open. Do you have new experiences with the problem in this bug? Sometimes the deltaindexing will be locked (e.gg if you kill the application). but you can delete the whole workspace or use the JConsole to unlock a specific datasource deltaindexing db. (In reply to comment #3) > I can reproduce this problem. > > I will fix that in the next upcoming days
Since we completely updated 5 minutes tutorial I am closing this bug.
Closing this