You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Gary Fix <ga...@win-na.com> on 2004/03/19 21:54:52 UTC

RE: comparison of Type 4 JDBC drivers

Thanks Yoav for the suggestion!

Can anyone point me to a comparison of Type 4 JDBC drivers supporting MS SQL Server and DB2 for the windows and IBM mainframe (Z_OS) linux platforms?

thanks...gary...

-----Original Message-----
From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
Sent: Thursday, March 18, 2004 6:02 AM
To: Tomcat Users List
Subject: RE: Tomcat 4.1.12LE Disappears



Hi,
Any and all suggestions will be welcome? ;)  OK.  Drop the JdbcOdbc
bridge so fast you do it even before the end of this sentence.  Use a
thin/type4 JDBC driver for your database.

What's happening is that your JdbcOdbc bridge driver is crashing with a
native-level (i.e. some DLL on Windoze) error.  That's crashing the JVM
internally, hence the hs_err_pid logs.  (HS stands for HotSpot).  

After tomcat crashes the ISAPI connector can't connect to it, hence the
jk errors in your log: these will go away if you fix your tomcat.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Gary Fix [mailto:gary.fix@win-na.com]
>Sent: Wednesday, March 17, 2004 4:40 PM
>To: Tomcat Users List
>Subject: Tomcat 4.1.12LE Disappears
>
>Hi,
>We are running Tomcat 4.1.12LE under Win2000 SP2 within a command
window.
>We use j2sdk1.4.1_02 for our servlet code.
>We also use the isapi_redirect.dll dated 11/8/2002.
>About the time we upgraded from version 3 of Tomcat to version 4, we
>strated having problems
>of Tomcat disappearing with no "apparent" error messages.
>In the last 8 days, it has disappeared 8 times.
>I have searched for a solution with no luck.
>The only error messages I could find are in the isapi_redirect.log and
some
>files named
>"hs_err_pid1208.log" showing up in the Tomcat \bin folder.
>
>The  isapi_redirect.log error messages look like this:
>[Mon Mar 15 16:19:39 2004]  [jk_isapi_plugin.c (724)]:
HttpExtensionProc
>error, service() failed
>[Mon Mar 15 16:19:40 2004]  [jk_connect.c (143)]: jk_open_socket,
connect()
>failed errno = 61
>[Mon Mar 15 16:19:40 2004]  [jk_ajp13_worker.c (196)]: In
>jk_endpoint_t::connect_to_tomcat, failed errno = 61
>[Mon Mar 15 16:19:40 2004]  [jk_ajp13_worker.c (635)]: Error connecting
to
>the Tomcat process.
>[Mon Mar 15 16:19:40 2004]  [jk_ajp13_worker.c (848)]: In
>jk_endpoint_t::service, send_request failed in send loop 1
>[Mon Mar 15 16:19:41 2004]  [jk_connect.c (143)]: jk_open_socket,
connect()
>failed errno = 61
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (196)]: In
>jk_endpoint_t::connect_to_tomcat, failed errno = 61
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (635)]: Error connecting
to
>the Tomcat process.
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (848)]: In
>jk_endpoint_t::service, send_request failed in send loop 0
>[Mon Mar 15 16:19:41 2004]  [jk_connect.c (143)]: jk_open_socket,
connect()
>failed errno = 61
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (196)]: In
>jk_endpoint_t::connect_to_tomcat, failed errno = 61
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (635)]: Error connecting
to
>the Tomcat process.
>[Mon Mar 15 16:19:41 2004]  [jk_ajp13_worker.c (848)]: In
>jk_endpoint_t::service, send_request failed in send loop 2
>[Mon Mar 15 16:19:41 2004]  [jk_isapi_plugin.c (724)]:
HttpExtensionProc
>error, service() failed
>
>Notice these seem to be loggin about once each second.
>We also some some console messages like this:
>361031 [Thread-8] WARN common.ChannelSocket  - server has closed the
>current con
>nection (-1)
>
>The hs_err_pid1208.log files have errors like this:
>An unexpected exception has been detected in native code outside the
VM.
>Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at
PC=0x77FCB8F4
>Function=RtlFreeHeap+0x263
>Library=C:\WINNT\System32\ntdll.dll
>
>Current Java thread:
>	at sun.jdbc.odbc.JdbcOdbc.freeConnect(Native Method)
>	at sun.jdbc.odbc.JdbcOdbc.SQLFreeConnect(JdbcOdbc.java:3287)
>	at
>sun.jdbc.odbc.JdbcOdbcDriver.closeConnection(JdbcOdbcDriver.java:952)
>	at
>sun.jdbc.odbc.JdbcOdbcConnection.close(JdbcOdbcConnection.java:740)
>	at
>sun.jdbc.odbc.JdbcOdbcConnection.finalize(JdbcOdbcConnection.java:87)
>	at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method)
>	at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83)
>	at java.lang.ref.Finalizer.access$100(Finalizer.java:14)
>	at
java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160)
>
>Dynamic libraries:
>followed by a bunch of DLLs.
>Any and all suggestions would be greatly appreciated.
>thanks...gary...
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged.  This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org