Hi,
You shouldn't have to do any of these manual steps. When you use the update center to update a 3.1 installation (for example) to 3.1.1, it doesn't touch the domain. Without the update center, you can do the same thing manually:
1. unzip 3.1.1 zip file
2. copy domainX from 3.1 installation domains dir to the 3.1.1 domains dir (stop the domain obviously)
3. start the 3.1.1 server
It will start up with the old domain without any other changes needed on your part. If the domain needs to be upgraded, which is the case when starting with a 2.X or 3.0.X domain, then the server will tell you what to do. But you shouldn't need to manually fiddle with domain.xml, and doing so might not leave your server in a usable state.
If starting the newer server with the older domain doesn't work, then there's a bug in whatever module isn't working correctly.
Cheers,
Bobby
On Oct 5, 2011, at 6:40 AM, forums_at_java.net wrote:
> Hi, I remembered that when I upgraded to glassfish 3.1 I had problems with
> the glassfish-3.1-windows.exe installation package, and there were others
> having problems with this as well if I remember correctly. What I did then,
> and what I did this time as well, is copy the glassfish-3.1.1.zip file and
> extract the files. Then it was a case of copying any changed configuration
> over from my existing installation, or at least applying the changes. The
> main pain for me was that the domain.xml has a load of new stuff in it for
> 3.1.1. I had to go through it line by line adding my config to the virgin
> 3.1.1 file. I also have a custom security realm etc... Unless I hear to
> the contrary it looks like the window distribution simply doesn't work. It
> could of course turn out to be something simple like having to disable your
> antivirus.
>
> --
>
> [Message sent by forum member 'oversteer']
>
> View Post: http://forums.java.net/node/827327
>
>