You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2025/06/27 07:38:21 UTC
(camel) branch main updated: CAMEL-22177: camel-ftp/camel-smb/camel-azure-files: Keep attempt to create starting dir if failed in doStart so we can recover.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 67fc12a12f7 CAMEL-22177: camel-ftp/camel-smb/camel-azure-files: Keep attempt to create starting dir if failed in doStart so we can recover.
67fc12a12f7 is described below
commit 67fc12a12f759b3916774b6a0caa813282592644
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Jun 27 09:38:05 2025 +0200
CAMEL-22177: camel-ftp/camel-smb/camel-azure-files: Keep attempt to create starting dir if failed in doStart so we can recover.
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
index 0b4051ab5bd..7d5f858a8cc 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_10.adoc
@@ -4,6 +4,15 @@ This document is for helping you upgrade your Apache Camel application
from Camel 4.x to 4.y. For example, if you are upgrading Camel 4.0 to 4.2, then you should follow the guides
from both 4.0 to 4.1 and 4.1 to 4.2.
+== Upgrading from 4.10.5 to 4.10.7
+
+=== camel-file / camel-ftp / camel-smb / camel-azure-files
+
+The consumers (`camel-ftp`, `camel-smb`, and `camel-azure-files`) will now in case of failure to create starting directory,
+on startup, keep attempting to create the directory on polling, until its successfully created.
+Previously in case of error creating the starting directory then this could cause the consumer to not be able to recover,
+and you would have to restart the route to attempt again.
+
== Upgrading from 4.10.4 to 4.10.5
=== camel-core