Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 35001 invoked from network); 10 Oct 2007 17:57:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Oct 2007 17:57:20 -0000 Received: (qmail 72407 invoked by uid 500); 10 Oct 2007 17:41:03 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 72392 invoked by uid 500); 10 Oct 2007 17:41:02 -0000 Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-dev@activemq.apache.org Delivered-To: mailing list camel-dev@activemq.apache.org Received: (qmail 72382 invoked by uid 99); 10 Oct 2007 17:41:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 10:41:02 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2007 17:41:14 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5ED137141F1 for ; Wed, 10 Oct 2007 10:40:24 -0700 (PDT) Message-ID: <21442937.1192038024385.JavaMail.jira@brutus> Date: Wed, 10 Oct 2007 10:40:24 -0700 (PDT) From: "Hiram Chirino (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-166) org.apache.camel.processor.UnitOfWorkWithAsyncFlowTest failure In-Reply-To: <33399383.1191907582922.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/CAMEL-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40334 ] Hiram Chirino commented on CAMEL-166: ------------------------------------- Ok I figured out why this was failing. Seem that when: (1) a route completes async (like in our UnitOfWorkWithAsyncFlowTest) (2) you invoked the route via the sync form of the Processor process() API. The test was assuming that all the registered Synchronizations on the UnitOfWork would complete before the process() call finished. Unfortunately, that's not the case. The Synchronizations are completed async and perhaps after the process call finishes. I patched up the test cases to account for this and now they should be working. > org.apache.camel.processor.UnitOfWorkWithAsyncFlowTest failure > -------------------------------------------------------------- > > Key: CAMEL-166 > URL: https://issues.apache.org/activemq/browse/CAMEL-166 > Project: Apache Camel > Issue Type: Bug > Components: camel-core > Affects Versions: 1.1.0 > Environment: SUSE Linux 10.1 > Reporter: Bozhong Lin > Priority: Blocker > Fix For: 1.2.0 > > > Running org.apache.camel.processor.UnitOfWorkWithAsyncFlowTest > Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.345 sec <<< FAILURE! > This prevents developer from building camel under Linux platform. Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.