Skip to main content

When GlassFish is updated through the update tool in GlassFish, does the domain.xml file get written to?

3 replies [Last post]
redhat19
Offline
Joined: 2012-01-31

When GlassFish is updated through the update tool in GlassFish, does the domain.xml file get written to?

I ask because while trying to specify a specify IP address for glassfish, by editing or changing the default 0.0.0.0 address attribute through the Admin console for network listeners, admin service and JMX Connector. I restarted GlassFish and it restarted, only not solving the problem I was faced with. I then proceeded to install all the available add-ons restarted my GlassFish and I was presented with a log in screen I couldn't get past (wasn't accepting GlassFish default password - and I had not set one). I had, in the past, experienced this before when I tired to modify the domain.xml file , while trying to add the address attribute directly to the file. So, I knew it was caused by a configuration error and replaced domain.xml with a copy of the original (backed up) and GlassFish started fine. But I'm not sure if the update process makes changes in the domain.xml file, hence I would have lost the modifications.

Thanks.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Richard Troy Guest 1
Offline
Joined: 2012-02-06

On Mon, 6 Feb 2012 forums@java.net wrote:
>
>  When GlassFish is updated through the update tool in GlassFish, does the
> domain.xml file get written to?
>
> I ask because while trying to specify a specify IP address for glassfish, by
> editing or changing the default 0.0.0.0 address attribute through the Admin
> console for network listeners, admin service and JMX Connector. I restarted
> GlassFish and it restarted, only not solving the problem I was faced with. I
> then proceeded to install all the available add-ons restarted my GlassFish
> and I was presented with a log in screen I couldn't get past (wasn't
> accepting GlassFish  default password - and I had not set one). I had, in
> the past, experienced this before when I tired to modify the domain.xml file
> , while trying to add the address attribute directly to the file. So, I knew
> it was caused by a configuration error and replaced domain.xml with a copy of
> the original (backed up) and GlassFish started fine. But I'm not sure if the
> update process makes changes in the domain.xml file, hence I would have lost
> the modifications.
>
> Thanks.
>
> Â

Â,

In addition to Tom Mueller's knowledgeable response, I'll introduce you to
a tool called "diff". Diff gives you a command-line accessable mechanism
for discovering differences in files. In your instance, you could have run
it against both the domain.xml file and your backup copy and thereby have
known in advance that the files were the same or different.

If your system doesn't have diff, you can get it either by installing
Microsoft's (oddly named) "Tools for Unix" package, or (what I use)
Cygwin, provided by Cygwin.com, an organization funded by Red Hat -
Cygwin provides Windows systems a Linux / Unix-like toolset.

Regards,
Richard

tmueller
Offline
Joined: 2005-10-31

On 2/6/2012 3:31 AM, forums@java.net wrote:
> When GlassFish is updated through the update tool in GlassFish, does the
> domain.xml file get written to?
No. Updatetool does not update anything under the glassfish/domains
directory.
>
> I ask because while trying to specify a specify IP address for
> glassfish, by
> editing or changing the default 0.0.0.0 address attribute through the
> Admin
> console for network listeners, admin service and JMX Connector. I
> restarted
> GlassFish and it restarted, only not solving the problem I was faced
> with. I
> then proceeded to install all the available add-ons restarted my
> GlassFish
> and I was presented with a log in screen I couldn't get past (wasn't
> accepting GlassFish default password - and I had not set one).
Depending on what version you started with an what version you updated
to, you
may be encountering changes in the behavior of secure admin with newer
versions
of GlassFish. Newer versions prevent accessing the console from a
remote system
unless secure admin is enabled (using asadmin enable-secure-admin). Also to
enable secure admin, an admin password is now required.

Tom

redhat19
Offline
Joined: 2012-01-31

Thanks a lot Tom. I appreciate this.