Xindice can only handle one JVM accessing it directly. So if you have
the Xindice servlet running, you will find problems with using embedded
mode. Likewise, if you run embedded mode in Tomcat, and then use the CLI
to write to the DB, you'll have problems. So, the moral is to only
access the DB from one JVM. If you want to be able to use the CLI and
Tomcat simultaneously, then use the XIndice servlet instead. My solution
to this was to implement some basic Java code that I can run within my
servlet container, using embedded mode driver, to update my DB via a
web interface. If you really want a CLI, write a CLI to drive that web
interface!
HTH.
Regards, Upayavira
[EMAIL PROTECTED] wrote:
Hi
I deployed xindice1.1b3 in Tomcat 5.0.16, use jdk1.4.2_02 in w2kp.
Deployment worked fine (I can see my db, create collections...).
The problem comes when I restart tomcat. I've read similar problems in the
mailing list, but no solution yet. The collections I created are no longer
accessible, so I have to delete them from the file system and create them again.
Is this a known and not solved bug, or just user problem?
I have also seen that after creating a collection in the "normal" database,
I cannot put any docs in that collection accessing it the "embedded" way. Am
I doing something wrong mixing both access method's?
Many thanks
Xaxo
