doTry() is confused by prior exceptions

Hi Camel community, I have observed following, if an exchange carries an exception, like in the onException() block, then: .log(...) .doTry() .removeProperty(...) behaves very differently from: // .log(...) .doTry() .removeProperty(...) If the exchange carries an exception, then with

FTPS consumer stops polling

Hi Camel community, I have a route with a from( FTPS component ). Recently it happened that the FTP server closed connection in middle of polling and on a next attempt PASV failed to open data connection. The route onException(Exception.class) logged two exchanges, two exceptions. It sets han

RE: FTPS consumer stops polling / listing

cases, please? I speculate that the route restart discarded some internal (likely corrupted) state. Hope it helps Cc. --   Mr. Petr Kužel, Software Engineer   Eurofins International Support Services s.à r.l.   Val Fleuri 23   L-1526 LUXEMBOURG -Original Message- From: Petr Kuze

Camel in Action: Microsoft Azure Files over public Internet

I have a new RFE which includes integrating Microsoft Azure Files over public Internet. Initial findings and constraints: - Azure Files do not implement the FTP standard. - Azure Files could expose SMB protocol but SMB over public Internet is blacklisted by the security policy. - Azure

RE: Camel in Action: Microsoft Azure Files over public Internet

િરાગ/चिराग/Chirag -- Sent from My Gmail Account On Mon, Apr 17, 2023 at 11:18 AM Petr Kuzel wrote: > > I have a new RFE which includes integrating > Microsoft Azure Files over public Internet. > > Initial findings and constraints: > > - Azure F

RE: Camel in Action: Microsoft Azure Files over public Internet

public Internet Hello, To me it makes sense to have a component supporting the SDK. Open an issue for that, if you have time you could contribute it, otherwise someone could take a look. Il giorno mar 18 apr 2023 alle ore 09:18 Petr Kuzel ha scritto: > Hi Chirag, > > well, it is not the f

users@camel.apache.org

Hi Camel community, I have a case where a route with a remote file-based endpoint polls a file message, processes it but in the GenericFileProcessStrategy.onComplete state an implementation of &move= throws an exception caused by missing delete/write permission. On next polling the same file is p

users@camel.apache.org

you recognise the sender and are certain that the content is safe. Hi Maybe plugin your custom process strategy on the file component and handle the exception there, you can extend the default process strategy. On Wed, Aug 16, 2023 at 3:58 PM Petr Kuzel wrote: > Hi Camel community,

users@camel.apache.org

bute RFE if I'm not the only one that thinks the case deserves some core-level enhancements. Best regards Cc. -- Mr. Petr Kužel, Software Engineer Eurofins International Support Services s.à r.l. Val Fleuri 23 L-1526 LUXEMBOURG -Original Message----- From: Petr Kuzel Sen

users@camel.apache.org

ption in completion while executing &move= Hi You can use a file filter where you check the file if you have permission to delete the file, that way you can control if you want Camel to consume the file or not. On Fri, Aug 18, 2023 at 5:56 PM Petr Kuzel wrote: > Experiments show th

FTPS moving away over-sized files remotely without downloading them

Hi riders, We have defined a max file size to be accepted and processed. Now, I wonder if it's possible to get the effect of &moveFailed= (a remote move) before a from()-exchange is created (which means a remote file body was already downloaded to the local working dir). I have tried at the leve

RE: FTPS moving away over-sized files remotely without downloading them

ownloading them Hi There is a download=false option On Tue, Dec 10, 2024 at 3:08 PM Petr Kuzel wrote: > Hi riders, > > We have defined a max file size to be accepted and processed. > > Now, I wonder if it's possible to get the effect of &moveFailed= (a > remote mo

RE: FTPS moving away over-sized files remotely without downloading them

those big files On Wed, Dec 11, 2024 at 10:21 AM Petr Kuzel wrote: > Thank you Claus, > > indeed, download=false I have overlooked. > > However thinking further it would require to configure two > routes/pollers with size filters: > (1) for normal files with default &