Multi-Tier Request Broker Shutdown Options

The OpenLink Request Broker can be shut down in various ways, using the available command line options.

Usage:
  oplshut [-hcskryfpP] [+hostname arg] [+configfile arg] [+show] [+kill]
          [+reinit] [+yes] [+force] [+protocol arg] [+port num] [pid ..]
  +hostname     contact oplrqb on given host
  +configfile   use alternate configuration file
  +show         show database agent connections
  +kill         kill a database agent
  +reinit       oplrqb must reread the rulebook
  +yes          don't ask for confirmation
  +force        force immediate shutdown (kill all)
  +protocol     specify protocol to use
  +port         specify port to use

Examples:
  oplshut            Shutdown broker on local machine (when idle)
  oplshut -f         Shutdown broker without waiting for clients to terminate
  oplshut -fy        Same as -f, but without asking for confirmation
  oplshut -s         Show the current active connections
  oplshut -k 81 93   Try to terminate the database agents with svpid 81 and 93

Command Line Examples

• oplshut
  
  
  Shuts down the Request Broker on the local machine. When a connection is still active, and the user calls oplshut without additional arguments, the broker will enter a gracefull shutdown state which means that it will not accept any new connections, but remains active until all active connections are terminated.
  
  
  
  • The shutdown state will be reported on the foreground screen or broker log:
    
    

    
    oplrqb: shutdown mode initiated by openlink@127.0.0.1
    

    
    
  • Any client that tries to connect to the broker will get the following error message:
    
    

    
    odbctest DSN=ora8i
    OpenLink ODBC Demonstration program
    This program shows an interactive SQL processor
    [OpenLink][ODBC]the broker is being shut down, SQLSTATE=08004
    [OpenLink][ODBC]Connection rejected by data source, SQLSTATE=08004
    

    
    
• oplshut -f
  
  
  Shuts down the Request Broker on the local machine without waiting for clients to terminate.
  
  
  
  • If you use the -f (or force) flag, the broker will kill all active connections regardless what the client application is doing, which can lead to problems if the applications are not written to handle such events. Depending on the database, open transactions will be rolled back etc.
    
    
    
  • Many databases like Oracle and Progress implement the same concept where the gracefull shutdown option is the default, but a shutdown can be forced in case of a big calamity, or when a connection remains lingering.
    
    
    
• oplshut -fy
  
  
  Same functionality as prior command, but without asking for confirmation.
  
  
  
• oplshut +port 16000
  
  
  Shuts down the Request Broker running on the TCP Listen port of "16000". Note that the default Request Broker Listen port is 5000, thus this option is not necessary unless you specified a different Listen port at install-time.
  
  
  
• oplshut -s
  
  
  Shows the current active OpenLink Data Access Client connections.
  
  
  
• oplshut -k 81 93
  
  
  Try to terminate the database agent sessions with process IDs 81 and 93.
  
  
  
• oplshut -h 12.34.56.78
  
  
  Shuts down the Request Broker on remote machine with IP address "12.34.56.78".