[ 
https://issues.apache.org/jira/browse/ARTEMIS-5146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Bertram reassigned ARTEMIS-5146:
---------------------------------------

    Assignee: Justin Bertram

> wget command creates duplicate index.html on filesystem
> -------------------------------------------------------
>
>                 Key: ARTEMIS-5146
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5146
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.37.0
>         Environment: Docker image: 
> [https://hub.docker.com/r/apache/activemq-artemis]
>  
>            Reporter: Noah Bailey
>            Assignee: Justin Bertram
>            Priority: Minor
>
> Requests to the webconsole (localhost:8161) creates a buildup of numerous 
> "index.html" files to be created on disk, which appears to slow down and 
> sometimes stall the application.
> For some of my deployments, we had configured a healthcheck on the docker 
> container for artemis by requesting the root path on the console every 30 
> seconds to check if the container was alive or not. Here's an example:
> {noformat}
>   artemis:                  
>     image: apache/activemq-artemis:2.37.0
>     ...
>     healthcheck:
>       test: ["CMD", "wget", "-q", "http://localhost:8161/";]
>       interval: 30s
>       timeout: 10s
>       start_period: 60s
>       retries: 3
> {noformat}
> After a few months of this, it builds up a large number of files on disk. 
> Here's an example of a container that was running for about 2 months:
> {code:java}
> find . -name "index.html.*" | tail -n5
> ./index.html.174545
> ./index.html.174548
> ./index.html.174551
> ./index.html.174552
> ./index.html.174553 {code}
> There are indeed nearly 200K index.html files!
> {noformat}
> find . -name "index.html.*" | wc -l
> 174538{noformat}
> Listing the directory for the app can hang for several seconds, and on 
> low-spec boxes perhaps cause IO stalls. It also causes the requests to the 
> console to take longer and longer, eventually reaching the 10s timeout I 
> specified previously (though others may have different configurations). If 
> this happens, it can cause the container to start boot-looping too.
> As a workaround, we've replaced the healthcheck command with a TCP check on 
> the jms port:
> {noformat}
> (echo -e 'CONNECT\n\n' > /dev/tcp/127.0.0.1/61616 >/dev/null 2>&1) || exit 
> 1{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to