Windows – Can Not Start Glassfish 4.1 Server, Download, Unzip, Install, Windows 8.1

command lineglassfishjavawindowszip

Before I start I wanted to say, I have to put a space in many of the links because I am new to superuser & have restrictions. You'll find the spaces http:// (HERE) localhost:4848/. I'm sorry for the inconvenience, I hope this restriction will be lifted soon.

I can not start, Glassfish 4.1 server.
I'm running, Windows 8.1, 64x.

I downloaded, Java EE 7 Full Platform glassfish-4.1.zip
From here: https://glassfish.java.net/download.html

Unzipped with, 7-Zip 9.20. Put zipped in a folder with my other zipped.
Put unzipped in C.

Path: C:\glassfish-4.1
Next inside, glassfish4.

Path: C:\glassfish-4.1\glassfish4
pic

Next inside, bin.

Path: C:\glassfish-4.1\glassfish4\bin
enter image description here

Now in, asadmin Windows Batch File, opens Command prompt, C:\Windows\system32\cmd.exe, asadmin>.

Enter, start-domain, Then cmd.exe outputs Waiting for domain1 to start……..(lots of these)……serverNoStart
Command start-domain failded.

Opened, pkg, ran it, it installed.
enter image description here

Opened, updatetools ran it, it installed.
enter image description here

Again, in asadmin Windows Batch File, opens Command prompt, C:\Windows\system32\cmd.exe, asadmin>.

Enter, start-domain, Then cmd.exe outputs Waiting for domain1 to start……..(lots of these)……serverNoStart
Command start-domain failded.

If I try asadmin start-domain or glassfish4/bin/asadmin start-domain from this location I get the following.
enter image description here

I'd like to better understand the nature of this problem. Suggestions on how to fix/start server?

P.S. when I check http://localhost:4848/
enter image description here

P.S.S. when I try to start GlassFish from Netbeans…

enter image description here

Best Answer

The last screenshot where you try to start GlassFish through Netbeans suggests that there is already something running which is bound to port 8080 and/or port 8443. Check if there's no other application server (Tomcat etc) currently running.

Aside from that, your server log should tell you what is going wrong:

C:\glassfish-4.1\glassfish4\glassfish\domains\domain1\logs\server.log
Related Question