[jira] [Comment Edited] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown
[
https://issues.apache.org/jira/browse/ARTEMIS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161287#comment-17161287
]
Stefan Buzoianu edited comment on ARTEMIS-2780 at 7/20/20, 4:46 PM:
I apologize for the delay but I wanted to do tests not only on 2.12 but also on
2.14. I made a build compiled with OpenJDK on the Windows environment.
For a few weeks I had the impression that this issue was resolved once this bug
was resolved - https://issues.apache.org/jira/browse/ARTEMIS-2596. I suspected
that our problem of deleting libraries was related to the cleanup procedure.
After at least four weeks in which this bug - deleting the jars from the lib
folder - did not reproduce in 2.1, it appeared when a VM we were testing
shutdown due to a windows update.
{code:java}
2020-07-15 01:49:04,123 ERROR [org.apache.activemq.artemis.core.server]
AMQ224068: Unable to stop component:
org.apache.activemq.artemis.component.WebServerComponent: java.io.IOException:
Cannot run program "C:\Client\Common\open-jre\bin\java": CreateProcess
error=19, The media is write protected2020-07-15 01:49:04,123 ERROR
[org.apache.activemq.artemis.core.server] AMQ224068: Unable to stop component:
org.apache.activemq.artemis.component.WebServerComponent: java.io.IOException:
Cannot run program "C:\Client\Common\open-jre\bin\java": CreateProcess
error=19, The media is write protected at
java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) [rt.jar:1.8.0_232] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:244)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:130)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:102)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:70)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:51)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebTmpCleaner.cleanupTmpFiles(WebTmpCleaner.java:77)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebTmpCleaner.cleanupTmpFiles(WebTmpCleaner.java:66)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.cleanupWebTemporaryFiles(WebServerComponent.java:318)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.internalStop(WebServerComponent.java:269)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.stop(WebServerComponent.java:358)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1265)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1033)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:876)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.integration.FileBroker.stop(FileBroker.java:98)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.cli.commands.Run.stop(Run.java:166)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.cli.commands.Run$2.run(Run.java:157)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT]Caused by:
java.io.IOException: CreateProcess error=19, The media is write protected at
java.lang.ProcessImpl.create(Native Method) [rt.jar:1.8.0_232] at
java.lang.ProcessImpl.(ProcessImpl.java:444) [rt.jar:1.8.0_232] at
java.lang.ProcessImpl.start(ProcessImpl.java:139) [rt.jar:1.8.0_232] at
java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) [rt.jar:1.8.0_232] ...
16 more
{code}
If on 2.12 this issue when it appears leads to the deletion of all jars in
libs, in this case, on 2.14, the jars in the lib folder have been partially
deleted.
We added some logs on our version of 2.14 and noticed that the jars that were
previously loaded in CLASSPATH are deleted:
[https://github.com/apache/activemq-artemis/blob/8fe1bb1c833e65a706423d332aa2abd5ae38d87b/artemis-commons/src/main/java/org/apache/activemq/artemis/utils/SpawnedVMSupport.java#L204]
My observation is that the jars are partially deleted because the child process
that is created to do web tmp folder cleanup cannot successfully initialize due
to the fact that the JVM is shutting down.
In this case I have two
[jira] [Work logged] (ARTEMIS-2843) LVQ + non-destructive not delivering message to existing consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-2843?focusedWorklogId=461146=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-461146 ] ASF GitHub Bot logged work on ARTEMIS-2843: --- Author: ASF GitHub Bot Created on: 20/Jul/20 16:08 Start Date: 20/Jul/20 16:08 Worklog Time Spent: 10m Work Description: asfgit closed pull request #3216: URL: https://github.com/apache/activemq-artemis/pull/3216 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: 461146) Time Spent: 20m (was: 10m) > LVQ + non-destructive not delivering message to existing consumer > - > > Key: ARTEMIS-2843 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2843 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > When a client acknowledges a message on a non-destructive LVQ and that > message is subsequently replaced by another "last value" the broker does not > deliver this message to the client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2843) LVQ + non-destructive not delivering message to existing consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161351#comment-17161351 ] ASF subversion and git services commented on ARTEMIS-2843: -- Commit ccc0fa7100575fb5b0a73229f0762829bcab2b5a in activemq-artemis's branch refs/heads/master from Clebert Suconic [ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=ccc0fa7 ] ARTEMIS-2843 non-destructive LVQ not delivering msg to consumer > LVQ + non-destructive not delivering message to existing consumer > - > > Key: ARTEMIS-2843 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2843 > Project: ActiveMQ Artemis > Issue Type: Bug >Reporter: Justin Bertram >Assignee: Justin Bertram >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When a client acknowledges a message on a non-destructive LVQ and that > message is subsequently replaced by another "last value" the broker does not > deliver this message to the client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (ARTEMIS-2849) Eliminate zeroing of buffers while writing the ASYNCIO journal
[
https://issues.apache.org/jira/browse/ARTEMIS-2849?focusedWorklogId=461140=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-461140
]
ASF GitHub Bot logged work on ARTEMIS-2849:
---
Author: ASF GitHub Bot
Created on: 20/Jul/20 15:53
Start Date: 20/Jul/20 15:53
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on a change in pull request
#3223:
URL: https://github.com/apache/activemq-artemis/pull/3223#discussion_r457515880
##
File path:
artemis-journal/src/main/java/org/apache/activemq/artemis/core/io/AbstractSequentialFile.java
##
@@ -271,7 +271,7 @@ protected ByteBuffer newBuffer(int size, int limit) {
public void flushBuffer(final ByteBuf byteBuf, final boolean
requestedSync, final List callbacks) {
final int bytes = byteBuf.readableBytes();
if (bytes > 0) {
-final ByteBuffer buffer = newBuffer(byteBuf.capacity(), bytes);
+final ByteBuffer buffer = newBuffer(byteBuf.capacity(), bytes,
false);
Review comment:
@franz1981 the failure is real... this PR is broken.
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: 461140)
Time Spent: 1h 50m (was: 1h 40m)
> Eliminate zeroing of buffers while writing the ASYNCIO journal
> --
>
> Key: ARTEMIS-2849
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2849
> Project: ActiveMQ Artemis
> Issue Type: Test
> Components: Broker
>Reporter: Francesco Nigro
>Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> By default ASYNCIO using TimedBuffer are zeroing the ByteBuffers used to
> perform the write on the journal: under load TimedBuffer can be big enough
> that zeroing would cost the same as copying the actual content into it, hence
> saving the zeroing is quite beneficial to save CPU time and increase IOPS.
> NIO and MAPPED doesn't need it because they already use directly the
> TimedBuffer's accumulation buffer to perform writes (that's never zeroed,
> because it already contains the content that they expect to write into the
> journal), but changing ASYNCIO need to adjust the same calls on NIO and
> MAPPED for completeness.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown
[
https://issues.apache.org/jira/browse/ARTEMIS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown
[
https://issues.apache.org/jira/browse/ARTEMIS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161326#comment-17161326
]
Domenico Francesco Bruscino commented on ARTEMIS-2780:
--
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)
[jira] [Work logged] (ARTEMIS-2849) Eliminate zeroing of buffers while writing the ASYNCIO journal
[
https://issues.apache.org/jira/browse/ARTEMIS-2849?focusedWorklogId=461114=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-461114
]
ASF GitHub Bot logged work on ARTEMIS-2849:
---
Author: ASF GitHub Bot
Created on: 20/Jul/20 14:45
Start Date: 20/Jul/20 14:45
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on a change in pull request
#3223:
URL: https://github.com/apache/activemq-artemis/pull/3223#discussion_r457453521
##
File path:
artemis-journal/src/main/java/org/apache/activemq/artemis/core/io/AbstractSequentialFile.java
##
@@ -271,7 +271,7 @@ protected ByteBuffer newBuffer(int size, int limit) {
public void flushBuffer(final ByteBuf byteBuf, final boolean
requestedSync, final List callbacks) {
final int bytes = byteBuf.readableBytes();
if (bytes > 0) {
-final ByteBuffer buffer = newBuffer(byteBuf.capacity(), bytes);
+final ByteBuffer buffer = newBuffer(byteBuf.capacity(), bytes,
false);
Review comment:
I actually had access to the same build as you, and as I can see the
build did not complete.. lots of failures due to open files. I will restart
that build
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: 461114)
Time Spent: 1h 40m (was: 1.5h)
> Eliminate zeroing of buffers while writing the ASYNCIO journal
> --
>
> Key: ARTEMIS-2849
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2849
> Project: ActiveMQ Artemis
> Issue Type: Test
> Components: Broker
>Reporter: Francesco Nigro
>Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> By default ASYNCIO using TimedBuffer are zeroing the ByteBuffers used to
> perform the write on the journal: under load TimedBuffer can be big enough
> that zeroing would cost the same as copying the actual content into it, hence
> saving the zeroing is quite beneficial to save CPU time and increase IOPS.
> NIO and MAPPED doesn't need it because they already use directly the
> TimedBuffer's accumulation buffer to perform writes (that's never zeroed,
> because it already contains the content that they expect to write into the
> journal), but changing ASYNCIO need to adjust the same calls on NIO and
> MAPPED for completeness.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown
[
https://issues.apache.org/jira/browse/ARTEMIS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161287#comment-17161287
]
Stefan Buzoianu commented on ARTEMIS-2780:
--
I apologize for the delay but I wanted to do tests not only on 2.12 but also on
2.14. I made a build compiled with OpenJDK on the Windows environment.
For a few weeks I had the impression that this issue was resolved once this bug
was resolved - https://issues.apache.org/jira/browse/ARTEMIS-2596. I suspected
that our problem of deleting libraries was related to the cleanup procedure.
After at least four weeks in which this bug - deleting the jars from the lib
folder - did not reproduce in 2.1, it appeared when a VM we were testing
shutdown due to a windows update.
{code:java}
2020-07-15 01:49:04,123 ERROR [org.apache.activemq.artemis.core.server]
AMQ224068: Unable to stop component:
org.apache.activemq.artemis.component.WebServerComponent: java.io.IOException:
Cannot run program "C:\NAPA\Common\open-jre\bin\java": CreateProcess error=19,
The media is write protected2020-07-15 01:49:04,123 ERROR
[org.apache.activemq.artemis.core.server] AMQ224068: Unable to stop component:
org.apache.activemq.artemis.component.WebServerComponent: java.io.IOException:
Cannot run program "C:\NAPA\Common\open-jre\bin\java": CreateProcess error=19,
The media is write protected at
java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) [rt.jar:1.8.0_232] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:244)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:130)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:102)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:70)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.utils.SpawnedVMSupport.spawnVM(SpawnedVMSupport.java:51)
[artemis-commons-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebTmpCleaner.cleanupTmpFiles(WebTmpCleaner.java:77)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebTmpCleaner.cleanupTmpFiles(WebTmpCleaner.java:66)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.cleanupWebTemporaryFiles(WebServerComponent.java:318)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.internalStop(WebServerComponent.java:269)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.component.WebServerComponent.stop(WebServerComponent.java:358)
[artemis-web-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1265)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:1033)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.stop(ActiveMQServerImpl.java:876)
[artemis-server-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.integration.FileBroker.stop(FileBroker.java:98)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.cli.commands.Run.stop(Run.java:166)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT] at
org.apache.activemq.artemis.cli.commands.Run$2.run(Run.java:157)
[artemis-cli-2.14.0-SNAPSHOT.jar:2.14.0-SNAPSHOT]Caused by:
java.io.IOException: CreateProcess error=19, The media is write protected at
java.lang.ProcessImpl.create(Native Method) [rt.jar:1.8.0_232] at
java.lang.ProcessImpl.(ProcessImpl.java:444) [rt.jar:1.8.0_232] at
java.lang.ProcessImpl.start(ProcessImpl.java:139) [rt.jar:1.8.0_232] at
java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) [rt.jar:1.8.0_232] ...
16 more
{code}
If on 2.12 this issue when it appears leads to the deletion of all jars in
libs, in this case, on 2.14, the jars in the lib folder have been partially
deleted.
We added some logs on our version of 2.14 and noticed that the jars that were
previously loaded in CLASSPATH are deleted:
[https://github.com/apache/activemq-artemis/blob/8fe1bb1c833e65a706423d332aa2abd5ae38d87b/artemis-commons/src/main/java/org/apache/activemq/artemis/utils/SpawnedVMSupport.java#L204]
My observation is that the jars are partially deleted because the child process
that is created to do web tmp folder cleanup cannot successfully initialize due
to the fact that the JVM is shutting down.
In this case I have two questions:
1. What are the implications for keeping the
[jira] [Updated] (ARTEMIS-2780) Artemis Jar Files are automatically removed after abnormal system shutdown
[
https://issues.apache.org/jira/browse/ARTEMIS-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Buzoianu updated ARTEMIS-2780:
-
Component/s: Web Console
> 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)
[jira] [Reopened] (ARTEMIS-2813) Kerberos tests failures on Java 11
[ https://issues.apache.org/jira/browse/ARTEMIS-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reopened ARTEMIS-2813: - Opening to keep track of these tests only running on 8 for now. > Kerberos tests failures on Java 11 > -- > > Key: ARTEMIS-2813 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2813 > Project: ActiveMQ Artemis > Issue Type: Test > Components: AMQP >Affects Versions: 2.14.0 >Reporter: Robbie Gemmell >Priority: Major > Fix For: 2.14.0 > > > The Kerberos tests in JMSSaslGssapiTest and SaslKrb5LDAPSecurityTest class > fail on Java 11. It isn't obvious that there is any issue here outside of the > Kerberos test harness bits themselves which are rather old, but not easily > updated as they have changed, so the tests will currently only be run on JDK8 > until such time as they can be made to work elsewhere. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (ARTEMIS-2813) Kerberos tests failures on Java 11
[ https://issues.apache.org/jira/browse/ARTEMIS-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161124#comment-17161124 ] Robbie Gemmell edited comment on ARTEMIS-2813 at 7/20/20, 10:31 AM: Reopening to keep track of these tests only running on 8 for now. was (Author: gemmellr): Opening to keep track of these tests only running on 8 for now. > Kerberos tests failures on Java 11 > -- > > Key: ARTEMIS-2813 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2813 > Project: ActiveMQ Artemis > Issue Type: Test > Components: AMQP >Affects Versions: 2.14.0 >Reporter: Robbie Gemmell >Priority: Major > > The Kerberos tests in JMSSaslGssapiTest and SaslKrb5LDAPSecurityTest class > fail on Java 11. It isn't obvious that there is any issue here outside of the > Kerberos test harness bits themselves which are rather old, but not easily > updated as they have changed, so the tests will currently only be run on JDK8 > until such time as they can be made to work elsewhere. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARTEMIS-2813) Kerberos tests failures on Java 11
[ https://issues.apache.org/jira/browse/ARTEMIS-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated ARTEMIS-2813: Fix Version/s: (was: 2.14.0) > Kerberos tests failures on Java 11 > -- > > Key: ARTEMIS-2813 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2813 > Project: ActiveMQ Artemis > Issue Type: Test > Components: AMQP >Affects Versions: 2.14.0 >Reporter: Robbie Gemmell >Priority: Major > > The Kerberos tests in JMSSaslGssapiTest and SaslKrb5LDAPSecurityTest class > fail on Java 11. It isn't obvious that there is any issue here outside of the > Kerberos test harness bits themselves which are rather old, but not easily > updated as they have changed, so the tests will currently only be run on JDK8 > until such time as they can be made to work elsewhere. -- This message was sent by Atlassian Jira (v8.3.4#803005)
