An unexpected error has been detected by HotSpot Virtual Machine:

Hi,

I am sorry if this has been reported before. I did a search and did not get any hit back.

When I run the following jsp code, I am getting the below error in Oracle Application Server log

#

# An unexpected error has been detected by HotSpot Virtual Machine:

#

# SIGSEGV (0xb) at pc=0xf78c1c0e, pid=22767, tid=2832190384

#

# Java VM: Java HotSpot(TM) Server VM (1.5.0_05-b05 mixed mode)

# Problematic frame:

# V [libjvm.so+0x276c0e]

#

# An error report file with more information is saved as hs_err_pid22767.log

#

# If you would like to submit a bug report, please visit:

#http://java.sun.com/webapps/bugreport/crash.jsp

#

Please note that I am using the following connection pool in data-sources.xml

<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource"

user="username"

password="password"

url="jdbc:oracle:oci:@....">

</connection-factory>

I would appreciate if you can shed any light on this.

Mustafa

try

{

InitialContext context =new InitialContext();

DataSource ds = (DataSource)context.lookup(datasource);

Connection conn = ds.getConnection();

DatabaseMetaData metadata = conn.getMetaData();

version ="The JDBC Driver loaded is " +

metadata.getDriverName() +

" version " +

metadata.getDriverVersion();

%>

<%=version%>

<%

Statement secure_stmt = conn.createStatement();

ResultSet rset = secure_stmt.executeQuery("select user from dual");

while (rset.next())

{

userName = rset.getString(1);

}

conn.close();

}

catch(Exception e)

{

e.printStackTrace();

%>

<%=e%>

<%

version ="<font color=\"red\">Error: could not connect to \"" + datasource +

"\".&nbsp;&nbsp;Make sure the required datasource is configured correctly</font>";

}

%>

[2473 byte] By [ACaycia] at [2007-10-3 5:58:46]
# 1
There have been a lot vm bug fixes since 1.5.0_05-b05. Try the latest VM
Caffeine0001a at 2007-7-15 0:40:19 > top of Java-index,Java HotSpot Virtual Machine,Specifications...
# 2

It is pretty much impossible to diagnose VM crashes like this. The interesting information is in the stacktrace, which (after processing) can show exactly where the crash happened.

The only general advice for things like this is to:

a) try on the latest update release and see if the problem persists;

b) if it does then try on a later version if you weren't already (eg try Java 6)

c) if the problem still persists file a bug report with Sun, with as much information as possible to help pin down the problem.

Often crashes are due to native code that is not part of the JVM, but which can stomp on memory used by the JVM

davidholmesa at 2007-7-15 0:40:19 > top of Java-index,Java HotSpot Virtual Machine,Specifications...