You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/09/19 15:10:21 UTC

[jira] [Commented] (AMQ-6436) tmp_storage folder not cleaned on startup

    [ https://issues.apache.org/jira/browse/AMQ-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503730#comment-15503730 ] 

Christopher L. Shannon commented on AMQ-6436:
---------------------------------------------

This happens because the temporary store is lazily initialized the first time it is needed which is only after there are enough non-persistent messages to fill up memory so that the messages need to be dumped to disk.  So on restart the old directory isn't touched until initialization.  However, it probably wouldn't hurt to clear out the temp store directory on first start up.

> tmp_storage folder not cleaned on startup
> -----------------------------------------
>
>                 Key: AMQ-6436
>                 URL: https://issues.apache.org/jira/browse/AMQ-6436
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.13.3
>         Environment: Windows/RHEL 6.8 tested
>            Reporter: Reid Sommerville
>         Attachments: JMSTmpStor.java, message.txt
>
>
> saw this on our production servers, activemq failed to start due to no space on the mount where tmp_storage was located. Reproduced it on a local windows machine.
> start a default activemq broker at the command line.
> Run the attached code enough times to cause activemq to start writing to the the tmp_storage folder, in my case 10000 messages was enough to give me 513Mb in tmp_storage
> restart activemq and note that the contents of the tmp_storage folder are still intact. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)