Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 66061 invoked from network); 23 Jun 2005 05:21:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jun 2005 05:21:31 -0000 Received: (qmail 31178 invoked by uid 500); 23 Jun 2005 05:21:21 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 30263 invoked by uid 500); 23 Jun 2005 05:21:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 29935 invoked by uid 99); 23 Jun 2005 05:21:12 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2005 22:21:11 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 88CAA19 for ; Thu, 23 Jun 2005 07:21:10 +0200 (CEST) Message-ID: <2071950353.1119504070558.JavaMail.jira@ajax.apache.org> Date: Thu, 23 Jun 2005 07:21:10 +0200 (CEST) From: "A B (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-388) Intermittent failures when executing UPDATE trigger statements Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Intermittent failures when executing UPDATE trigger statements -------------------------------------------------------------- Key: DERBY-388 URL: http://issues.apache.org/jira/browse/DERBY-388 Project: Derby Type: Bug Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0 Reporter: A B Assigned to: A B Fix For: 10.0.2.2 If I define an UPDATE trigger and then I repeatedly perform a table update that fires the trigger over many rows, I occasionally see intermittent failures of two kinds: 1) a null pointer exception, and/or 2) a syntax error. The NPE stack trace is this: The syntax error stack trace is this: In both cases, it looks like the error happens when Derby decides (internally) to recompile the trigger-action statement in the middle of trigger processing--depending on the state of the underlying Statement object that performs the trigger action, the result will be an NPE or a syntax error. I'm working on writing up a simplified reproduction and will post soon... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira