Sun Microsystems 820682310 manual Server Will Not Start on Windows Port Conflict, Start the server

Server Will Not Start on Windows (Port Conflict)

Note – The commands will still expect a value for --username (or -u) and --password (or -w). But these can be dummy values, since the server side does not impose any security.

4Start the server.

At this point, the server does not have command-line security.

5Create a plain text file that defines theAS_ADMIN_USERPASSWORD variable as follows:

AS_ADMIN_USERPASSWORD=adminpassword

adminpassword Your choice of password for the administration user's password.

6Create an administration user whose password is the password that you defined in the preceding step.

asadmin create-file-user --groups asadmin --passwordfile=password-file adminuser passwordfile The full path to the file that you created in the previous step.

adminuser The name of the user that you are creating.

This command adds an entry to the as-install/domains/domain-name/config/keyfile file.

7Uncomment the <security-constraint>element in the web.xml file.

8Restart the server for the new user name-password to take effect.

Note – After the server is restarted, remote commands must specify adminuser as the administration user and adminpassword as the administration password.

Server Will Not Start on Windows (Port Conflict)

If a message similar to the following is displayed when starting Enterprise Server on Microsoft Windows, a server port conflict has occurred:

Address already in use

This error occurs when another application is running on the Enterprise Server port (default 8080), or because a previous instance of Enterprise Server did not shut down cleanly.

You might also check the following:

■“Is Another Application Running on the Server's Port?” on page 28

■“Has an Ungraceful Shutdown Occurred on a Previously Running Server?” on page 28

Chapter 2 • Specific Issues 27