Problem: The Refresh button in the Server Configuration node does not display correct properties or values, despite changes being made and saved. Updates consequently appear to have been lost. In some scenarios, when you save the Server Configuration, it fails with the message Save Failed.
Scenario 1: After restarting Unwired Server, refreshing the server configuration displays the first saved change, but not subsequent saved updates. The message Save Failed appears in the administration console after you attempt to save an update.
In this scenario, the second save was likely unsuccessful. The message Save Failed indicates a conflict with the first set of updates.
Cumulative saved changes are applied successfully upon server restart only if these updates do not conflict. Attempting to save two conflicting sets of changes fails.
Solution: Inject a server restart in between each saved change to ensure that the required updates are propagated across the server.
Scenario 2: After restarting Unwired Server, refreshing the server configuration displays the final saved update, but not previous ones.
The refresh action following saved configuration changes must be used in conjunction with an Unwired Server restart. Refreshing the server configuration displays the latest successfully saved configuration information.
Solution: If you refresh the configuration after saving updates to it, restart Unwired Server immediately to apply those changes before making another set of updates. Otherwise, the first set of configuration changes will be lost. The Refresh button allows you to then validate that those changes are applied and used by Unwired Server. For details on how to refresh the server in the correct sequence, see Saving and Refreshing an Unwired Server Configuration in the Sybase Control Center online help.