db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stan Bradbury (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4064) interaction between derby and jdk 1.5.0_17 causes core dump
Date Wed, 04 Mar 2009 18:42:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678835#action_12678835
] 

Stan Bradbury commented on DERBY-4064:
--------------------------------------

FWIW:

Similar problem has been reported to Redhat - not enough information on Redhat site to know
if Derby is involved but a workaround us use an earlier version of the JVM is presented:

https://bugzilla.redhat.com/show_bug.cgi?id=476695 :

When we run JBossAS 4.3.0-2.GA_CP01 with the Sun 1.5.0_17 JVM, 
we will see the
following crash within five minutes:

#
# An unexpected error has been detected by HotSpot Virtual 
Machine:
#
#  SIGSEGV (0xb) at pc=0x00002af0b777f6c4, pid=4198, 
tid=1091778880
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_17-b04 
mixed mode)
# Problematic frame:
# V  [libjvm.so+0x5bc6c4]
#
When we use the Sun 1.5.0_16 JVM, this doesn't happen.


> interaction between derby and jdk 1.5.0_17 causes core dump
> -----------------------------------------------------------
>
>                 Key: DERBY-4064
>                 URL: https://issues.apache.org/jira/browse/DERBY-4064
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.4.2.0
>         Environment: windows XP SP3, jdk 1.5.0_17, jboss 4.0.5-GA
> windows Server 2003 SP2, jdk 1.5.0_17, jboss 5.0.0-GA
> windows Server 2003 SP2, jdk 1.5.0_17, jboss 4.0.5-GA with derby 10.2.1.6
> linux 2.6.18-128.el5, jdk 1.5.0_17, jboss 5.0.0-GA 
>            Reporter: primasol
>            Priority: Blocker
>         Attachments: hs_err_pid156.log, hs_err_pid30771.log, hs_err_pid5340_withDerby10.2.1.6.log,
hs_err_pid600.log
>
>
> some unknown interaction causes derby to halt JVM with a core dump (see attached hs_err_*.log
files)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message