Occasionally on Windows, the following server.log message is seen:
This is seen consistently on the hudson job for the admin devtests, if it is run
on Windows. See http://hudson.sfbay.sun.com/job/admin-devtests-v3.1/
This log message indicates that the memory copy of the configuration has not
been written out correctly to the domain.xml. Future operations, such starting
an instance that was just created will fail because these operations depend on
the disk copy of the domain.xml being correct.
This problem appears to be related to the way that the domain.xml is written out
after a transaction. The domain.xml is saved from a transaction listener that
is executed in a separate thread from where the changes to the configuration
were made. This means that it is possible for other operations to continue,
specifically, other operations that read (and lock) the domain.xml file, while
the save operation is underway, thereby causing the rename failure.