Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <28067551.1202923268999.JavaMail.jira@brutus>
Date: Wed, 13 Feb 2008 09:21:08 -0800 (PST)
From: "Ludovic Pourrat (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3413) Derby crash in
 LockControl.isGrantable
In-Reply-To: <1672154.1202919068969.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ludovic Pourrat commented on DERBY-3413:
----------------------------------------

Both solutions will be tested on our pre produciton systems looking forward to bring them on production.
I will give some comment and update on that issue within few days.
   

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