Hi Kedar,
For the people who don't utilize this mechanism, shouldn't we also add a
check of the disk space before domain.xml is flushed? If there isn't
enough disk space to write domain.xml out, then don't allow an update.
This way you always have the current running domain.xml on disk.
My 2 cents...
Thanks - Mark
Kedar Mhaswade wrote:
> Finally, I have been able to fix this problem (reasonably).
>
> All about it can be found at:
> http://wiki.glassfish.java.net/attach/GlassFishAdminReferences/6505045.html
>
>
> Please go through the background and code changes if you have time and
> let me
> know if you have any comments, by tomorrow 12.00 noon, pacific.
>
> I am planning to check this in then, on GlassFish trunk.
>
> Mark Basler: I leave it up to you to approve the fix for 9.1 UR1. If
> you do
> want to do that, let me know and I can port the changes there.
>
> I have run the tests on my 128M Zip-drive on Mac OS X by observing
> domain.xml go
> to zero-bytes and domain.xml.protect coming to rescue, making every
> attempt
> to persist the domain.xml.
>
> Regards,
> Kedar