Websphere 5.1 Jtds jdbc driver issue

Question

Can some one suggest the possible solution to this issue.
I am trying to use Jtds 1.2 jdbc driver to connect to Sqlserver 2000 from the websphere 5.1 app server ( actually test server environment from WSAD 5.1.2) and I am getting the SQLException as follows "The requested size is greater than the maximum number of rows" . We have the same Jtds driver running fine on JBoss app server for the same application. So I am guessing it must be some configuration that I am missing in websphere that I could nt able to figure out. Appreciate if some one can direct me.
The run time error....
[7/3/06 11:34:47:297 CDT] 7c2fe6bb WebGroup I SRVE0181I: [Form Action Servlet] [ARJ] [Servlet.LOG]: java.sql.SQLException: java.sql.SQLException: The requested fetch size is greater than the maximum number of rows.
     at net.sourceforge.jtds.jdbc.JtdsStatement.setFetchSize(JtdsStatement.java:956)
     at net.sourceforge.jtds.jdbcx.proxy.StatementProxy.setFetchSize(StatementProxy.java:393)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.enforceStatementProperties(WSJdbcStatement.java:290)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeQuery(WSJdbcStatement.java:443)
     at com.actek.j2ee.common.sessionbean.QuerySessionBean.processQueryParm(QuerySessionBean.java:140)
and the concised SQL query, app error are as follows...
SELECT TOP 101 P.CreditTrnNo, P.CreditType, P.CustomerNo, P.Reviewed, P.NextReviewDate, P.DateComp .......... FROM CreditTrn P LEFT OUTER JOIN Customer Customer_CreditTrn ON P.CustomerNo = Customer_CreditTrn.CustomerNo LEFT OUTER JOIN Dealer Dealer_CreditTrn ON P.DealerNo = Dealer_CreditTrn.DealerNo LEFT OUTER JOIN UsrSet UsrSet_CreditTrn ON P.ChkUserNo = UsrSet_CreditTrn.UserNo WHERE Customer_CreditTrn.CustomerId = '013108' ORDER BY P.SalePend DESC, P.CompReq DESC, P.TrnType, P.FstDate, P.FstTime
java.sql.SQLException: The requested fetch size is greater than the maximum number of rows.
     at net.sourceforge.jtds.jdbc.JtdsStatement.setFetchSize(JtdsStatement.java:956)
     at net.sourceforge.jtds.jdbcx.proxy.StatementProxy.setFetchSize(StatementProxy.java:393)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.enforceStatementProperties(WSJdbcStatement.java:290)
     at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.executeQuery(WSJdbcStatement.java:443)

Answer 1

It passes the J2EE 1.3 certification ...So it is JDBC 2.0 compliant.
How does it rate with JDBC 3.0? Like mostly
complete? Or all complete but just not certified
(presuming such a certification exists.)It's both JDBC 2.0 and 3.0 compliant. The problem with the J2EE 1.4 compliance test suite is that it's not publicly available (1.3 is) so we simply can't test against it. We are trying to get jTDS certified, but it costs $2000 and we don't have that kind of money (not unless we pay from our pockets). We intend to do it, from donations and commercial support, but we're currently quite far from the $2k target. Even without an official certification jTDS is the driver of choice for a number of applications that need JDBC 3.0 features (e.g. Hibernate).
The only missing JDBC 3.0 features are connection pooling and row sets. The reason we did not implement these features is that there are good, free third party implementations out there, which are probably better implemented and tested than anything we could come up with (namely DBCP and c3p0 for connection pooling and the Sun reference implementation for row sets). Regarding connection pooling, jTDS does implement the PooledConnection interface, it just doesn't implement the pooling DataSource.
And it does windows auth as well as database auth
right (not a new feature but I want to make sure I
remember?)Yes, it does both SQL Server and Windows authentication. Windows authentication can be done using the credentials of the currently logged user (i.e. without the need to specify a user name and password) or by providing a Windows user name and password (this is useful when logging in from a non-Windows machine or a machine outside of the domain to an SQL Server that is only configured to accept Windows authentication). As far as I know the second Windows authentication mode is only supported by jTDS.
Alin.