[
https://issues.apache.org/jira/browse/ARTEMIS-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271623#comment-17271623
]
ASF subversion and git services commented on ARTEMIS-2026:
----------------------------------------------------------
Commit 9c9d4de2311a145405da755d7ab27cc33dedf64f in activemq-artemis's branch
refs/heads/master from Dirk Van Haerenborgh
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9c9d4de ]
ARTEMIS-2026 don't override 'java.io.tmpdir' if set
> Allow location of $ARTEMIS_INSTANCE/tmp location to be overridden
> -----------------------------------------------------------------
>
> Key: ARTEMIS-2026
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2026
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Keith Wall
> Priority: Major
>
> Currently Artemis creates the {{tmp}} directory as a child of
> {{$ARTEMIS_INSTANCE}}. There is no mechanism to override the location so the
> temporary files are written elsewhere in the filesystem.
> Whilst Artemis does take steps to delete the temporary files it has created
> as it shuts-down, this relies on the JVM's shutdown hooks firing correctly.
> If the JVM or container crashes or aborts, temporary files accumulate.
> Operator intervention would then be required to manually delete the files,
> which is problematic for use-cases where Artemis is deployed as part of
> service (as for http://enmasse.io).
> It would be desirable to be able to separate the temporary files from the
> other files that represent the Broker's state at a filesystem level. This
> would allow the user of Artemis to direct the temporary directory at an
> operating system defined temporary location that will be cleared no matter
> what.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
