You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/04/05 21:21:05 UTC
[jira] [Created] (CAMEL-3838) FileStreamCache with Jetty and HTTP
may cause reply message to be empty instead of containing the cached stream
FileStreamCache with Jetty and HTTP may cause reply message to be empty instead of containing the cached stream
---------------------------------------------------------------------------------------------------------------
Key: CAMEL-3838
URL: https://issues.apache.org/jira/browse/CAMEL-3838
Project: Camel
Issue Type: Bug
Components: camel-core, camel-http, camel-jetty
Affects Versions: 2.7.0, 2.6.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.8.0
See nabble
http://camel.465427.n5.nabble.com/http-not-cleaning-up-tmp-files-when-exchange-is-stopped-td4269124.html
The issue was discovered during looking into that. The issue is not the STOP the end user talks about.
Its the file based stream cache which may return null for message body.
I am working on a patch as I got the unit test to verify the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-3838) FileStreamCache with Jetty and HTTP
may cause reply message to be empty instead of containing the cached stream
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-3838.
--------------------------------
Resolution: Not A Problem
> FileStreamCache with Jetty and HTTP may cause reply message to be empty instead of containing the cached stream
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3838
> URL: https://issues.apache.org/jira/browse/CAMEL-3838
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-http, camel-jetty
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/http-not-cleaning-up-tmp-files-when-exchange-is-stopped-td4269124.html
> The issue was discovered during looking into that. The issue is not the STOP the end user talks about.
> Its the file based stream cache which may return null for message body.
> I am working on a patch as I got the unit test to verify the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-3838) FileStreamCache with Jetty and HTTP
may cause reply message to be empty instead of containing the cached stream
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CAMEL-3838:
-------------------------------
Fix Version/s: 2.7.3
> FileStreamCache with Jetty and HTTP may cause reply message to be empty instead of containing the cached stream
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-3838
> URL: https://issues.apache.org/jira/browse/CAMEL-3838
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-http, camel-jetty
> Affects Versions: 2.6.0, 2.7.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.7.3, 2.8.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/http-not-cleaning-up-tmp-files-when-exchange-is-stopped-td4269124.html
> The issue was discovered during looking into that. The issue is not the STOP the end user talks about.
> Its the file based stream cache which may return null for message body.
> I am working on a patch as I got the unit test to verify the issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira