new automatic startup reconfig

John Mazzitelli mazz at redhat.com
Tue Jan 8 15:50:08 UTC 2013


> Sounds harmless except for the strange messages a user may see. Is it
> the startup script that is running the installer with the --reconfig
> before starting the server or is this just part of our server startup
> process? In other words, is there a startup method that might
> accidentally bypass this --reconfig step?

It is the startup script itself that launches "installer --reconfig". You'll see the line added in rhq-server.sh (or .bat) where it runs rhq-installer --reconfig at the same time it runs the actual RHQ Server.

Yes, if a customer wants to write their own startup mechanism, they will have to remember to run "installer.sh --reconfig" if they ever change .properties or they can do what we did and run that every time you restart the server.

Remember, you do not have to run this automatically every time you start the server like we are doing. We are only doing this as a convenience for the user because we assume people either will not know they have to run "installer --reconfig" or they will forget.

But if they are disciplined, and they know "if I change .properties, I should run installer --reconfig after I restart the server", then they can avoid doing this every time automatically when the server starts and only run reconfig when they need to.

It's a real bummer and it's a shame we have to jump through these hoops (especially when you consider this worked great in JBossAS 4) but it is what it is and we need to work around these AS7 problems until they are fixed in AS7.


More information about the rhq-devel mailing list