iProcess Objects and iProcess Server Objects Behavior The following table shows how different TIBCO iProcess Objects and TIBCO iProcess Server Objects components behave in the event of a database failure or failover. iProcess Objects/iProcess Server Objects Components Behavior When Failure or Failover Occurs iProcess Objects Server From the viewpoint of a database failure or failover, the iProcess Objects Server is a TIBCO iProcess Engine server process. As such, its behavior is the same as any other TIBCO iProcess Engine server process - see Server processes. iProcess Objects Clients and iProcess Server Objects Clients Existing iProcess Objects/iProcess Server Objects client sessions may be unaffected by a database failure or failover, as many client operations - such as retrieving information about a work item from the WIS cache - do not require access to the database. iProcess Objects/iProcess Server Objects client behavior is only affected when an operation that requires access to the database is performed - for example, opening a procedure. The client passes a request to the iProcess Objects Server, which passes it to the TIBCO iProcess Engine, which in turn tries to access the database. The request therefore hangs until the database connection returns. If this period exceeds the iProcess Objects Server’s RPC timeout period (by default, 25 seconds), a timeout exception is returned to the iProcess Objects/iProcess Server Objects client. It is the iProcess Objects/iProcess Server Objects client’s responsibility to handle that exception.