#393 Hotspot with V2.2 JDK 1.5.0_06

2.2rc1
closed-invalid
None
5
2006-09-30
2006-06-30
Anonymous
No

I get a HotSpot error every time with Squirell 2.1 and
2.2 using JDK 1.5.0_06. The initial start is fine but
wehn I configure an Alias and close Squirrel, the next
time I start squirrel I get a HotSpot (see error below).
I am using Aquirell SQL v2.2 Or 2.1 JDK 1.5.0_06 on
SuSe Linux 10.

HotSpot Error:
# An unexpected error has been detected by HotSpot
Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x55a8fcd1, pid=3489, tid=1871203248
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05
mixed mode)
# Problematic frame:
# V [libjvm.so+0x3c9cd1]
#
# An error report file with more information is saved
as hs_err_pid3489.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
/opt/SquirrelSQLClient22/squirrel-sql.sh: line 45:
3489 Aborted $JAVA -Xmx256m -cp $TMP_CP
net.sourceforge.squirrel_sql.client.Main
--log-config-file $SQUIRREL_SQL_HOME/log4j.properties
--squirrel-home $SQUIRREL_SQL_HOME $1 $2 $3 $4 $5 $6 $7
$8 $9

Discussion

  • Tim

    Tim - 2006-08-25

    Logged In: YES
    user_id=1297500

    I get the same problem. See this discussion:
    http://forum.java.sun.com/thread.jspa?threadID=691320&tstart=1

    It would appear there are 2 solutions:

    1) Use Java 1.5.0_05

    2) Add a command line flag to turn off hotspot compilation
    of a certain method:

    By looking in the log file hs_err_pid3489.log you can see
    the offending method name.

    You can fix the problem (at least, it appears to fix it for
    me) by adding this to Squirrel's startup by editing the
    startup script:

    -XX:CompileCommand=exclude,net/n3/nanoxml/StdXMLParser,processElement

    You can add it just before the
    net.sourceforge.squirrel_sql.client.Main part.

    If the class/method in the log file is different, you'll
    have to substitute the appropriate value.

     
  • Rob Manning

    Rob Manning - 2006-09-30
    • assigned_to: nobody --> manningr
    • status: open --> closed-invalid
     
  • Rob Manning

    Rob Manning - 2006-09-30

    Logged In: YES
    user_id=1287991

    This would be a JVM bug. I suggest you file a bug with Sun
    unless there already is one. You might also want to try
    timmorrow's advice while waiting for a fix from Sun.

    Rob

     

Log in to post a comment.