javax.ejb.EJBException: nested exception is: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: null; nested exception is:
Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2.0.1 (Build b04-fcs (04/11/2008))): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: sun.jdbc.odbc.JdbcOdbcDriver cannot be cast to javax.sql.DataSource
The JDBC/ODBC bridge driver is quite basic, and long predates the DataSource class. Anytime you find yourself wanting to use a DataSource, or are working in an enterprise application, that's a strong indication to use a better driver. (The bridge driver is also buggy and not thread-safe.) The jTDS driver handles MS SQLServer 2000 quite nicely.
But the same thing is working fine in the weblogic server. So, I can n't agree with the
point that the Driver is buggy.
Any way, could you explain the steps to configure
NetBeans with the iJTDS as You told .
What is the Driver Class name for ijTDS?
Joined: Mar 22, 2005
The bridge driver is positively buggy (and not thread-safe). It's possible that a different app server uses it in a different manner and thus doesn't expose its problems as quickly, but if you search around the net you'll find many problem reports.
Googling for "jtds" will get you to its home page, which has extensive documentation available.