You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2009/07/15 21:00:34 UTC
[jira] Created: (CAMEL-1834) Message content sent to exception
handler is not re-readable
Message content sent to exception handler is not re-readable
------------------------------------------------------------
Key: CAMEL-1834
URL: https://issues.apache.org/activemq/browse/CAMEL-1834
Project: Apache Camel
Issue Type: Bug
Affects Versions: 1.6.1
Reporter: Gert Vanthienen
Assignee: Gert Vanthienen
Fix For: 1.6.2
When a route contains an exception handler clause, stream based message being sent to the error handler have been cached, but the message still isn't readable.
This only happens with a 1.6.2-SNAPSHOT, the trunk handles stream-based messages correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1834) Message content sent to exception
handler is not re-readable
Posted by "Gert Vanthienen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gert Vanthienen resolved CAMEL-1834.
------------------------------------
Resolution: Fixed
Fixed for 1.6.2-SNAPSHOT in http://svn.apache.org/viewvc?view=rev&revision=794375,
the extra unit test was added to trunk first in http://svn.apache.org/viewvc?view=rev&revision=794368
> Message content sent to exception handler is not re-readable
> ------------------------------------------------------------
>
> Key: CAMEL-1834
> URL: https://issues.apache.org/activemq/browse/CAMEL-1834
> Project: Apache Camel
> Issue Type: Bug
> Affects Versions: 1.6.1
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 1.6.2
>
>
> When a route contains an exception handler clause, stream based message being sent to the error handler have been cached, but the message still isn't readable.
> This only happens with a 1.6.2-SNAPSHOT, the trunk handles stream-based messages correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.