I get intermittent Dr. Watson errors (access exceptions) running servlets which access Microsoft Sequel Server via JDBC using the ODBC bridge driver. This is running in JRun 3.0 Professional version. Anybody got a clue on this one? If ODBC bridge driver is the problem, anybody know of a better driver on a free download basis?
Jesse Tilly
Ranch Hand
Joined: Jun 25, 2000
Posts: 37
posted
0
The Type I driver isn't that good. Why the requirement for a zero-cost driver? Sounds like it's pretty expensive in terms of time working around the problems. I couldn't find anything on JRun's site mentioning included JDBC drivers (WebLogic comes with drivers) http://www.openlinksw.com/info/pricing.htm That's a pricing list for some MS SQL Server Type II/IV drivers. Looks like the max you could pay if $6000. If your site needed that many concurrent connections, $6000 is cheap insurance. As for the Type I driver, it should work. Confirm using MS Query (or another ODBC-using application) to make sure that the client's ODBC configuration is correct. You may need an updated MS SQL ODBC driver or you may have a corrupted installation. Make sure the driver DLL isn't found in more than one place. Jesse
Yoo-Jin Lee
Ranch Hand
Joined: Nov 01, 2000
Posts: 119
posted
0
Hi, What kind of exceptions are you getting? If you cannot connect to SQL Server perhaps you misspelled the driver or url name. Also, remember to register your ODBC driver data source. Check out:http://www.javaranch.com/ubb/Forum34/HTML/000279.html on how to do it. There's lots of free JDBC drivers that you can use. From what I've experienced, many only allow 2 connections when you are testing them. To get a list of companies that offer JDBC drivers try Java's: http://industry.java.sun.com/products/jdbc/drivers You may wish to try i-net's JDBC driver Type IV which supports SQL Server: http://www.inetsoftware.de/English/Produkte/JDBCTreiber/Default.htm hope that helps, Yoo-Jin.
Mirko Froehlich
Ranch Hand
Joined: Aug 21, 2000
Posts: 114
posted
0
I can highly recommend the i-net driver mentioned in the previous posting. I have had lots of problems with the JDBC-ODBC bridge in general, and using it to access SQL Server in particular - it isn't meant for production anyway. Never ran into any problems with the i-net driver. -Mirko
Originally posted by Yoo-Jin Lee: Hi, What kind of exceptions are you getting? If you cannot connect to SQL Server perhaps you misspelled the driver or url name. Also, remember to register your ODBC driver data source. Check out:http://www.javaranch.com/ubb/Forum34/HTML/000279.html on how to do it. There's lots of free JDBC drivers that you can use. From what I've experienced, many only allow 2 connections when you are testing them. To get a list of companies that offer JDBC drivers try Java's: http://industry.java.sun.com/products/jdbc/drivers You may wish to try i-net's JDBC driver Type IV which supports SQL Server: http://www.inetsoftware.de/English/Produkte/JDBCTreiber/Default.htm hope that helps, Yoo-Jin.