You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "jorgheymans (via GitHub)" <gi...@apache.org> on 2023/05/08 09:51:25 UTC
[GitHub] [maven-mvnd] jorgheymans opened a new issue, #842: NPE during expiration check
jorgheymans opened a new issue, #842:
URL: https://github.com/apache/maven-mvnd/issues/842
Just encountered this on a maven build (regular clean install, small single module project)
```
Apache Maven Daemon (mvnd) 1.0-m6 linux-amd64 native client (47d4c6b9c399079d91312bb8ae35d1d76e7fd97a)
Terminal: org.jline.terminal.impl.PosixSysTerminal with pty org.jline.terminal.impl.jansi.linux.LinuxNativePty
Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: /home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn
Java version: 11.0.18, vendor: IBM Corporation, runtime: /home/user/.sdkman/candidates/java/11.0.18-sem
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.19.0-41-generic", arch: "amd64", family: "unix"
```
```11:42:54.378 D Expiration check running
11:42:54.378 E Problem in daemon expiration check
java.lang.NullPointerException: null
at org.mvndaemon.mvnd.daemon.DaemonMemoryStatus.isTrashing(DaemonMemoryStatus.java:163)
at org.mvndaemon.mvnd.daemon.DaemonExpiration.lambda$gcTrashing$0(DaemonExpiration.java:75)
at org.mvndaemon.mvnd.daemon.DaemonExpiration.lambda$any$9(DaemonExpiration.java:200)
at org.mvndaemon.mvnd.daemon.DaemonExpiration.lambda$any$9(DaemonExpiration.java:200)
at org.mvndaemon.mvnd.daemon.Server.expirationCheck(Server.java:321)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:839)
```
daemon log:
```
Starting daemon process: id = ddb5dd8d, workingDir = /home/user/src/auditing, daemonArgs: /home/user/.sdkman/candidates/java/11.0.18-sem/bin/java -classpath /home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn/boot/plexus-classworlds-2.6.0.jar -javaagent:/home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn/lib/mvnd/mvnd-agent-1.0-m6.jar -client -XX:+ClassRelationshipVerifier -Dmvnd.home=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39 -Dmaven.home=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn -Dmaven.conf=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn/conf -Dclassworlds.conf=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39/bin/mvnd-daemon.conf -Dmvnd.java.home=/home/user/.sdkman/candidates/java/11.0.18-sem -Dlogback.configurationFile=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39/mvn/conf/logging/logback-daemon.xml -Dmvnd.id=ddb5dd8d -Dmvnd.daemonStorage=/home/user/.m2/mvnd/registry/1.0-m6 -Dmvnd.registry=/home/user/.m2/mvnd/registry/1.0-m6/registry.bin -Dmvnd.socketFamily=inet -Dmvnd.h
ome=/home/user/.sdkman/candidates/mvnd/1.0-m6-m39 -Djdk.java.options=--add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED --add-opens java.base/sun.nio.fs=ALL-UNNAMED -Dmvnd.noDaemon=false -Dmvnd.debug=false -Dmvnd.debug.address=8000 -Dmvnd.idleTimeout=3h -Dmvnd.keepAlive=100ms -Dmvnd.extClasspath= -Dmvnd.coreExtensions= -Dmvnd.jvmArgs=-client -XX:+ClassRelationshipVerifier -Dmvnd.enableAssertions=false -Dmvnd.expirationCheckDelay=10s -Dmvnd.duplicateDaemonGracePeriod=10s -Dmvnd.socketFamily=inet org.codehaus.plexus.classworlds.launcher.LauncherNOTE: Picked up JDK_JAVA_OPTIONS: --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/sun.net.www.protocol.jar=ALL-UNNAMED --add-opens java.base/sun.nio.fs=ALL-UNNAMED
```
--
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.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] ppalaga commented on issue #842: NPE during expiration check
Posted by "ppalaga (via GitHub)" <gi...@apache.org>.
ppalaga commented on issue #842:
URL: https://github.com/apache/maven-mvnd/issues/842#issuecomment-1538490862
First a `null` strategy is a legit outcome of the code around here
https://github.com/apache/maven-mvnd/blob/a15abc25dfea50cf1479307a2ac0af2db7730f68/daemon/src/main/java/org/mvndaemon/mvnd/daemon/DaemonMemoryStatus.java#L110-L142
So isTrashing, isHeapSpaceExhausted & friends should not assume strategy being non-null
https://github.com/apache/maven-mvnd/blob/a15abc25dfea50cf1479307a2ac0af2db7730f68/daemon/src/main/java/org/mvndaemon/mvnd/daemon/DaemonMemoryStatus.java#L162-L171
Would you mind sending a PR?
Second, I wonder what GcStrategy params would catch your JVM `Java version: 11.0.18, vendor: IBM Corporation, runtime: /home/user/.sdkman/candidates/java/11.0.18-sem`?
https://github.com/apache/maven-mvnd/blob/a15abc25dfea50cf1479307a2ac0af2db7730f68/daemon/src/main/java/org/mvndaemon/mvnd/daemon/DaemonMemoryStatus.java#L49-L53
--
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.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-mvnd] gnodet closed issue #842: NPE during expiration check
Posted by "gnodet (via GitHub)" <gi...@apache.org>.
gnodet closed issue #842: NPE during expiration check
URL: https://github.com/apache/maven-mvnd/issues/842
--
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.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org