JBoss server – How to Start and Stop? | Baeldung

We ’ rhenium looking for a DevOps mastermind with knock, LAMP, and LEMP stack experience : Read More

1. Introduction

In this tutorial, we ‘ll have a look at how to start and stop a JBoss application waiter .
first gear, we ‘ll explore the operate modes of this waiter. far, we ‘ll discuss how to start and stop the server in each of these operate modes.

JBoss is an open source application server developed by RedHat and is now known as WildFly. We can download it from the official WildFly web site .
We can operate this waiter in two different modes. however, the key difference between these modes lies in the management of the server .

2. JBoss Standalone Server

In this mode, each standalone waiter exemplify is an mugwump process. consequently, we have to manage each of these servers individually. In early words, we can launch multiple instances of the standalone servers in case multi-server configuration is desired.
however, we ‘ll need to deploy the application on each waiter individually .

2.1. Preferences and Configurations

The standalone inauguration script i.e. standalone.sh for OSX/Linux and standalone.bat for Windows, utilizes :

  • standalone.conf/standalone.conf.bat: defines the JVM preferences for the standalone server instance
  • standalone.xml: defines the default configurations for the server; we can find it under $JBOSS_HOME/standalone/configuration.

JBoss besides provides some alternate configurations in the same directory :

  • standalone-ee8.xml: same as standalone.xml, but with EE8 technologies enabled
  • standalone-ha.xml: Java Enterprise Edition 7 web profile certified configuration with high availability
  • standalone-full.xml: Java Enterprise Edition 7 full profile certified configuration including all the required EE 7 technologies
  • standalone-full-ha.xml: Java Enterprise Edition 7 full profile certified configuration with high availability

2.2. Starting the Server

Let ‘s open a terminal in OSX/Linux or a command immediate in Windows and navigate to the $ JBOSS_HOME/bin directory. promote, we ‘ll start the standalone waiter with nonpayment configuration by running :


in OSX/Linux or in Windows :


similarly, we can start the standalone waiter with an alternate shape, say with EE8 capabilities, by executing :

standalone.sh --server-config=standalone-ee8.xml

in OSX/Linux or in Windows :

standalone.bat --server-config=standalone-ee8.xml

furthermore, to check if the startup is successful, we can open up a browser and navigate to http : //localhost:8080/. It ‘ll show the default WildFly welcome page .

2.3. Stopping the Server

To stop the server we can just press “ CTRL+C ” .
additionally, jboss-cli could be utilized for issuing commands to the running example of the server. For case, we can use it to shut down the waiter .
Let ‘s open a new concluding or a control prompt and run :

./jboss-cli.sh --connect command:shutdown

in OSX/Linux and in Windows :

./jboss-cli.bat --connect command:shutdown

3. Managed Domain Servers

In this mode, we can manage multiple instances of the server from a single control point. These servers are logically members of a one sphere. here, a single Domain Controller process acts as the central management control point .
By default, JBoss provides few instances of the waiter. We can find these instances under $ JBOSS_HOME/domain/servers directory .

3.1. Preferences and Configurations

The domain inauguration script i.e. domain.sh for OSX/Linux and domain.bat for Windows utilizes :

  • domain.conf/domain.conf.bat: defines the JVM preferences for the servers under the domain
  • domain.xml: defines the configurations for the domain; we can find it under $JBOSS_HOME/domain/configuration.

additionally, we can define our custom shape for operating these servers alike to the interchange configurations of the standalone waiter .

3.2. Starting the Server

The process of starting the server under a managed domain remains the lapp as the standalone server. however, rather of standalone.sh/domain.bat, we ‘ll use domain.sh/domain.bat .
consequently, this will spin up multiple servers instances under a single world .

3.3. Stopping the Server

To stop all the servers we can simply press “ CTRL+C ”. furthermore, we can stop a specific waiter using jboss-cli .
Let ‘s open a new end or a command immediate and run :

jboss-cli.sh --connect

in OSX/Linux or in Windows :

jboss-cli.bat --connect

soon, we are connected to the sphere control. here, we can issue commands to multiple instances of the server. For example, to view all the servers under this world :


similarly, to stop a specific case of the waiter, we ‘ll execute :


accordingly, we can check the status of this server :


4. Conclusion

In this short usher, we explored how to start and stop the application server with unlike configurations .
For further reading, we have an article that describes the action of deploying a war file on the JBoss lotion server.

Generic bottom

Get started with Spring 5 and Spring Boot 2, through the Learn Spring course:

Generic footer banner

source : https://thefartiste.com
Category : Tech

About admin

I am the owner of the website thefartiste.com, my purpose is to bring all the most useful information to users.

Check Also


Manage participants in a zoom meeting webinar

Call the people who attend the meet as follows Alternate host host Who scheduled the …

Leave a Reply

Your email address will not be published.