• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

An unexpected error of Java Runtime Environment:

 
faisal hameed
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I hava a two classes MainDataBase(parent) and SignUpDatabase.When i call methods of SignUpDatabase seperately,its working fine and when i call two methods same time it shows error.
My classes are :
Parent Class is


Child Class is


The exception is

Connection Created
Connection Closed
Connection Already Created
ok22
#
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c90100b, pid=1000, tid=3912
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# Problematic frame:
# C [ntdll.dll+0x100b]
#
# An error report file with more information is saved as hs_err_pid1000.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Java Result: 1
 
Peter Johnson
author
Bartender
Posts: 5852
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is a JVM crash. Usually I would recommend updating to a more recent JDK (a good idea anyway) and if the problem still occurs sending it to Sun (now Oracle, I guess). But given where it is aborting I suspect that your NIC driver might be bad. Try updating the driver to the latest level. If that does not solve the problem, try to code on another machine. If the problem happens there also, send the issue to Sun/Oracle.

Another possibility: what database are you using and what driver? Be very specific as to which driver. If could be the driver that is crashing.
 
faisal hameed
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using sql server 2000 and jdk version 1.6.If there is problem of jdbc driver then why single method works fine??
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34218
341
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Faisal,
Different code gets executed when you do different things. The face that it worked for something doesn't mean it isn't the driver.

I don't think this is your problem, but note that closing the statement/connection should be in different try/catch blocks. If closing the Statement fails, you still want to close the Connection.
 
faisal hameed
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I found its solution by putting con = null; just after con.close(); in method closeConnection();
But i dont know how works?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic