[
https://issues.apache.org/activemq/browse/CAMEL-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2899.
--------------------------------
Resolution: Fixed
The {{maxMessagesPerPoll}} option is now applied earlier for the file/ftp
components so we avoid creating so many Exchange objects which are then
afterwards discarded.
trunk: 960839.
Notice there is no limit in the java.io.File or FTP API to tell it to only list
at most X number of files.
> out of heap space if remote FTP site has too many files to pick up
> ------------------------------------------------------------------
>
> Key: CAMEL-2899
> URL: https://issues.apache.org/activemq/browse/CAMEL-2899
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-ftp
> Affects Versions: 2.3.0
> Reporter: Karl Palsson
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
>
> 2010-07-02 11:38:07,439 FATAL
> [org.apache.camel.component.file.remote.FtpConsumer:CamelThread 10] -
> <Consumer Consumer[my_ftp_URI_here caused by: Java heap space>
> java.lang.OutOfMemoryError: Java heap space
> My remote FTP server has ~60k 100 byte files, and the camel endpoint consumer
> falls over and doesn't start again. I can use JMX to stop/start the
> consumer, (it still has status "started") and it will log in to the remote
> server again, but then fall over with the out of heap space.
> I can work around this by increasing the heap, or by moving some of the files
> aside, but I don't think camel should care how many files there are, or at
> least, I think it should deal with it more gracefully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
