Was it slow? I tried this particualr driver on 2 RedHat boxes, and one Mandrake, and found it extremely slow (approx 12 seconds) to create the connections initially. Not so much of a problem when using pooling, but... lucky for me we ended up using Postgresql :)
Scott On Wed, 2003-02-26 at 11:14, White, Joshua A (CASD, IT) wrote: > I have gotten this driver to work with mssql 2k and DBCP. Check it out! > > Joshua > > -----Original Message----- > From: David Bolsover [mailto:[EMAIL PROTECTED] > Sent: Monday, February 24, 2003 6:18 AM > To: Struts Users Mailing List > Subject: RE: [Microsoft][ODBC SQL Server Driver]Communication link > failure > > > I would certainly suggest you check out alternative drivers; the > JdbcOdbcDriver is not recommended > for production use. > > Ideally, you should look for a type 4 driver that supports at least JDBC API > V 2.0 - try the M$ > driver it's free!!!!! > > <http://msdn.microsoft.com/downloads/default.asp?URL=/downloads/sample.asp?u > rl=/MSDN-FILES/027/001/7 > 79/msdncompositedoc.xml> > > db > > > -----Original Message----- > > From: Murray, Mark [mailto:[EMAIL PROTECTED] > > Sent: 24 February 2003 09:04 > > To: '[EMAIL PROTECTED]' > > Subject: [Microsoft][ODBC SQL Server Driver]Communication link failure > > > > > > Hi all, > > > > I'm having a problem reconnecting to a database after a number of hours of > > inactivity or of the database times out for any length of time. > > > > java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Communication > link > > failure > > > > My datasource definition reads as follows: > > > > <data-sources> > > <data-source > > autoCommit="false" > > description="database1" > > key="db1" > > minCount="2" > > maxCount="4" > > driverClass="sun.jdbc.odbc.JdbcOdbcDriver" > > url="jdbc:odbc:database1" > > user="auser" > > password="apassword" /> > > <data-source > > autoCommit="false" > > description="database2" > > key="db2" > > minCount="2" > > maxCount="4" > > driverClass="sun.jdbc.odbc.JdbcOdbcDriver" > > url="jdbc:odbc:database2" > > user="anotheruser" > > password="anotherpassword"/> > > </data-sources> > > > > I've tried adding autoReconnect to the datasource definition, either as a > > property or as part of the url, but this has no effect, other than to > cause > > errors when the config is being parsed. The Java application server we're > > using is SAP's J2EE engine (formerly known as In-Q-My) > > > > Is there another way to force a reconnect? A different driver set perhaps? > > > > any help would be appreciated > > > > Mark > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > This communication, including attachments, is for the exclusive use of > addressee and may contain proprietary, confidential or privileged > information. If you are not the intended recipient, any use, copying, > disclosure, dissemination or distribution is strictly prohibited. If > you are not the intended recipient, please notify the sender > immediately by return email and delete this communication and destroy all copies. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
