General Information

The GlassFish Server creates one application server instance, called server at the time of installation. You can delete the server instance and create a new instance with a different name if you prefer.

Each GlassFish Server instance has its own Java configuration, Java resources, application deployment areas, and server configuration settings. Changes to one application server instance have no effect on other application server instances. You can have one application server instance within one administrative domain.

For many users, one application server instance meets their needs. However, depending upon your environment, you might want to create one or more additional application server instances. For example, in a development environment you can use different application server instances to test different GlassFish Server configurations, or to compare and test different application deployments. Because you can easily add or delete an application server instance, you can use them to create temporary "sandbox" areas to experiment with while developing.

In addition, for each application server instance you can also create virtual servers. Within a single installed application server instance you can offer companies or individuals domain names, IP Addresses, and some administration capabilities. For the users, it is almost as if they have their own web server, without the hardware and basic server maintenance. These virtual servers do not span application server instances. For more information about virtual servers, see JVM General Settings.

In operational deployments, for many purposes you can use virtual servers instead of multiple application server instances. However, if virtual servers do not meet your needs, you can also use multiple application server instances.

An GlassFish Server instance is not started automatically. Once you start an instance, the instance runs until you stop it. When you stop an application server instance, it stops accepting new connections, then waits for all outstanding connections to complete. If your machine crashes or is taken offline, the server quits and any requests it was servicing may be lost.

Use the General Information page to verify GlassFish Server settings and to view Java Virtual Machine data.

The General Information page contains the following information.

Stop Button

Click the Stop button to stop the GlassFish Server.

Restart Button

Click the Restart button to restart the GlassFish Server.

View Log Files Button

Click the View Log Files button to view log files for a GlassFish Server instance or cluster.

View Raw Log Button

Click the View Raw Log button to view raw log files for the Admin Server (named server).

Rotate Log Button

Click the Rotate Log button to rotate the log file for the Admin Server (named server).

Recover Transaction Button

Click the Rotate Log button to recover transactionsfor the Admin Server (named server) on the Recover Transactions page.

Secure Administration Button

Click the Secure Administration button to enable or disable secure administration on the Secure Administration page.

Name

The name of the current server.

Status

The current status of the server instance. The server can be stopped, started, or running.

Uptime

The number of hours and minutes that the server instance has been continuously running. This is read-only.

HTTP Load Balancer

The name of the load balancer, if it is enabled for the server instance.

JVM

If you click JVM Report, a separate window opens and displays reports on the Java Virtual Machine, including a summary report, memory management and garbage collection report, class loading report, and a current thread dump.

Configuration Directory

The directory on the host machine that contains configuration files, such as domain.xml.

Installed Version

The product version identifier.

Secure Administration

The current status of secure administration. Possible values are Enabled and Not Enabled.

Debug

Identifies whether debugging is enabled. If debugging is enabled, the port number is also displayed.

HTTP Port(s)

The currently configured ports for HTTP requests and responses.

IIOP Port(s)

The currently configured ports for IIOP requests and responses.

Related Task
Copyright © 2005, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices