For what it's worth, after some 5 days of work, and a couple of schema changes
to boot, LCF now runs with Derby.
Some caveats:
(1) You can't run more than one LCF process at a time. That means you need
to either run the daemon or the crawler-ui web application, but you can't run
both at
The daemon does not need to interact with the UI directly, only with the
database. So, you stop the UI, start the daemon, and after a while, shut down
the daemon and restart the UI.
Karl
-Original Message-
From: ext Jack Krupansky [mailto:jack.krupan...@lucidimagination.com]
Sent:
Just to be clear, the full sequence would be:
1) Start UI app. Agent process should not be running.
2) Start LCF job in UI.
3) Shutdown UI app. Not just close the browser window.
4) AgentRun.
5) Wait long enough for crawl to have finished. Maybe watch to see that Solr
has become idle.
6)
What is the nature of the single LCF process issue? Is it because the
database is being used in single-user mode, or some other issue? Is it a
permanent issue, or is there a solution or workaround anticipated at some
stage.
Thanks.
-- Jack Krupansky
