Hi It can be stream caching (if you use that) that overflow to disk, where it writes to a temp folder by default.
However that warning is harmless - it was enabled due to a upstream contribution from a code scan tool so the contributor added WARN logs and much more in some big PRs where this falled between our review. It has been restored to as it was before in a newer Camel version On Mon, Jan 10, 2022 at 12:29 PM Steve973 <steve...@gmail.com> wrote: > > Hello. I am using camel 3.12.0 in a project, and I am probably not logging > enough detail, but I see a message like this: > > org.apache.camel.util.FileUtil (101) - mkdirs() failed for > /tmp/camel/camel-temp-<bunch of hex alphanumerics followed by a dash and a > bunch of zeros> > > To give a bit more context, I am using the following: > > - camel-spring-boot-starter > - camel-jms-starter > - camel-bean-starter > - camel-servlet-startre > - camel-openapi-java-starter > - camel-jsonpath-starter > - camel-jackson-starter > - spring-boot-starter-artemis > - artemis-jms-server > > The last two are not camel artifacts, of course, but I include them because > I suspect that it has something to do with my configuration and/or use of > JMS in conjunction with the artemis server. In /tmp, I do not see a camel > subdirectory, so perhaps it is lacking permissions to write to /tmp. If > that is the case, can I set up a temp directory for camel file operations > that I give explicit permissions to? Or if any of you have some ideas > about how I might be able to get some more information, that would help, > too. Thanks in advance. > > Steve -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
