Jboss 7 online training
Published Articles » JBoss
There will be lot of business cases to be executed for an application. Consider a scenario that you want to execute on business case only once across the cluster.
In this scenario if one node picks up the task then the other node should not pick the same task. so use HA singleton for this.
We can run Jboss on port other than the default port 8080.
In order to do this we have to change the port entry in server.xml
change the port number from 8080 to what ever you wish.
This will allow the Jboss to start in your
Go to the following directory jboss-eap-5.1/jboss-as/server/default/deploy/jbossweb.sar
1. edit the server.xml
2. uncomment the line
<Connector protocol="HTTP/1.1" SSLEnabled="true"
Start the servers after enabling the cluster.
In order to manage all the nodes in one console log on to the below mentioned link
Note: Chnage the www.yourwiz.com with your hostname
In order to deploy your application without specifying any context path, You need to delete Root.war and deploy your application in the same name at the same location.
Once the JBoss is up it will point to the Root.war. Since your application is deployed over there, Jboss will point your application without any context path.
In a clustered environment the war or ear files needs to be deployed in each and every instances.
Using the farm deployment, the *.ear or *.war files will be deployed only in the farm directory.
JBoss will automatically deploy the *.ear or *.war in the farm directory to all instance in the cluster.
Note: Farm deployment w
Jboss instances are normally started using run.sh in foreground or background. If the Jboss server is started in the foreground then it can be stopped by using Ctrl-c. Consider a scenario where the Jboss server is started in the background and you want to stop the server. If we kill the Jboss instance then the server will stop abruptly. The correct way
If the heap size needs to be set for all the instance to the same value then use the run.conf in the bin directory
set the JAVA_OPTS value as
Thread dumps are generated by JVM either automatically or manually. In order to figure out a problem proactively, we might require to generate thread dumps in various scenarios.
Thread dumps are generated using the following command
kill -3 pid
Copy server/all to server/node1 by entering the following: