Jboss standalone-full.xml file getting overridden while restart

jboss

I have modified the standalone-full.xml while jboss is running. And then I have restarted the jboss instance. My change is not available in the file (standalone-full.xml) after restarting. Seems, previous version (before modification) got restored.
But sometimes, changes are reflecting after restarting.
Its confusing. Any Idea, what is happening while restart?

Best Answer

I have modified the standalone-full.xml while jboss is running.

JBoss actively manages the server configuration, and rewrites the XML based on events that take place during its operation. I am assuming that you made these modifications by editing the XML directly using a text editor. While you can do this with little impact while the server is offline, doing this while the server is running yields unpredictable results, as you have found.

You can definitely make changes to the server's configuration while it is running, but for it to be consistently applied you should use the web management console (http://localhost:8080/console) or the CLI (${JBOSS_HOME}/bin/jboss-cli.sh). Making your changes this way, you can even get feedback on whether your change will require the restart of JBoss.

Related Solutions

JBoss: reload log4j config without restarting the server

Looks like JBoss actually does reload the log4j config automatically. But contrary to the other hot-pluggable files (like deploys or other server config) it does not happen instantaneously but at a set interval of 60 seconds.

I guess I was just to fast and impatient to notice this.

Here some more info on the matter:
http://blog.techstacks.com/2009/03/dynamically-updating-log-levels-in-jboss.html

Crontab to restart jboss server

The run.sh script saves logging infomration on console. If you want to run it in background you should:

Redirect output to /dev/null:
```
run.sh -c all &> /dev/null &
```
Turn off console logging in the login-conf.xml.

But I think the best solution if will be use jboss_init_redhat.sh script. You can find it in the bin directory (the same where the run.sh script is placed).

The jboss_init_redhat.sh script is wrapper on run.sh which allow you to use it as Init V script - it has such parameters like start, stop. You have to set up it properly but its quite easy - just open it and edit some bash variables.

You can have some problems when you use some user to connect to JMX console. In that case you have to modify that script and add credential - the JMX use used to stop JBoss instance.

You have to modify JBOSS_CMD_STOP variable and add there your credentials.

Best Answer

Related Solutions

JBoss: reload log4j config without restarting the server

Crontab to restart jboss server

Related Topic