camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4126) S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
Date Sun, 26 Jun 2011 20:55:47 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055176#comment-13055176
] 

Christian Müller commented on CAMEL-4126:
-----------------------------------------

Committed r1139939
Thanks Brendan for the patch.
Working on the wiki page...

> S3Producer does not use CamelAwsS3ContentLength or CamelAwsS3ContentType
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-4126
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4126
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.8.0
>            Reporter: Brendan Long
>            Assignee: Christian Müller
>            Priority: Minor
>         Attachments: s3-content-length-and-type-patch.diff
>
>
> With InputStreams, Amazon's Java libraries aren't able to generate the content length
or content type, and we get warnings like this:
> WARN  AmazonS3Client - No content length specified for stream data.  Stream contents
will be buffered in memory and could result in out of memory errors.
> Not including the content type means S3 will be serving the uploaded file as generic
binary.
> Since there are already Camel headers for this, I'm proposing that they be used when
sending messages to S3. I can write a patch for this if it would help.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message