The AdminServer regularly checks the corresponding
*.properties files for changes (default location: <DLC>/properties).
- When a change is detected it automatically loads the new settings from the modified *.properties file without the need to restart the AdminServer.
- Any change that modifies the file timestamp will trigger the AdminServer warm start, for example a Linux touch command, manual edit of the ubroker.property file or changes with the mergeprop utility. When this occurs first there will be a WarmStartBegan message followed by a WarmStartFinished message. This alert is for informational purposes.
APPSERVER: ASBROKER1
ALERTS: WarmStartFinished
- Until the warmstart has completed no parallel change to the .properties should be performed. Concurrent changes to the ubroker.properties file (regardless of method) will cause problems. "Concurrent changes" mean making changes to the .properties file at the same time that the file is in use by a running AdminServer then committing further changes or making multiple changes in parallel like merging several properties files at the same time with mergeprop to one .properties file.
- After one change is made, the admserv.log file will show lines similar to the following:
[3] [AdminServer] Start doing partial warm start...
[0] [Fathom] * Alert! Alert Name: WarmStartBegan, Resource Name: <resource>, Severity: 4, Message: AdminServer started partial warm start. (11234)
[3] [AdminServer] Partial warm start has completed.
