Listing 2 shows two connection handles reuse the same physical connection in one LTC.
清单2显示了在一个LTC中两个连接句柄重用相同的物理连接。
Connections conn1 and conn2 are two connection handles acquired from the same data source, ds.
连接conn1和conn2是从同一数据源ds获取的两个连接句柄。
The first set addresses limitations in the way application servers could manage connection handles under previous JCA versions.
第一组接口解除了以前JCA版本中应用服务器管理连接句柄方式的限制。
Multiple getConnection calls in one global transaction or LTC will return connection handles with different physical connections.
在一个全局事务或LTC 中的多个getConnection调用将返回包含不同物理连接的连接句柄。
Within a Local Transaction Containment (LTC) boundary, you cannot have multiple active connection handles that use the same physical connections.
在一个本地事务容器(Local Transaction Containment,LTC)边界中,您不能拥有多个使用同一物理连接的活动连接句柄。
For transparent switch over, applications can be coded to catch the StaleConnection exception and retry a specified number of times to obtain new connection handles.
为了能够透明地切换,可以将应用程序编码为捕获StaleConnection异常,并重试指定的连接次数来获取新的连接句柄。
The initial JCA release provided a detailed life-cycle model for managed connections and their associated connection handles, but it included no such concept for the resource adapter as a whole.
最初的JCA版本为托管连接及其相关联的连接句柄提供了详细的生命周期模式,但是它没有为资源适配器提供这种概念。
Listing 1 shows an example of two connection handles, one connecting to an Informix server and the other connecting to a DB2 server, and how a table is created in both Informix and DB2 databases.
清单1展示一个包含两个连接句柄的示例,其中一个连接到Informix服务器,另一个连接到DB 2服务器,并展示如何在Informix和DB 2数据库中创建表格。
Connection handles conn1 and conn2 will have different physical connections. This application may fail in one of the two following scenarios.
连接句柄conn1和conn2将有不同的物理连接。
Connection handles conn1 and conn2 will have different physical connections. This application may fail in one of the two following scenarios.
连接句柄conn1和conn2将有不同的物理连接。
应用推荐