Collection creation and server shutdown

[Ly Le <ll...@galdosinc.com>]

Hi all,

We currently use Xindice for our project.  We ran into the following
problem:
Our system installation includes the distribution package of Xindice.  In
our set up script, we start the db server, create several collections, and
then shut down the server.  All of these operations are done through calls
to dbxmladmin script.  However, sometimes, especially at the first initial
attempt after installing the server, the collections are not created
completely (ie. supposedly we created 4 collections, but only 2 were
created) eventhough the commands were shown on standard output as completed
successfully.  Is that because the server shutdown was executed before the
rest of the collections were created?  If that is the case then it is quite
strange since we expected the ops to be sequential (ie. completion of one
operation before starting the next one).

We use Xindice version beta 4 for Windows 2000.  Below is an example of our
script:

echo Start up the db server...
call "%DBXML_HOME%\startup.bat"

pause

call "%DBXML_HOME%\bin\dbxmladmin" add_collection -c /db -n collection1
call "%DBXML_HOME%\bin\dbxmladmin" add_collection -c /db/casa -n collection2
call "%DBXML_HOME%\bin\dbxmladmin" add_collection -c /db/casa -n collection3
call "%DBXML_HOME%\bin\dbxmladmin" add_collection -c /db/casa -n collection4
call "%DBXML_HOME%\bin\dbxmladmin" add_collection -c /db/casa -n collection5

echo Shutdown the db server...
call "%DBXML_HOME%\bin\dbxmladmin.bat" shutdown -c /db


All necessary environment variables and classpath are set up correctly.  No
exception was thrown.  Everything seems to be successfully completed.
However, only collections 1-3 were created (or sometimes from 1-4).

Any of you have encountered similar problem before?  Please let us know if
you have an answer.

Thank you in advance,

Best regards,

Ly Le


------------------
Privileged or confidential information may be contained in this message. If
this message was not intended for you, destroy it and notify us immediately.
Opinions, conclusions, recommendations, and other information presented in
this message are not given or necessarily endorsed by my employer or firm.

Re: Collection creation and server shutdown

[Tom Bradford <br...@dbxmlgroup.com>]

Ly Le wrote:
> We currently use Xindice for our project.  We ran into the following
> problem:
> Our system installation includes the distribution package of Xindice.  In
> our set up script, we start the db server, create several collections, and
> then shut down the server.  All of these operations are done through calls
> to dbxmladmin script.  However, sometimes, especially at the first initial
> attempt after installing the server, the collections are not created
> completely (ie. supposedly we created 4 collections, but only 2 were
> created) eventhough the commands were shown on standard output as completed
> successfully.  Is that because the server shutdown was executed before the
> rest of the collections were created?  If that is the case then it is quite
> strange since we expected the ops to be sequential (ie. completion of one
> operation before starting the next one).

> Any of you have encountered similar problem before?  Please let us know if
> you have an answer.

This may have to do with the delayed write of the system.xml file when a
collection is created.  This method of managing volatile configurations
has been replaced in Xindice by the storage of all configuration in the
database itself.  You should consider check the Xindice tree out of CVS,
and using it instead, as the dbXML trees will no longer be maintained.

-- 
Tom Bradford - http://www.tbradford.org
Developer - Apache Xindice (formerly dbXML)
Maintainer - jEdit-Syntax Java Editing Bean