Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] /tmp files cleanup issue when running the MI in Windows #1217

Open
ruwanmadhusanka opened this issue Dec 20, 2024 · 0 comments
Open
Labels

Comments

@ruwanmadhusanka
Copy link

Description

When MI is doing a xslt transformation using the xslt mediator, if the input message size that is being transformed exceeds the synapse.temp_data.chunk.size, it will create a temporary file.

Once the transformation has been completed, if the transformed message size exceeds the synapse.temp_data.chunk.size, another temporary file will be created. At the moment, MI does not manually delete this temporary file as the reference for the content of this file can be used later, even after the xslt transformation. It is expected to be deleted at java.lang.Object.finalize() from the GC thread when there are no references to this temporary file.

We need to run a cron job to manually delete the files or else we have to add a cleanup task before starting the server. Then at every restart, the tmp folder will be cleaned up.

We need to add these details in xslt mediator docs.

Steps to Reproduce

Execute xslt transformation using the xslt mediator, which the input message size that is being transformed exceeds the synapse.temp_data.chunk.size.

Version

wso2mi/4.x.x

Environment Details (with versions)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant