You are still using the JdbcOdbc bridge to connect to the database. So what others said about the stability of it, is still true, no matter which database you connect to.
The cheapest solutions (in terms of license fees) I know: http://www.freetds.org/download.html (Not feature complete) http://www.microsoft.com/sql/downloads/2000/jdbc.asp (Beta, just a few days old) Or have a look for commercial ones: http://industry.java.sun.com/products/jdbc/drivers > -----Urspr�ngliche Nachricht----- > Von: Vara Prashanth [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 2. Oktober 2001 01:11 > An: [EMAIL PROTECTED] > Betreff: RE: Tomcat 3.2.2 crashes with JDBC > > > Hello all: > > This is a follow up to the problem I was having with MS > access driver and > Java. > I just migrated my database from Access to MS SQL 2000 and > stress tested the > system. > I am still getting an error which causes tomcat to crash. > > I dont quite know how to analyse the error file language! so > I am attaching > a copy of the error file tomcat produces before quitting. Can > someone take a > look at it and please tell me if it is a problem with the > driver...or a > problem with my crappy code? > > Thanks a lot > Prashanth > > Here's the error file...... > > > An unexpected exception has been detected in native code > outside the VM. > Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at > PC=0x41166aba > Function name=SQLGetData > Library=C:\WINNT\System32\SQLSRV32.dll > > Current Java thread: > at sun.jdbc.odbc.JdbcOdbc.getDataInteger(Native Method) > at sun.jdbc.odbc.JdbcOdbc.SQLGetDataInteger(JdbcOdbc.java:3165) > at > sun.jdbc.odbc.JdbcOdbcResultSet.getDataInteger(JdbcOdbcResultS > et.java:5338) > at > sun.jdbc.odbc.JdbcOdbcResultSet.getInt(JdbcOdbcResultSet.java:555) > at > sun.jdbc.odbc.JdbcOdbcConnection.buildTypeInfo(JdbcOdbcConnect > ion.java:1474) > at > sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection > .java:379) > at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:163) > at java.sql.DriverManager.getConnection(DriverManager.java:517) > at java.sql.DriverManager.getConnection(DriverManager.java:199) > at > dlnetSearchInfc.dBMgmFiles.processdBCmds.initiateDatabase(proc > essdBCmds.java > :21) > at > dlnetSearchInfc.searchProcess.processSearchResults.performSing > leWildStringSe > arch(processSearchResults.java:119) > at > dlnetSearchInfc.searchProcess.processSearchResults.getResultDo > cs(processSear > chResults.java:41) > at > dlnetSearchInfc.searchProcess.processSearchString.getSearchPhr > aseResult(proc > essSearchString.java:576) > at > dlnetSearchInfc.searchProcess.processSearchString.searchCorpus > (processSearch > String.java:74) > at > dlnetSearchInfc.dlnetSearch.searchButtonClicked(dlnetSearch.java:35) > at dlnetSearchInfc.Search.doGet(Search.java:78) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper > .java:405) > at org.apache.tomcat.core.Handler.service(Handler.java:287) > at > org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) > at > org.apache.tomcat.core.ContextManager.internalService(ContextM > anager.java:79 > 7) > at > org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) > at > org.apache.tomcat.service.connector.Ajp12ConnectionHandler.pro > cessConnection > (Ajp12ConnectionHandler.java:166) > at > org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoin > t.java:416) > at > org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPo > ol.java:501) > at java.lang.Thread.run(Thread.java:484) > > Dynamic libraries: > 0x00400000 - 0x00405000 c:\jdk1.3.1\bin\java.exe > 0x77F80000 - 0x77FFB000 C:\WINNT\System32\ntdll.dll > 0x77DB0000 - 0x77E0B000 C:\WINNT\system32\ADVAPI32.dll > 0x77E80000 - 0x77F35000 C:\WINNT\system32\KERNEL32.dll > 0x77D40000 - 0x77DAC000 C:\WINNT\system32\RPCRT4.dll > 0x78000000 - 0x78046000 C:\WINNT\system32\MSVCRT.dll > 0x6D420000 - 0x6D4EF000 c:\jdk1.3.1\jre\bin\hotspot\jvm.dll > 0x77E10000 - 0x77E74000 C:\WINNT\system32\USER32.dll > 0x77F40000 - 0x77F7C000 C:\WINNT\system32\GDI32.DLL > 0x77570000 - 0x775A0000 C:\WINNT\System32\WINMM.dll > 0x6D220000 - 0x6D227000 c:\jdk1.3.1\jre\bin\hpi.dll > 0x6D3B0000 - 0x6D3BD000 c:\jdk1.3.1\jre\bin\verify.dll > 0x6D250000 - 0x6D266000 c:\jdk1.3.1\jre\bin\java.dll > 0x6D3C0000 - 0x6D3CD000 c:\jdk1.3.1\jre\bin\zip.dll > 0x6D340000 - 0x6D348000 C:\jdk1.3.1\jre\bin\net.dll > 0x75050000 - 0x75058000 C:\WINNT\System32\WSOCK32.dll > 0x75030000 - 0x75043000 C:\WINNT\System32\WS2_32.DLL > 0x75020000 - 0x75028000 C:\WINNT\System32\WS2HELP.DLL > 0x74FD0000 - 0x74FEF000 C:\WINNT\system32\msafd.dll > 0x75010000 - 0x75017000 C:\WINNT\System32\wshtcpip.dll > 0x785C0000 - 0x785CC000 C:\WINNT\System32\rnr20.dll > 0x77980000 - 0x779A4000 C:\WINNT\System32\DNSAPI.DLL > 0x77340000 - 0x77353000 C:\WINNT\System32\iphlpapi.dll > 0x77520000 - 0x77525000 C:\WINNT\System32\ICMP.DLL > 0x77320000 - 0x77337000 C:\WINNT\System32\MPRAPI.DLL > 0x75150000 - 0x75160000 C:\WINNT\System32\SAMLIB.DLL > 0x75170000 - 0x751BF000 C:\WINNT\System32\NETAPI32.DLL > 0x77BE0000 - 0x77BEF000 C:\WINNT\System32\SECUR32.DLL > 0x751C0000 - 0x751C6000 C:\WINNT\System32\NETRAP.DLL > 0x77950000 - 0x77979000 C:\WINNT\system32\WLDAP32.DLL > 0x77A50000 - 0x77B3A000 C:\WINNT\system32\OLE32.DLL > 0x779B0000 - 0x77A4B000 C:\WINNT\system32\OLEAUT32.DLL > 0x773B0000 - 0x773DE000 C:\WINNT\System32\ACTIVEDS.DLL > 0x77380000 - 0x773A2000 C:\WINNT\System32\ADSLDPC.DLL > 0x77830000 - 0x7783E000 C:\WINNT\System32\RTUTILS.DLL > 0x77880000 - 0x7790D000 C:\WINNT\System32\SETUPAPI.DLL > 0x77C10000 - 0x77C6D000 C:\WINNT\System32\USERENV.DLL > 0x774E0000 - 0x77512000 C:\WINNT\System32\RASAPI32.DLL > 0x774C0000 - 0x774D1000 C:\WINNT\System32\RASMAN.DLL > 0x77530000 - 0x77552000 C:\WINNT\System32\TAPI32.DLL > 0x77B50000 - 0x77BD9000 C:\WINNT\system32\COMCTL32.DLL > 0x77C70000 - 0x77CBA000 C:\WINNT\system32\SHLWAPI.DLL > 0x77360000 - 0x77379000 C:\WINNT\System32\DHCPCSVC.DLL > 0x775A0000 - 0x77625000 C:\WINNT\System32\CLBCATQ.DLL > 0x777E0000 - 0x777E8000 C:\WINNT\System32\winrnr.dll > 0x6D290000 - 0x6D29A000 C:\jdk1.3.1\jre\bin\JdbcOdbc.dll > 0x1F7F0000 - 0x1F825000 C:\WINNT\System32\ODBC32.dll > 0x76B30000 - 0x76B6E000 C:\WINNT\system32\comdlg32.dll > 0x782F0000 - 0x78532000 C:\WINNT\system32\SHELL32.DLL > 0x1F8E0000 - 0x1F8F6000 C:\WINNT\System32\odbcint.dll > 0x77820000 - 0x77827000 C:\WINNT\system32\VERSION.dll > 0x759B0000 - 0x759B6000 C:\WINNT\system32\LZ32.DLL > 0x1F840000 - 0x1F85A000 C:\WINNT\System32\odbccp32.dll > 0x782D0000 - 0x782EE000 C:\WINNT\system32\msv1_0.dll > 0x41160000 - 0x411D3000 C:\WINNT\System32\SQLSRV32.dll > 0x41090000 - 0x410BD000 C:\WINNT\System32\SQLUNIRL.DLL > 0x77800000 - 0x7781D000 C:\WINNT\System32\WINSPOOL.DRV > 0x769A0000 - 0x769A7000 C:\WINNT\System32\NDDEAPI.DLL > 0x0AA10000 - 0x0AA26000 C:\WINNT\System32\sqlsrv32.rll > 0x74CB0000 - 0x74CC7000 C:\WINNT\System32\DBNETLIB.DLL > 0x75500000 - 0x75504000 C:\WINNT\System32\security.dll > 0x77440000 - 0x774B5000 C:\WINNT\System32\crypt32.dll > 0x77430000 - 0x77440000 C:\WINNT\System32\MSASN1.DLL > 0x77BF0000 - 0x77C01000 C:\WINNT\System32\ntdsapi.dll > 0x74CD0000 - 0x74CD7000 C:\WINNT\System32\DBmsLPCn.dll > 0x77920000 - 0x77943000 C:\WINNT\system32\imagehlp.dll > 0x72A00000 - 0x72A2D000 C:\WINNT\system32\DBGHELP.dll > 0x690A0000 - 0x690AB000 C:\WINNT\System32\PSAPI.DLL > > -----Original Message----- > From: Randy Layman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 27, 2001 7:01 AM > To: [EMAIL PROTECTED] > Subject: RE: Tomcat 3.2.2 crashes with JDBC > > > > Its also considered "experimental" by Sun. (They > mention this in > one of the closed bug reports about it - basically they know > that the bridge > isn't thread safe and they don't want to fix it). > > Randy > > > > -----Original Message----- > > From: Artigas, Ricardo Y. [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, September 26, 2001 9:02 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Tomcat 3.2.2 crashes with JDBC > > > > > > Are you using the JDBC-ODBC bridge packaged with jdk? If so, > > it may be the > > cause of the problem. Try using another driver (type 3 or > > 4?). I've learned > > that the JDBC-ODBC bridge is not suggested for production use. HTH. > > > > :~) > > Ricky Y. Artigas > > Analyst/Programmer / > > Database Administrator > > Information Technology Division > > Easycall Communications Phils., Inc. > > > ------------------------------- > > > IMPORTANT NOTICE: > > > > > This message (and any attachment hereto) may contain > > privileged and/or > > > confidential information specific to EasyCall. If you are > > not the intended > > > addressee indicated in this message, you may not copy or > > disseminate this > > > message (or any attachment hereto) to anyone. Instead, > > please destroy this > > > message (and any attachment hereto), and kindly notify the > > sender by reply > > > email. Any information in this message (and any attachment > > thereto) that > > > do not relate to the official business of EasyCall shall be > > understood as > > > neither given nor endorsed by the company. > > > > > > > > > -----Original Message----- > > > From: Vara Prashanth [SMTP:[EMAIL PROTECTED]] > > > Sent: Thursday, September 27, 2001 7:22 AM > > > To: [EMAIL PROTECTED] > > > Subject: Tomcat 3.2.2 crashes with JDBC > > > > > > Hello all: > > > > > > I am facing a problem when I use JDBC to query a microsoft > > access database > > > on a win2K advanced server! I was testing the system for > > stability using > > > JMeter which essentially passes requests to a servlet. The > > servlet in turn > > > queries an access database and responds. When the number > of threads > > > increases I get an error while closing the DB connection > and Tomcat > > > crashes > > > producing a log file. I will be happy to send out the log file if > > > required. > > > Can you please help me solve the problem? Is this a > problem with the > > > access > > > driver or with access or with my servlet or tomcat(although very > > > unlikely!) > > > > > > Thanks in advance > > > > > > Prashanth > > > > > > > > > > > > _________________________________________________________ > > > > > > Do You Yahoo!? > > > > > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > > > > > > > > > _________________________________________________________ > > Do You Yahoo!? > > Get your free @yahoo.com address at http://mail.yahoo.com > > > > >
