Nonstop Database, HiRDB Version 9 UAP Development Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
4.15.4 Notes about using the automatic reconnect facility
- The automatic reconnect facility cannot be used if the UAP contains a LOCK statement that specifies UNTIL DISCONNECT.
- If the UAP that uses a holdable cursor is being used, the automatic reconnect facility returns an error to the UAP, even if a transaction is not being processed.
- If the JDBC driver#1 or DABroker for JAVA#2 accesses the system and a statement that applies over several transactions is effective, the JDBC statement becomes ineffective after the automatic reconnect facility reconnects the HiRDB client. In this case, the prepareStatement() method must be executed again.
- If the time specified in PDCWAITTIME is reached by the first SQL statement of the transaction, HiRDB re-executes the CONNECT statement and SQL statement without returning an error to the UAP. Therefore, HiRDB might return an error when the amount of time equivalent to about twice the PDCWAITTIME value is reached.
- If Cosminexus is connected and DB Connector's statement pooling facility is enabled, an SQLException exception including the KFPA11901-E message might occur when an SQL statement is executed after connection has been re-established by HiRDB's automatic reconnect facility. If you use the statement pooling facility, do not use the automatic reconnect facility. For details about the statement pooling facility, see the Cosminexus Application Setup Guide.
- #1: When the JDBC driver is used, a statement that applies over several transactions becomes effective when "CLOSE" or "RESERVE" is set to COMMIT_BEHAVIOR. COMMIT_BEHAVIOR can be set with the Properties info argument of the connect method in the Driver class, the Properties info argument of the DriverManager.getConnection method, or the COMMIT_BEHAVIOR key in a URL connection.
- #2: When DABroker for JAVA is used, a statement that applies over several transactions becomes effective when the DABroker version is 03-06 or later and the DABroker for JAVA version is 02-10 or later.
All Rights Reserved. Copyright (C) 2011, Hitachi, Ltd.