Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.1 |  CUBRID 8.4.3 |  CUBRID 9.0.0 | 



The cci_set_query_timeout function configures timeout value for query execution.

The timeout value configured by cci_set_query_timeout affects cci_prepare, cci_execute, cci_execute_array, an  cci_execute_batch functions. When timeout occurs in the function and if the disconnect_on_query_timeout value configured in cci_connect_with_url connection URL is yes, it returns the CCI_ER_QUERY_TIMEOUT error.

These functions can return the CCI_ER_LOGIN_TIMEOUT error in case that login_timeout is configured in the connection URL, which is an argument of cci_connect_with_url function; this means that login timeout happens between application client and server (CAS) during re-connection.

It is going through the process of re-connection between application client and server (CAS) when an application restarts or it is re-scheduled. Re-scheduling is a process that an application server chooses an application client, and starts and stops connection in the unit of transaction. If KEEP_CONNECTION, Broker parameter, is OFF, it always happens; if AUTO, it can happen depending on its situation. For details, see "Performance Tuning > Broker Configuration > Parameter by Broker."


int cci_set_query_timeout (int req_handle, int milli_sec);

  • req_handle : (IN) Request handle
  • milli_sec : (IN) Timeout (unit: msec.)
Return Value
  • Success : Request handle ID (int)
  • Failure : Error code
Error Code