You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org> on 2008/04/08 16:09:24 UTC

[jira] Closed: (DERBY-3413) Derby crash in LockControl.isGrantable

     [ https://issues.apache.org/jira/browse/DERBY-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dyre Tjeldvoll closed DERBY-3413.
---------------------------------

    Resolution: Invalid

Closing this as 'Invalid' since it appears to be an instance of a JVM bug, and there has been no more comments.

> Derby crash in LockControl.isGrantable
> --------------------------------------
>
>                 Key: DERBY-3413
>                 URL: https://issues.apache.org/jira/browse/DERBY-3413
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    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.