Glassfish admin-listener disabled by mistake.

Glassfish has a set of network listeners which are named are follows:
1.http-listener1
2.http-listener2
3.admin-listener
 
An HTTP listener named admin-listener, associated with the virtual server named __asadmin. For this listener, security is not enabled.
The admin-listener is used to listen  to the administrative Glassfish console  where you can configure all the settings for the  specific Glassfish domain.

HTTP listeners associated with the virtual server named server:  
The listener named http-listener-1 does not have security enabled.
The listener named http-listener-2 has security enabled.

Now we will focus on the error in which you might encounter when you by mistake disable the admin-listener.

SOLUTION is:

1. in command prompt run this command
 tasklist
 It will get the list of all the tasks and their process Id's.
2.Run netstat -a -o -n and check which process is using the port of your glassfish listener.
It will usually be a java process. End that java process if you know what it is.
3.If this does not work follow the following methods :

Glassfish always has its server log in the specific domain folder
The file structure will usually be something like glassfishv3/glassfish/domains/domain1/config/domain.xml.

Edit the domain.xml file. First check there is no process which is locking the file otherwise you will not be able to edit it.

Study the file beforehand and you will see there is a specification at the bottom like this
<network-listeners><network-listener port="8080" protocol="http-listener-1" transport="tcp" name="http-listener-1" thread-pool="http-thread-pool" />
  <network-listener port="8181" protocol="http-listener-2" transport="tcp" name="http-listener-2" thread-pool="http-thread-pool" />
  <network-listener port="4848" enabled="false"  protocol="admin-listener" transport="tcp" name="admin-listener" thread-pool="http-thread-pool" />
  </network-listeners>

Check whether these ports are open using the nestat -a command.
If  the ports are used you might see in the server logs which are located in
glassfishv3/glassfish/domains/domain1/logs/server.log there will be a message stating that the ports are already used.

In that case simply change the port number which has been specified in the error to something else.

Now focusing on our main problem if you have changed the  enabled="false" to enabled="true" it should solve your problem. :)

If you make a mistake in editing the domain.xml there is a domain.xml.bak which you can simply rename to the domain.xml file.

Cheers mate .. Hope this helps.
Any other problems simply email them to my email address and I will get back as soon as possible

jos.sanika@gmail.com