http //localhost/8080 : Cannot Access Local Server (http://localhost:8080)

http //localhost/8080 : Cannot Access Local Server (http://localhost:8080)

When this error occurs, check the following:

• Did the Server Start?
• Was the Server Started at the Expected Port?
• Is a Personal Firewall Enabled?

Did the Server Start?

Description

If the console window is still open, the expected message indicates that the default domain was started successfully.

If the console window is already closed, check for messages in the log file:

as-install/domains/domain1/logs/server.log

If startup was successful, the expected message is similar to that on the console, and appears at the end of the log file.

For more information about starting a domain, see Starting and Stopping a Domain in Oracle GlassFish Server 3.1 Administration Guide. To easily determine if a domain is running, use the asadmin list-domains command.

Was the Server Started at the Expected Port?

Description

The server might be running at a different port number than expected, either because it was intentionally installed there, or because another server was already running on the default port when the server was installed.

To Determine Which Port Number the Server Is Using

1. Examine the server’s configuration file:

   as-install/domains/domain1/config/domain.xml

2. Find the network-listener element.
3. Inspect the value of the port attribute.Be sure to enter the correct port number when invoking the server.

   ---

   Note – The server’s default port number is 8080, however, there are a number of ways in which the expected value can change:

   • A different port number was specified during installation.
   • A previous installation exists.

   ---

Is a Personal Firewall Enabled?

Issues might result when personal firewalls are enabled. Disable your personal firewall and see if the server access problem still exists.

To Start a Domain

When you start a domain or server, the domain administration server (DAS) is started. After startup, the DAS runs constantly, listening for and accepting requests.

If the domain directory is not specified, the domain in the default as-install/domains directory is started. If there are two or more domains, the domain_name operand must be specified. Each domain must be started separately.

This subcommand is supported in local mode only.

• Start a domain by using the start-domain(1) subcommand.

Example 3-6 Starting a Domain

This example starts domain2 in the default domain directory.

asadmin> start-domain domain2

If there is only one domain, you can omit the domain name. If you do not include the password, you might be prompted to supply it.

Name of the domain started: [domain1] and its location: 
[C:\prelude\v3_prelude_release\distributions\web\target\glassfish
domains\domain1].
Admin port for the domain: [4848].

See Also

You can also view the full syntax and options of the subcommand by typing asadmin help start-domain at the command line.

To Stop a Domain

Stopping a domain or server shuts down its domain administration server (DAS). When stopping a domain, the DAS stops accepting new connections and then waits for all outstanding connections to complete. This shutdown process takes a few seconds. While the domain is stopped, the Administration Console and most of the asadmin subcommands cannot be used. This subcommand is particularly useful in stopping a runaway server. For more controlled situations, you can use the restart-domain(1) subcommand.

1. If necessary, notify users that you are going to stop the domain.
2. Stop the domain by using the stop-domain(1) subcommand.

Example 3-7 Stopping a Domain (or Server)

This example stops domain1 in the default directory, where domain1 is the only domain present in the directory.

asadmin> stop-domain
Waiting for the domain to stop ...........
Command stop-domain executed successfully.

See Also

You can also view the full syntax and options of the subcommand by typing asadmin help stop-domain at the command line.

To Restart a Domain

Use the restart-domain subcommand in remote mode to restart the Domain Administration Server (DAS) of the specified host. When restarting a domain, the DAS stops accepting new connections and then waits for all outstanding connections to complete. This shutdown process takes a few seconds. Until the domain has restarted, the Administration Console and most of the asadmin subcommands cannot be used.

This subcommand is particularly useful for environments where the server machine is secured and difficult to get to. With the right credentials, you can restart the server from a remote location as well as from the same machine.

If the server will not restart, use the stop-domain(1) subcommand followed by the start-domain(1) subcommand.

1. Ensure that the server is running.Remote subcommands require a running server.
2. Restart the domain by using the restart-domain(1) subcommand.

Example 3-8 Restarting a Domain (or Server)

This example restarts mydoimain4 in the default directory.

asadmin> restart-domain mydomain4
Waiting for the domain to restart ...........
Command restart-domain executed successfully.

Example 3-9 Restarting a Domain in a Browser

This example invokes the restart-domain subcommand in a browser.

http://yourhost:4848/__asadmin/restart-domain