-
1. Re: JBoss console issue.
arun2arunraj Apr 13, 2015 7:48 AM (in response to muthu.kumar)Hi Muthu Kumar,
Don't bind your Jboss instance with 0.0.0.0. Instead bind the Instance with specific IP Address like the below.
> standalone.bat -c standalone-full.xml -b 192.168.1.1
Thanks & Regards,
ArunRaj. R -
2. Re: JBoss console issue.
muthu.kumar Apr 13, 2015 10:49 AM (in response to arun2arunraj)Hi Arun
Tried the same. No luck. getting the same error. I used the actual ip of the system.
I saw the same issue got resolved in below forum using following command.
https://github.com/jboss-dockerfiles/wildfly/issues/3
docker run -it -p 8123:8080 -p 9123:9990 jboss/wildfly-custom /opt/jboss/wildfly/bin/domain.sh -b 0.0.0.0 -bmanagement 0.0.0.0 -Djboss.management.http.port=8124
Just want to validate the same and confirm Jboss forum.
Please suggest.
Thx
Muthu
-
3. Re: JBoss console issue.
jaikiran Apr 13, 2015 11:45 PM (in response to muthu.kumar)Are you using Docker?
What exact URL are you using to access the admin console? Are you accessing it from the same machine as the one running the server?
-
4. Re: JBoss console issue.
muthu.kumar Apr 14, 2015 2:01 AM (in response to jaikiran) -
5. Re: JBoss console issue.
jaikiran Apr 14, 2015 2:28 AM (in response to muthu.kumar)Use http://172.30.51.10:9990/console/ to access the console.
-
6. Re: JBoss console issue.
muthu.kumar Apr 14, 2015 2:44 AM (in response to jaikiran)Hi Jai
Tried the same in my server it self. No luck.
Thx
Muthu
-
7. Re: JBoss console issue.
jaysensharma Apr 14, 2015 3:04 AM (in response to muthu.kumar)Hello Muthu,
As you mentioned in your initial issue description that you are starting your JBoss as following:
standalone.bat -c standalone-full.xml -b 0.0.0.0
Above means that the public interface (-b) is set to run on all the available interface addresses (like IP, 172.30.51.10, localhost, 127.0.0.1) which means you should be able to access the applications deployed on EAP6 using those addresses. BUT if you want to access your Management Console then you will have two options:
Option-1). Start EAP as standalone.bat -c standalone-full.xml -b 0.0.0.0 And Access the Console using localhost as http://localhost:9990/console
Option-2). If you want to access the console via IP Address then (as it is by default bound to localhost) then use the "-bmanagement" option to start your JBoss, then try http://172.30.51.10:9990/console
standalone.bat -c standalone-full.xml -b 0.0.0.0 -bmanagement 172.30.51.10
-
8. Re: JBoss console issue.
lylewang Apr 14, 2015 3:36 AM (in response to muthu.kumar)If you try to check your server log for the startup, you should be able to find out the exact IP / Port bindings, search for those lines like below in server.log
......
16:58:48,878 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://IP:port/management
16:58:48,878 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://IP:port
......
-
9. Re: JBoss console issue.
muthu.kumar Apr 14, 2015 3:56 AM (in response to jaysensharma)Thanks Jay
I restarted the Jboss with new option you suggested.
standalone.bat -c standalone-full.xml -b 0.0.0.0 -bmanagement 172.30.51.10
Now I am able to login to console..from server and from any machine in network with out any issue.
Many thanks to Jay , Arun and Lyle.
Thanks
Muthukumar.S