Behavioral Change: dev environment impact due to agent preferences handling
Jay Shaughnessy
jshaughn at redhat.com
Mon Mar 25 18:50:48 UTC 2013
I just pushed changes for
https://bugzilla.redhat.com/show_bug.cgi?id=824010. With this change
the agent no longer uses the native implementation of Java Preferences.
Instead, it uses our custom implementation (FilePreferences.java). Now
the agent configuration will be stored in a configurable file, as
opposed to the default file location on Linux and the registry on windows.
By default, and there shouldn't be a lot of need to change from the
default, the agent config will be placed in
RHQ_AGENT_HOME/conf/agent-prefs.properties.
For new agents there shouldn't be any discernible difference in
behavior, other than the new file being generated. For existing agents
the preferences will be migrated from the native storage to our file
storage during the agent auto update procedure.
BUT, for your dev environments, where you likely don't go through an
autoupdate, you have a few options. Start by:
1) bring down your agent.
2) rebuild the agent: mvn -Pagent
Option 1 (easiest, new agent):
3) delete your registered agent, either via the new Delete button
under Administration->Topology->Agents or by just doing a dbsetup.
4) start your new agent and enter the setup info as usual
Option 2 (recommended, autoupdate):
3) rebuild the appserver/autoupdate module
4) copy the autoupdate jar to your agent home dir
5) > java -jar rhq-enterprise-agentupdate-4.7.0-SNAPSHOT.jar -u
6)your updated agent should now be running and using the migrated prefs
Note, option 1 will leave your old prefs in the native prefs store.
Option 2 will clean them up as part of the migration. If you have time
try option 2, it will test the code better and do the cleanup.
Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/rhq-devel/attachments/20130325/da42e9f3/attachment.html>
More information about the rhq-devel
mailing list