db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3413) Derby crash in LockControl.isGrantable
Date Wed, 13 Feb 2008 16:39:08 GMT

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

Knut Anders Hatlen commented on DERBY-3413:
-------------------------------------------

I believe this is the following JVM bug: http://bugs.sun.com/view_bug.do?bug_id=6519085

If that's the case, upgrading to the latest update of Java SE 5.0 should help (was fixed in
update 14). Alternatively, you could try the workaround mentioned near the bottom of this
page: http://forum.java.sun.com/thread.jspa?threadID=5119596&messageID=9737995

> Derby crash in LockControl.isGrantable
> --------------------------------------
>
>                 Key: DERBY-3413
>                 URL: https://issues.apache.org/jira/browse/DERBY-3413
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.3.1.4
>         Environment: Sun Solaris Sparc
> JVM 1.5.0-11
>            Reporter: Ludovic Pourrat
>         Attachments: hs_err_pid23203.log
>
>
> The DERBY database server crashes sometimes on our production environment by producing
a hs_err_pid file.
> After recycling our application the same process come throught.
> On the client side all the DERBY connections are loss.

-- 
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