Open sken130 opened 3 months ago
/cc @geoand (kotlin)
Can try again with Java 17 or 21? Java 18 is not supported. I doubt the Java version will change anything, I just want to be sure.
The result is the same using Java 21. Attached are more thread dumps. threaddumps-20240607.zip
I will also edit the issue to include the most relevant part of stack trace.
Thanks for checking.
From the stacktrace, it looks like a Gradle bug instead of a Quarkus one.
@gsmet do we know anyone from Gradle that can have a look at this?
Describe the bug
I was trying to update Quarkus from 3.5.3 to latest (3.11.1 at the time of this report)
OS: Windows Server 2019 Datacenter Java version running the quarkus update command: 18.0.2.1 and 21.0.2 Gradle version: 8.8
build.gradle:
Relevant final Java command from Task Manager/Process Explorer:
"C:\Program Files\Eclipse Adoptium\jdk-21.0.2.13-hotspot/bin/java.exe" "-Xmx64m" "-Xms64m" "-Dorg.gradle.appname=gradlew" -classpath "C:\path\to\project\\gradle\wrapper\gradle-wrapper.jar" org.gradle.wrapper.GradleWrapperMain --console plain --stacktrace --init-script C:\Users\xxxxx\AppData\Local\Temp\2\openrewrite-init14975923088595330686gradle rewriteRun
Console output with Java 21:
Console output using Java 18:
Thread dumps are attached too.
threaddumps-20240606.zip
The most relevant stack trace:
Expected behavior
The
quarkus update
should have a response, no matter succeeded or failed.Actual behavior
It's hung, and seems waiting forever.
How to Reproduce?
Run
quarkus update --verbose
in consoleOutput of
uname -a
orver
No response
Output of
java -version
18.0.2.1 and 21.0.2
Quarkus version or git rev
3.5.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.8
Additional information
No response