Application Is Disconnected Unexpectedly

If an application becomes disconnected from a TimesTen database, one of the following events occurs:

• If there was no outstanding transaction, the connection is cleanly removed by the TimesTen daemon. Other existing connections continue processing as if no problem had occurred.

• If there was an outstanding transaction, the transaction is rolled back and the connection is cleanly removed by the TimesTen daemon. Other existing connections continue processing as if no problem had occurred.

This section describes what to check if your application unexpectedly disconnects from the database.

Possible cause	See...
There is an internal application error.	Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL Application Errors for information.
There is failure of a concurrent application thread.	Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL Application Errors for information. Check the User Error Log for information.
If using a client/server connection, the client may have disconnected from the application.	Troubleshooting Client/Server Problems for information.
There is an error in the TimesTen library.	Contact TimesTen Customer Support.