From dev-return-4803-apmail-ode-dev-archive=ode.apache.org@ode.apache.org Thu Dec 25 00:59:13 2008 Return-Path: Delivered-To: apmail-ode-dev-archive@www.apache.org Received: (qmail 38394 invoked from network); 25 Dec 2008 00:59:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Dec 2008 00:59:13 -0000 Received: (qmail 41486 invoked by uid 500); 25 Dec 2008 00:59:13 -0000 Delivered-To: apmail-ode-dev-archive@ode.apache.org Received: (qmail 41464 invoked by uid 500); 25 Dec 2008 00:59:13 -0000 Mailing-List: contact dev-help@ode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ode.apache.org Delivered-To: mailing list dev@ode.apache.org Received: (qmail 41453 invoked by uid 99); 25 Dec 2008 00:59:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Dec 2008 16:59:13 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Dec 2008 00:59:05 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 56D57234C46A for ; Wed, 24 Dec 2008 16:58:44 -0800 (PST) Message-ID: <240229563.1230166724354.JavaMail.jira@brutus> Date: Wed, 24 Dec 2008 16:58:44 -0800 (PST) From: "Karthick Sankarachary (JIRA)" To: dev@ode.apache.org Subject: [jira] Updated: (ODE-262) Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception In-Reply-To: <1924708540.1207588285274.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/ODE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthick Sankarachary updated ODE-262: -------------------------------------- Attachment: unique-correlation-set-for-trunk.patch > Duplicated correlation set values is accepted and creates a second instance instead of throwing an exception > ------------------------------------------------------------------------------------------------------------ > > Key: ODE-262 > URL: https://issues.apache.org/jira/browse/ODE-262 > Project: ODE > Issue Type: Bug > Components: BPEL Runtime > Affects Versions: 1.1.1 > Environment: Apache ODE 1.1.1 or 1.2 > Tomcat > The counter example of infoq. > Reporter: Amin Anjomshoaa > Assignee: Karthick Sankarachary > Fix For: 2.0 > > Attachments: unique-correlation-set-for-branch.patch, unique-correlation-set-for-trunk.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > The classical counter example of infoq (http://www.infoq.com/articles/paul-brown-ode) can be used. Sending the "init" message for the second (third, fourth, ... ) time with the value "foo" will create a new instance. I was expecting a CorrelationViolation exception when the second init message is arriving. > All upcoming messages are then correlated with the last instance only. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.