[jira] Created: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

JIRA jira@apache.org
Enable stream caching on DeadLetterChannel by default
-----------------------------------------------------

                 Key: CAMEL-520
                 URL: https://issues.apache.org/activemq/browse/CAMEL-520
             Project: Apache Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 1.3.0
            Reporter: Gert Vanthienen
            Priority: Minor
             Fix For: 1.4.0


The dead letter channel will retry to send the same message multiple times, so the message content should be stream-cached before trying to process it the first time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

JIRA jira@apache.org

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

Willem Jiang reassigned CAMEL-520:
----------------------------------

    Assignee: Willem Jiang

> Enable stream caching on DeadLetterChannel by default
> -----------------------------------------------------
>
>                 Key: CAMEL-520
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-520
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The dead letter channel will retry to send the same message multiple times, so the message content should be stream-cached before trying to process it the first time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Willem Jiang resolved CAMEL-520.
--------------------------------

    Resolution: Fixed

> Enable stream caching on DeadLetterChannel by default
> -----------------------------------------------------
>
>                 Key: CAMEL-520
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-520
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The dead letter channel will retry to send the same message multiple times, so the message content should be stream-cached before trying to process it the first time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Reopened: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Gert Vanthienen reopened CAMEL-520:
-----------------------------------


The current fix handles an InputStream being sent as the message body correctly, but I think we should also handle other kinds of streaming data (StaxSource, Reader, ...).  How about using the same as the interceptor logic from the StreamCachingInterceptor?  We still have to find a way to reset the stream between redelivery attempts (adding a reset() method to the StreamCache interface perhaps?)

> Enable stream caching on DeadLetterChannel by default
> -----------------------------------------------------
>
>                 Key: CAMEL-520
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-520
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The dead letter channel will retry to send the same message multiple times, so the message content should be stream-cached before trying to process it the first time.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-520) Enable stream caching on DeadLetterChannel by default

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Willem Jiang resolved CAMEL-520.
--------------------------------

    Resolution: Fixed

Added the unit test to show how the Source, Read, InputStream can be cached with StreamCache.

> Enable stream caching on DeadLetterChannel by default
> -----------------------------------------------------
>
>                 Key: CAMEL-520
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-520
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0
>            Reporter: Gert Vanthienen
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The dead letter channel will retry to send the same message multiple times, so the message content should be stream-cached before trying to process it the first time.

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