# Configuration Files

When an active server fails, its standby server assumes the status of the active server and resumes operation. Before becoming the active server, the standby server re-reads its configuration files.

If the two servers share configuration files, then the administrative changes to an active server carry over to its standby once the latter becomes active.

Note: When fault-tolerant servers share configuration files, you must limit configuration changes to the active server only. Separately reconfiguring the standby server can cause it to overwrite the shared configuration files; unintended misconfiguration can result.

Additionally, when a server that is a member of a fault-tolerant pair requires a restart, both servers must be restarted to activate the change. When the active server is shut down, the standby server does not reinitialize its properties (such as listens, heartbeats, timeouts, and so on) or stores during activation. It does reinitialize objects such as queues, topics, factories, routes, and so on.

Copyright © Cloud Software Group, Inc. All rights reserved.