[ 
https://issues.apache.org/jira/browse/ARTEMIS-2596?focusedWorklogId=446853&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-446853
 ]

ASF GitHub Bot logged work on ARTEMIS-2596:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Jun/20 19:31
            Start Date: 16/Jun/20 19:31
    Worklog Time Spent: 10m 
      Work Description: asfgit closed pull request #3187:
URL: https://github.com/apache/activemq-artemis/pull/3187


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 446853)
    Time Spent: 1h 40m  (was: 1.5h)

> (kill -9) AMQ causes tmp web dir space usage to increase
> --------------------------------------------------------
>
>                 Key: ARTEMIS-2596
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2596
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.10.1
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>            Priority: Major
>             Fix For: 2.14.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> If you kill the server without invoking a normal shutdown, tmp files are not 
> cleaned out.  This leaves old webapp folders lingering until a normal 
> shutdown.
> {code}
> ./tmp/jetty-0.0.0.0-8443-redhat-branding.war-_redhat-branding-any-3285121346946007361.dir
> ./tmp/jetty-0.0.0.0-8443-console.war-_console-any-4977922188149081743.dir/
> ./tmp/jetty-0.0.0.0-8443-artemis-plugin.war-_artemis-plugin-any-4959919418401315172.dir
> {code}
> In a failover test environment that repeatedly kills the server, this causes 
> disk space usage issues.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to