It's not a secret anymore!*
The moose likes JDBC and the fly likes Wanted: Help using DBUnit with MS SQL Server: java.sql.SQLException: Invalid Fetch Size Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Wanted: Help using DBUnit with MS SQL Server: java.sql.SQLException: Invalid Fetch Size" Watch "Wanted: Help using DBUnit with MS SQL Server: java.sql.SQLException: Invalid Fetch Size" New topic
Author

Wanted: Help using DBUnit with MS SQL Server: java.sql.SQLException: Invalid Fetch Size

Siegfried Heintze
Ranch Hand

Joined: Aug 11, 2000
Posts: 381
Question #1: Can someone help me correct this invalid fetch size from DBUnit?

I'm using java 1.70, dbunit-2.4.8, MS sqlserver 2008 and I'm getting this stack trace:



I thought maybe the problem was that I had to use the Microsoft driver instead of the sun driver. The Sun driver seems to connect OK but produces the exception on line 28.

As you can see from my comments, I've tried both the sun and microsoft drivers.



I'd love to know how to use com.microsoft.sqlserver.jdbc.SQLServerDriver too.

Question #2: Can someone help me make this work with the Microsoft Driver? I cannot seem to get the connection string right and it keeps dying on the call to getConnection.


Exception in thread "main" com.microsoft.sqlserver.jdbc.SQLServerException: The connection to the host localhost, named instance sqlexpress has failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names, check that no firewall is blocking UDP traffic to port 1434, and for SQL Server 2005 or later verify that the SQL Server Browser Service is running on the host.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:171)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.getInstancePort(SQLServerConnection.java:3174)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.primaryPermissionCheck(SQLServerConnection.java:937)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:800)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:700)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:842)
at java.sql.DriverManager.getConnection(DriverManager.java:579)
at java.sql.DriverManager.getConnection(DriverManager.java:243)
at DatabaseExportSample.main(DatabaseExportSample.java:19)

Rob Spoor
Sheriff

Joined: Oct 27, 2005
Posts: 19655
    
  18

Are you sure the instance is called SQLEXPRESS? From http://technet.microsoft.com/en-us/library/ms143744(SQL.90).aspx:
SQL Server Express always installs a named instance (SQLExpress) unless you select a default instance. This behavior differs from SQL Server 2005, which installs a default instance unless a named instance is selected.

Try it without the "\\SQLEXPRESS" part to see if that works.


SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6
How To Ask Questions How To Answer Questions
Siegfried Heintze
Ranch Hand

Joined: Aug 11, 2000
Posts: 381
Thanks for the suggestion but

(1) the program at the bottom works (and contains SQLEXPRESS)
(2) I took the SQLEXPRESS out of the other two connection strings in the first program that uses DBUnit and neither connection string works.

Any more suggestions?

Thanks
Siegfried

 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Wanted: Help using DBUnit with MS SQL Server: java.sql.SQLException: Invalid Fetch Size
 
Similar Threads
SQLServerException - could not connect to the host on port 1433
exception while running my first jdbc code
Connecting To Database
Exception during connecting to sql server2005
Updated from JRE 1.5 to 1.6, now SQL JDBC Connection doesnt work