Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JDBC:ODBC Native Code errors,please help!

 
Ken Smith
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,im writing a system using tomcat. I connect to an ingres database using an ODBC bridge. Lately Tomcat has been crashing and generating the error report below.I think it says that the native odbc driver is crashing and causing tomcat to crash.It crashes outside the java VM so theres seems to be little i can do.Would anyone know how to fix this or even what causes it?Its been happening very frequently lately.Thanks for any help cause im lost!

An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x77F64860
Function=[Unknown.]
Library=(N/A)

NOTE: We are unable to locate the function name symbol for the error
just occurred. Please refer to release documentation for possible
reason and solutions.


Current Java thread:
at sun.jdbc.odbc.JdbcOdbc.freeStmt(Native Method)
at sun.jdbc.odbc.JdbcOdbc.SQLFreeStmt(JdbcOdbc.java:3385)
- locked <0x1002ee98> (a sun.jdbc.odbc.JdbcOdbc)
at sun.jdbc.odbc.JdbcOdbcStatement.close(JdbcOdbcStatement.java:496)
- locked <0x1004ba40> (a sun.jdbc.odbc.JdbcOdbcStatement)
at org.apache.jsp.ViewApplication_jsp._jspService(ViewApplication_jsp.java:156)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
/*section cut out,

*/

Dynamic libraries:

Heap at VM Abort:
Heap
def new generation total 576K, used 337K [0x10010000, 0x100b0000, 0x104f0000)
eden space 512K, 57% used [0x10010000, 0x10059328, 0x10090000)
from space 64K, 70% used [0x100a0000, 0x100ab498, 0x100b0000)
to space 64K, 0% used [0x10090000, 0x10090000, 0x100a0000)
tenured generation total 6432K, used 4118K [0x104f0000, 0x10b38000, 0x14010000)
the space 6432K, 64% used [0x104f0000, 0x108f5880, 0x108f5a00, 0x10b38000)
compacting perm gen total 8192K, used 8100K [0x14010000, 0x14810000, 0x18010000)
the space 8192K, 98% used [0x14010000, 0x147f90d0, 0x147f9200, 0x14810000)

Local Time = Wed Jul 07 10:06:37 2004
Elapsed Time = 64
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_02-b03 mixed mode)
#
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34084
337
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ken,
What database are you using?

Welcome to Javaranch!
 
Ken Smith
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I was using an ingres DB,i fixed the error though.
It was because my drivers were too old.I was using a version 3.5 ODBC manager and once i updated the drivers the random crashes stopped.
Thanks tho
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic