MuleSoft · DataWeave
No space left on device
Short answer
No space left on device in a DataWeave transformation means the temporary files DataWeave writes for large payloads filled the disk. Give the application more resources, or reduce how much it buffers at once.
VerifiedLast verified
01Error text
No space left on device02Likely causes
- Payloads over a configurable limit are written to temporary files on disk.
- Those files stay in use during long or concurrent runs, and the disk fills up.
03How to fix it
- Check how large the payloads are and how many transformations run at the same time.
- Give the application more resources, or reduce its consumption.
- If files are not released on the latest Mule release, report it to MuleSoft support.
04Official documentation
→Related errors
- MULE:STREAM_MAXIMUM_SIZE_EXCEEDEDMULE:STREAM_MAXIMUM_SIZE_EXCEEDED means a stream grew past the maximum size allowed for it, typically the in-memory buffer of a repeatable in-memory stream. Raise the buffer's maximum size, or use a streaming strategy that does not keep the content in memory.
- java.lang.OutOfMemoryError when listing filesA java.lang.OutOfMemoryError from the File Connector List operation with large files is caused by the default streaming strategy, Repeatable file store iterable. Change the operation's Streaming strategy to No repeatable iterable.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer