Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1923282067.10001265235032819.JavaMail.jira@brutus.apache.org>
Date: Wed, 3 Feb 2010 22:10:32 +0000 (UTC)
From: "Stan Lewis (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Updated: (CAMEL-2445) BatchProcesser.processExchange needs
 to catch Throwable
In-Reply-To: <1060178541.9901265234312554.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Stan Lewis updated CAMEL-2445:
------------------------------

    Attachment: patch-1.x.txt

> BatchProcesser.processExchange needs to catch Throwable
> -------------------------------------------------------
>
>                 Key: CAMEL-2445
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2445
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.6.2
>            Reporter: Stan Lewis
>            Assignee: Stan Lewis
>             Fix For: 1.6.3
>
>         Attachments: patch-1.x.txt
>
>
> Have to test this on 2.x still.
> If an aggregator sends an exchange to a processor that throws an Error this causes the thread started by BatchProcessor to exit, exchanges will then accumulate in the aggregator until an OutOfMemoryError occurs.
> This patch sorts that out and adds a unit test, however there's another problem that I'm still looking into, namely that BatchProcessor just uses an instance of LoggingErrorHandler as it's exception handler, so any exceptions/errors caught by this processor will just get logged and not follow the normal Camel error handling.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.