The Auto Reconnect (-autoReconnect) client-session startup parameter serves two purposes:
  • For GUI and character-mode ABL sessions, indicates you want to re-establish connections to disconnected databases that were specified using startup parameters.
  • If OpenEdge replication is used, indicates that the primary replication target database should be included in the alternate database connection set, if the connection to the replication source database fails.
Operating system and syntax UNIX / Windows -autoReconnect
Use with Maximum value Minimum value Single-user default Multi-user default
Client Session
Re-establish connection for GUI and character-mode clients

When a STOP condition is raised, GUI and character-mode ABL sessions are reset and restarted if the STOP condition is not handled by the application. If -autoReconnect is specified, the AVM attempts to reestablish connections to any disconnected databases (including shared-memory connections) that were specified through startup parameters. This happens immediately before running the procedure specified by the -p startup parameter. If the database connections cannot be reestablished during a restart, the AVM does not attempt to run the procedure. Instead, the AVM exits to the operating system.

Auto Reconnect (-autoReconnect) only applies to GUI or character-mode clients. The parameter is a no-op if specified for batch-mode clients or application server sessions.

When running without -autoReconnect, the ABL session is reset and and the procedure specified by the -p startup parameter is run, without attempting to reconnect to any databases that were specified at startup using startup parameters.

For more information, see Learn about automatic database reconnect.

Re-establish connection to an OpenEdge replication database

By using the -autoReconnect client-session startup parameter, remote clients can automatically connect to an OpenEdge replication primary target database, if the connection to the OpenEdge replication source database fails. When an OpenEdge database fails over (planned or unplanned) to a replication target database, then remote clients (ABL clients or Progress Application Server for OpenEdge agents) running the application, automatically connect to the replication primary target database.

For more information, see Automatic database reconnection with OpenEdge replication.