afternoon all,
i just wasted the better part of the afternoon trying to debug a problem
with disappearing collections when tomcat restarts. Well i guess its not
wasted if i found the problem and we can do something about it. Ive
searched the archives and found a few people with the same problem, but
no REAL solutions yet. The only responses were along the lines of:
1 - check the location of the db in system.xml
2 - make sure the .war isnt reloading everytime
well these have been done and these are NOT the cause of the problem.
Ive found a workaround of sorts for the moment but im sure there is an
underlying bug that needs to be addressed somewhere in the xindice code.
ok my setup:
RedHat Linux 8.0
Tomcat 4.1.24
Xindice 1.1b (built fresh from the CVS just a few minutes ago, but that
didnt help the situation anyways)
ok my problem was collections added through XMLdbGUI would show up in
the gui. They would show up using the "ugly debug tool" servlet, AND
they would show up using the command line tool. Once i restarted they
would disappear.
Ok i figured out that upon xindice webapp shutdown the SysConfig.tbl
file would get rewritten to the state it was in before i started the
webapp. Well actually database.xml (which resides in SysConfig.tbl) is
getting reset thus effectively erasing the new collection entries).SO,
the workaround im using at the moment is to shutdown the webapp
completely and then add collections using the command line util. Then
start the webapp back up and the collections stick around when the
webapp is restarted again. BUT of course any new collections added
through XMLdbGUI would not show up, they would be lost as usual.
adding documents to these new collections also works fine through
XMLdbGUI (or really the XML-RPC interface)
