[
https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674630#action_12674630
]
Bryan Pendleton commented on DERBY-4064:
----------------------------------------
I think you need to pursue this with your JVM vendor, rather than with Derby.
JVM crashes
like this indicate a bug in the JVM rather than a bug in Derby.
I've also seen this sort of thing arise due to hardware errors, for example
you may have a memory board that's going bad, or a disk that's developing
bad sectors. A first step in this direction is to try to reproduce your problem
on a variety of different machines, and see if it's consistent across them.
Do you have a reproducible test case that you can provide which demonstrates
the crash?
> 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.
