Problem Note 33382: Attempting to set up a connection pool with the SAS® IOM driver for JDBC might cause errors to occur
When you attempt to set up a connection pool with the SAS IOM driver for JDBC, you might receive one of the following errors:
Datasource cannot be used as one phase.... null
DataSource class cannot be used as one phase
ClassCastException: com.sas.rio.MVADriver
Select the Hot Fix tab in this note to access the hot fix for this issue.
The following procedure shows how to use JDBC connection pooling with IBM WebSphere 6.0. In this procedure it is necessary to use the SAS IOM driver for JDBC in conjunction with the Apache Database connection pooling services (DBCP).
The WebSphere Connection Pool requires that the JDBC driver that is being used must implement the XADataSource method. Note that none of the SAS JDBC drivers implement this method at this time.
By using the Apache database connection pooling services to handle the pooling methods that are not implemented at this time, you can setup a JDBC connection pool in WebSphere 6.0.
Preparing for JDBC Connection-Pooling Setup
To set up JDBC connection pooling with IBM WebSphere Application Server 6.0, you must use the following driver and Java components:
- the SAS IOM JDBC driver, which is available in the hox fix that is referenced in this note.
- the latest JAR files from the following Apache projects which are available from the Apache Commons Web site.
Setting Up WebSphere 6.0
- Start the WebSphere Application Server.
- Set your browser to the WebSphere Administrative Console application.
- Click Logon.
- Log on to the WebSphere Administrative Console. By default, an account and password are not required.
- On the left side of the console, navigate through the hierarchy to the Preparing for Application Installation wizard.
- Click Resources ► JDBC Providers.
- Click New.
- In the Step 1 list box, select User Defined. The other boxes will populate automatically.
- Click Next.
- In the Name text box, type a descriptive name for the JDBC provider, for example, SAS JDBC Provider.
- In the Class path text box enter, the paths for the JAR files from the Apache downloads and the JAR files from the SAS IOM JDBC driver that is available from the hot fix. Enter each JAR file on its own line, similar to the following example:
From the Apache Commons Projects:
C:\temp\commons-collections-3.X.X.jar
C:\temp\commons-dbcp-1.X.X.jar
C:\temp\commons-pool-1.X.jar
From the SAS IOM driver for JDBC:
C:\temp\sas.intrnet.javatools.jar
C:\temp\sas.svc.connection.jar
- In the Implementation class name field, type org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
Note that this character string is case-sensitive.
- Click Apply.
- Under the Additional Properties menu, click Data sources.
- Click New.
- Type a descriptive name for your data source name, such as SASDB, in the Name text block.
- Under Data store helper class name, select Generic data store helper.
- Click Apply.
- Click the Custom Properties link.
- Click New and add the two following properties:
- In the Name field, enter url.
- In the Value field, enter jdbc:sasiom://your-server-name:IOM-port-number.
- Click OK.
- Click New and add the two following properties:
- In the Name field, enter driver.
- In the Value field, enter com.sas.rio.MVADriver. Note: This string is case sensitive.
- Click OK.
- Click the Save link.
- Click Save.
Operating System and Release Information
SAS System | SAS Integration Technologies | z/OS | 9.1 TS1M3 SP4 | |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M3 SP4 | |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | |
Microsoft® Windows® for x64 | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | |
Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | |
Windows Vista | 9.1 TS1M3 SP4 | |
64-bit Enabled AIX | 9.1 TS1M3 SP4 | |
64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | |
64-bit Enabled Solaris | 9.1 TS1M3 SP4 | |
HP-UX IPF | 9.1 TS1M3 SP4 | |
Linux | 9.1 TS1M3 SP4 | |
Linux on Itanium | 9.1 TS1M3 SP4 | |
OpenVMS Alpha | 9.1 TS1M3 SP4 | |
Solaris for x64 | 9.1 TS1M3 SP4 | |
Tru64 UNIX | 9.1 TS1M3 SP4 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2008-10-01 10:07:45 |
Date Created: | 2008-09-23 10:53:48 |