[jira] [Comment Edited] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown

["Domenico Francesco Bruscino (Jira)" <ji...@apache.org>]

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

Domenico Francesco Bruscino edited comment on ARTEMIS-2780 at 7/20/20, 3:34 PM:
--------------------------------------------------------------------------------

By default, Jetty will create this directory inside the directory named by the java.io.tmpdir system property, according to [jetty temporary directories documentation|https://www.eclipse.org/jetty/documentation/current/ref-temporary-directories.html]. 

Before the [ARTEMIS-2596 Move tmp web dir for a safe clean up|https://github.com/apache/activemq-artemis/commit/819f1834f5342bd4d425d4c2ff83f3b0bbaef373] commit all files included in the jetty default temporary web directory was deleted on start, so if your java.io.tmpdir system property is pointing to the lib path or a parent path of the lib path, it would explain your issue.
After the [ARTEMIS-2596 Move tmp web dir for a safe clean up|https://github.com/apache/activemq-artemis/commit/819f1834f5342bd4d425d4c2ff83f3b0bbaef373] commit the artemis web tmp folder is set, so now the cleanup only deletes files included in the artemis web tmp folder and not files at java.io.tmpdir.

The temporary web cleanup on stop deletes the files related to the loaded web contexts, wherever they are.
The temporary web cleanup on start is a workaround procedure that tries to delete temporary web files created by a previous execution terminated abnormally. This procedure deletes all files included in the web tmp folder, so also files not related to the web contexts. It can not delete temporary web files in other folders than the web tmp folder.


was (Author: brusdev):
By default, Jetty will create this directory inside the directory named by the java.io.tmpdir system property, according to [jetty temporary directories documentation|https://www.eclipse.org/jetty/documentation/current/ref-temporary-directories.html]. 

If your java.io.tmpdir system property is pointing to the lib path or a parent path of the lib path, it would explain your issue.
The [ARTEMIS-2596 Move tmp web dir for a safe clean up|https://github.com/apache/activemq-artemis/commit/819f1834f5342bd4d425d4c2ff83f3b0bbaef373] commit sets the artemis web tmp folder so now the cleanup should only delete files included in the artemis web tmp folder and not files at java.io.tmpdir.

The temporary web cleanup on stop deletes the files related to the loaded web contexts, wherever they are.
The temporary web cleanup on start is a workaround procedure that tries to delete temporary web files created by a previous execution terminated abnormally. This procedure deletes all files included in the web tmp folder, so also files not related to the web contexts. It can not delete temporary web files in other folders than the web tmp folder.

> Artemis Jar Files are automatically removed after abnormal system shutdown
> --------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2780
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2780
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: 2.11.0
>         Environment: Artemis is configured to always use a personally built OPEN JRE java (not using the default one)
>  * Artemis 2.11.0.
>  * Windows 10
>  * OpenJDK 1.8.0_66 (OPEN_JRE - C: \ work \ open-jre \)
>  * Oracle JDK 1.9.0_191 (Environment variable JAVA_HOME - C: \ Program Files \ Java \ jdk1.8.0_191
>  
>            Reporter: Stefan Buzoianu
>            Priority: Critical
>         Attachments: ARTEMIS-2780.png, artemis-service.xml, artemis.cmd
>
>
> If you kill the server without invoking a normal shutdown, the contents of the lib folder (ArtemisRootDir/lib) are removed. This makes Artemis Brokers unable to start.
> My suspicion is that there is a certain incompatibility between my local Windows resources and the way ActiveMQ Artemis is configured. Can you check the attached files please?
>  
> I found this
> [https://github.com/apache/activemq-artemis/blob/a68381904f658dfb3765710ae63f7c79e038b1ed/artemis-commons/src/main/java/org/apache/activemq/artemis/utils/SpawnedVMSupport.java#L192]
> Which apparently makes the java path to be set to java_home
> {code:java}
> final String javaPath = Paths.get(System.getProperty("java.home"), "bin", "java").toAbsolutePath().toString();{code}
> But in my case, I actually start the application using Open Jre. (Please check Environment details)
>  
>  
> I found some similarities in these issues
> https://issues.apache.org/jira/browse/ARTEMIS-2596
> https://issues.apache.org/jira/browse/ARTEMIS-1058
>   
>   
>   
>   



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