[
https://issues.apache.org/jira/browse/DERBY-4064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693869#action_12693869
]
Myrna van Lunteren commented on DERBY-4064:
-------------------------------------------
I'd like to either close this as 'not a (derby) bug', or insist on at least
giving us the results when a different jvm is used. I'll close this in 2 days
if there is no response.
> 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.
