Welcome to the JBoss FAQ at JavaRanch. You will surprised to know that many of the questions that get asked in the forums have already been asked and answered many times before. This JBoss FAQ page is an effort to consolidate all such questions (forum discussions) in one place, so that ranchers can easily and quickly find answers to their questions.
This page is open for edits/additions for any registered JavaRanch member. If you find anything that's incorrect or is missing on this page, feel free to edit this page. If you are new to editing wiki pages at JavaRanch, then please take a look at a quick tutorial on editing wiki pages. Don't worry, these wiki pages are versioned, so if anything goes wrong, we can always revert page to a previous version. Feel free to contact any forum moderator, in such cases - they are always ready to help.
Finally, if this FAQ doesn't answer your questions, then feel free to visit our JBoss Forum to ask your question. Also, if you believe that the forum discussion that you started, is some commonly asked question (which hasn't been covered in this JBoss FAQ) then please add it here (with a bit of details).
The word JBoss, on it's own, is just a brand name. However, due to the popularity of JBoss Application Server, most of the times, when people refer to JBoss, they usually are talking about the JBoss Application Server.
As has been mentioned in those threads, starting JBoss AS 4.2.x, the server now binds only to localhost by default. The reasons for doing that are mentioned here. The solution is to use the -b option with the run.sh/run.bat script while starting the server.
where IP address is the address to which you want to bind the services. Passing 0.0.0.0 as the value to -b binds the services to all addresses, but isn't recommended. See the JBoss42FAQ for more details.
Since the early days, JBoss Application Server used to (and continues to) ship with the jmx-console and web-console which were the only consoles available in JBoss. These consoles did not have much of an admin functionality. The jmx-console was meant to interact with the MBeans deployed in JBoss. Since JBoss itself had a JMX kernel (in JBoss AS 3.x and JBoss AS 4.x), most of the admin functions like deploying applications (in a limited way) or taking thread dumps were done from this console. Although, the jmx-console provided some of the admin functions, it was never a tool which the JBoss admins could use. Expectedly, there were users who wanted to have a better console for administration. Some such discussions are here:
However, starting JBoss AS 5.1.0.CR1, JBoss AS now ships with an admin console. The console is by default available at http://localhost:8080/admin-console (replace localhost and port with the correct IP/port of your server). Some forum discussions related to JBoss admin console, that you might find useful are here: