spring-integration | personal hacking space for spring integration

The IntegrationFlows.from(somePublisher) start a ractive stream for the provided Publisher. The rest of the flow is done against every single event in the source Publisher. So, your .handle(flux ->) is going to work only if that event from the source is a Flux.

If your idea to apply that buffer() for the source Publisher and go on, then consider to use a reactive() customizer: https://docs.spring.io/spring-integration/docs/current/reference/html/reactive-streams.html#fluxmessagechannel-and-reactivestreamsconsumer.

So, instead of that handle() I would use:

The logic you write in that e.reactive() is not correct. See documentation for that endpoint configurer option to understand its purpose:

Acording to this answer: https://stackoverflow.com/a/51236918/16651073 tomcat falls back to default logging if it can resolve the location

Can you try to save the properties without the spaces.

Like this: logging.file.name=application.logs

The MessageProducerSpec is for Java DSL. It has nothing to do with low-level logic of the channel adapter. If you have a MessageProducerSupport, then this one is good enough for you to use in the flow definition:

It depends how blocking is a MessageHandler subscribed to that DirectChannel. Its purpose is to call a MessageHandler directly on a thread which has sent a message to this DirectChannel. So, if you do .map(e -> directChannel.send(e)), you need to be sure that MessageHandler is not blocking.

That is the default behavior; the second subscriber won't be called unless the ignoreFailures property is true (it is false by default).

You need to show the upstream flow, but to "catch" the exception you need to add an error channel to the (presumably) message-driven inbound adapter and handle the exception there.

The @MessagingGateway was designed for high-level end-user API, to hide messaging underneath as much as possible. So, the target service is free from any messaging abstraction when you develop its logic.

It is possible to use such an interface adapter from the IntegrationFlow and you should treat it as regular service activator therefore it would look like this:

This is a bug in the FileSupplierConfiguration - the call to start() is missing. The fix is already merged, but in the meantime, the workaround is like this:

Your problem is here: com.jcraft.jsch.ChannelSftp$2. Pay attention to that $2. This is already not a ChannelSftp, but an internal InputStream for the remote file. And that's exactly what SftpStreamingMessageSource is producing. It does not return files, neither ChannelSftp. You cannot call rename() on the InputStream.

Consider to use a special IntegrationMessageHeaderAccessor.CLOSEABLE_RESOURCE header instead. This one is an instance of the org.springframework.integration.file.remote.session.Session which already has a required rename(String pathFrom, String pathTo) method. But again: this one is going to do that for the remote file: