the QuickReload plugin doesn’t work when running Confluence (probably same issue with Jira) with a native arm64 JDK on M1 MacBooks:
java.lang.UnsatisfiedLinkError: Can't load library: /Users/jens/k15t/confluence-7.18/atlassian-confluence/temp/jpathwatch-nativelib-v-0-95-atlassian-1-libjpathwatch-native-32.dylib
It tries to load the native lib from these locations as well, but also fails (same stacktrace otherwise):
java.lang.UnsatisfiedLinkError: Can't load library: /Users/jens/k15t/confluence-7.18/atlassian-confluence/temp/jpathwatch-nativelib-v-0-95-atlassian-1-10280375601353966685libjpathwatch-native-32.dylib
java.lang.UnsatisfiedLinkError: no jpathwatch-native in java.library.path: [/Users/jens/Library/Java/Extensions, /Library/Java/Extensions, /Network/Library/Java/Extensions, /System/Library/Java/Extensions, /usr/lib/java, .]
Java Runtime Environment:
Operating System: Mac OS X 12.5.1
OS Architecture: aarch64
Application Server: Apache Tomcat/9.0.63
Servlet Version: 4.0
Java Version: 11.0.16
Java Vendor: Eclipse Adoptium
JVM Version: 11
JVM Vendor: Oracle Corporation
JVM Implementation Version: 11.0.16+8
Java Runtime: OpenJDK Runtime Environment
Java VM: OpenJDK 64-Bit Server VM
QuickReload version is 3.2.0
I assume this happens because there simply is no native library for arm64/aarch64 in the QuickReload plugin’s JAR.
Can you please fix this so we can continue to enjoy QuickReload?
I am able to replicate this issue in both JDK 1.8 and JDK 11 ( jdk-11.0.16) and able to resolve it with the below changes.
Please try with 11.0.3 or 11.0.9 version and add the below recommended configurations in the plugin’s POM where the product-specific plugin is configured.
Hi @SangeethaShanmugaSun, thanks for looking into this!
I’m using this on a standalone Confluence installation (installed according to the official installation guide), not an instance that’s started via maven. So I’m sure that those properties don’t affect it, because none of the dev tools using them are installed in that instance. I’m installing quickreload manually via UPM.
extractDependencies is set to
false in our product poms, though.
Also I don’t think going back to an older JVM version is a viable long term fix.
Could it be that your 11.0.3 or 11.0.9 JVM versions are x86_64 executables and not aarch64? Because I’m relatively sure that an aarch64 JVM cannot load the x86_64 shared libraries bundled in quickreload, failing with the error I mentioned above.
I just double checked the release archives of AdoptOpenJDK and Adoptium / Temurin.
AdoptOpenJDK doesn’t have any MacOS/aarch64 builds at all and the oldest release in the Adoptium archive for aarch64 is 11.0.15+10.
Are you using a JVM from another distributor?
Yeah, I am using the OracleJDK and below is the Runtime environment details
java version “11.0.3” 2019-04-16 LTS
Java™ SE Runtime Environment 18.9 (build 11.0.3+12-LTS)
Java HotSpot™ 64-Bit Server VM 18.9 (build 11.0.3+12-LTS, mixed mode) and platform is OSX Darwin Kernel Version 21.6.0 xnu-8020.141.5~2/RELEASE_ARM64_T6000 arm64.
Hi, when I use an x64 JVM then quickreload works as expected, but the point of this request was compatibility with aarm64 JVMs to avoid the performance impacts of running x64 executables on Rosetta.
As far as I understood the problem to enable this a new quickreload release would be required with a release of atlassian-jpathwatch containing an aarch64 version of the native library, essentially “libjpathwatch-native-aarm64.dylib” next to those: Bitbucket
@SangeethaShanmugaSun Any news if / when Atlassian is going to fix this? Thanks!
Hi @Jens, I will share an update once I get some information on this.
As it is a complete architectural change, internal discussions are in progress. We will get back with our timeline / decision.
@jens, @y from the bitbucket team experimenting the above requirement for tracking purpose we have create this ticket under QuickReload project, [QR-20] - Ecosystem Jira.
as this is not a direct feature implementation in atlassian products(not a customer ask), and this requirement is useful for the developers work on M1 MacBooks, we are looking for code contributors internally as we are already busy with other tasks.
however if the solution is ready by @y or any other contributors we will keep you post the updates.
thanks for reaching out to us.
Thanks @NarendraGhanta, I appreciate this being looked into!
Any chance I could get access to that ticket? It seems to be restricted but the project itself is not.
Here is the link for the ticket, [QR-20] - Ecosystem Jira, let me know you are able to access the same.
I get a “You don’t have access to this issue” message when opening
I can open other issues in that project such as
https://ecosystem.atlassian.net/browse/QR-18, so it seems to be some restriction on QR-20 and not on the project.
@jens this issue was recently fixed by @YingranSun and released with QuickReload 4.0.0.
I also removed restrictions on QR issues.
Hi @MichalSamujlo, thanks for letting me know.
I tested 4.0.0 and it works like a charm. Many thanks to you as well @YingranSun