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

Stefan Buzoianu updated ARTEMIS-2780:
-------------------------------------
    Description: 
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
  
  
  
  

  was:
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

final String javaPath = Paths.get(System.getProperty("java.home"), "bin", 
"java").toAbsolutePath().toString();

But in my case, I actually start the application using Open Jre.

I found some similarities in these issues

https://issues.apache.org/jira/browse/ARTEMIS-2596

https://issues.apache.org/jira/browse/ARTEMIS-1058
  
  
  
 


> 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
>    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: Major
>         Attachments: 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)

Reply via email to