[
https://issues.apache.org/jira/browse/DIRSTUDIO-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579234#comment-17579234
]
ben zoo commented on DIRSTUDIO-1293:
------------------------------------
I think I found the reason, why Apache Directory Studio is not working and
Eclipse works on Apple arm arhitecture.
This is the difference - check eclipse.ini file in:
* *ApacheDirectoryStudio* (cocoa.macosx.x86_64)
** /Applications/ApacheDirectoryStudio.app/Contents/Eclipse:
***
{code:java}
--launcher.library
../Eclipse/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.2.0.v20200915-1442{code}
* *Eclipse* (cocoa.macosx.aarch64)
** /Users/benzoo/eclipse/java-2022-06/Eclipse.app/Contents/Eclipse
***
{code:java}
--launcher.library
/Users/benzoo/.p2/pool/plugins/org.eclipse.equinox.launcher.cocoa.macosx.aarch64_1.2.500.v20220509-0833{code}
I can also confirm, that running ApacheDirectoryStudio on macos/arm also works
if openjdk@11 is installed for x86 arch, like this via brew:
{code:java}
$ arch -x86_64 /usr/local/homebrew/bin/brew install openjdk@11{code}
Of course it works slower via Rosetta in this way, but at least it works.
Please fix this mismatch, that native java can be used.
> Fails to start on MacOS Monterey
> --------------------------------
>
> Key: DIRSTUDIO-1293
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1293
> Project: Directory Studio
> Issue Type: Bug
> Components: studio-ldapbrowser
> Affects Versions: 2.0.0-M17
> Environment: Model Name: MacBook Pro
> Model Identifier: MacBookPro18,2
> Chip: Apple M1 Max
> Total Number of Cores: 10 (8 performance and 2 efficiency)
> Memory: 32 GB
> System Firmware Version: 7429.41.5
> OS Loader Version: 7429.41.5
> Reporter: Philip Peake
> Priority: Major
> Fix For: 2.0.0-M18
>
> Attachments: alert.png
>
>
> Launching Directory Studio fails with an error (see attached image),
> basically saying that the JNI_CreateJavaVM symbol is not found in
> libjvm.dylib.
> The symbol is actually there:
>
> {code:java}
> bin philip$ nm ../lib/server/libjvm.dylib | grep -i jni_create
> 00000000004e3190 T _JNI_CreateJavaVM
> {code}
>
> Tried two different java versions:
> * zulu-11.jdk
> * zulu-17.jdk
> Tried adding the path to the java version explicitly in the Info.plist file:
>
> {code:java}
> <array>
>
> <!-- to use a specific Java version (instead of the platform's default)
> uncomment one of the following options,
> or add a VM found via $/usr/libexec/java_home -V
>
> <string>-vm</string><string>/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Commands/java</string>
>
> <string>-vm</string><string>/Library/Java/JavaVirtualMachines/1.8.0.jdk/Contents/Home/bin/java</string>
> -->
>
> <string>-vm</string><string>/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home/bin/java</string>
> <string>-keyring</string>
> <string>~/.eclipse_keyring</string>
>
> </array>
> {code}
>
> This appears to be a problem in Eclipse/Directory Studio.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
