Re: Camel AWS SQS and concurrentConsumers

Hi Narsi, I've just created the Jira: CAMEL-17592 On Wed, Feb 2, 2022 at 11:35 PM Narsi Reddy Nallamilli < narsi.nallami...@gmail.com> wrote: > Hi Arnaud, > > Yup, It used to work before because I use it in my project and was not > aware of the

Bloker kafka sftp connector

Hello We are trying to read files using the following connector https://github.com/apache/camel-kafka-connector-examples/tree/main/sftp/sftp-source The connector send the whole file in one record to kafka which it is failing with big files It is possible to override the apply method to convert t

Re: Bloker kafka sftp connector

Hi Sergio, Can you tell a bit more about your use case? 1) How big are the files? Is there a specific threshold when doesn't it work anymore? 2) What kind of error do you get and where do you get it? (On Camel side or Kafka side, is it memory related)? 3) What kind of files are you using (csv, xm

Seda doesn't appear to be locking when queue is full

I've got a scenario where I need to iterate through all users within a system and send them to a remote as part of a routine "sync" to ensure that both systems are in agreement. User imports are also supported so there is some initial aggregation done on id in an attempt to minimize updates to the

Re: Seda doesn't appear to be locking when queue is full

I think you need to use blockWhenFull on the producer, so in your to() call. On Thu, Feb 3, 2022 at 10:33 AM Craig Taylor wrote: > I've got a scenario where I need to iterate through all users within a > system and send them to a remote as part of a routine "sync" to ensure that > both systems a

Re: Seda doesn't appear to be locking when queue is full

As mentioned I did try using blockWhenFull=true. It appears that the population of offerTimeout > 0 is required for blockWhenFull to be enabled. The documentation doesn't mention and it's unclear how all the various defaultBlockWhenFull, blockWhenFull etc are intended to be used. I'll look into