Server-side Cursors Causes Hanging Connections In SequeLink Server For MS SQL Server

Technote (FAQ)
Problem
Using DataDirect Technologies (formerly known as MERANT) SequeLink Server, the database connections remain hung after the application has disconnected. Over a period of time, this causes the system to freeze.
Cause
The problem is with the SequeLink server, where hanging processes are clearly visible on the SequeLink Console as well as MS SQL Server Query Analyzer.

There is no problem using the same application with SequeLink Server for Oracle
Solution
Switching from Serverside to Clientside cursors fixed the problem.

For SequeLink Server 5.1 for Microsoft SQL Server, the SequeLink Datasource attribute is called DataSourceMSSCursorType. It should be set to clientside.

1. Launch the SequeLink 5.1 Manager Snapin and navigate to the datasource.



2. Right click on datasource (Default in this example), select New, then select Attribute. From the New Attribute windows, select DataSourceMSSCursorType for Attribute, and select Clientside for the Value.


3. Click OK

4. Save the configuration

5. Restart the SequeLink service for SQL Server.

Related information
DataDirect JDBC Product Documentation

Product Alias/Synonym
Merant SequeLink Server











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Java 2 Connectivity (J2C)
Operating system(s): AIX, HPUX, Linux, Multi-Platform, Solaris, Windows, Windows 2000, Windows NT
Software version: 3.5, 3.5.1, 3.5.2, 3.5.3, 3.5.4, 3.5.4.1, 3.5.4.2, 3.5.5, 3.5.6, 3.5.7, 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.1, 5.0, 5.0.1, 5.0.2, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.2.4, 5.0.2.5, 5.0.2.6, 5.1, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, 5.1.1, 5.0.2.7
Software edition: Advanced, Base, Edition Independent, Express, Network Deployment, Single Server
Reference #: 1178130
IBM Group: Software Group
Modified date: 2004-08-28