Yellowfin on Apple M1 Pro - issues?
I have recently installed Yellowfin on the new M1 Macbook using my dev license. Following specs.
Application Version: | 9.7.2 |
Build: | 20220602 |
Java Version: | 17.0.3.1 |
Operating System: | Mac OS X 12.4 (aarch64) |
Initially everything works and can import files, build connections, views, reports etc.
After a few hours use it becomes unusable. Are there any known issues with the M1 chip?I was careful to install the java version that is compatible.
For example.
I get this error in the yellowfin.log when attempting to export:
ERROR (V4ExportProcess) - [41] [B738AC36] [/MIExportAjaxAction.i4] Error: java.lang.RuntimeException: Report Identifier not specified
---
When I attempt to 'Browse' the spinner appears and never goes away - hangs.Yellowfin.log entry is:
ERROR (ContentProcess) - [60] [B738AC36] [/BrowseAjax.i4] com.hof.util.ActionErrorsException: java.lang.NullPointerException: Cannot invoke "java.lang.Integer.equals(Object)" because the return value of "com.hof.mi.data.ReportViewBean.getParentViewId()" is null
Thanks
Hi Scudfest,
It's a bit hard to come by hardware to test on the M1 chips, but luckily we do have one member of our team with an M1 Macbook Pro - I can confirm that unfortunately at this time the Docker image doesn't work on M1 hardware but I don't have any word on the standard install.
Have you installed the latest version of Azul Java for Mac, 17.0.3+7, Azul Zulu: 17.34.19?
Kind regards,
Chris
Hi Scudfest,
It's a bit hard to come by hardware to test on the M1 chips, but luckily we do have one member of our team with an M1 Macbook Pro - I can confirm that unfortunately at this time the Docker image doesn't work on M1 hardware but I don't have any word on the standard install.
Have you installed the latest version of Azul Java for Mac, 17.0.3+7, Azul Zulu: 17.34.19?
Kind regards,
Chris
I installed Azul Zulu: 17.34.19 and changed the JAVA_HOME value in catalina.sh to point to it.
Is that the correct procedure?
Unfortunately, same errors.
I installed Azul Zulu: 17.34.19 and changed the JAVA_HOME value in catalina.sh to point to it.
Is that the correct procedure?
Unfortunately, same errors.
Perhaps the same issue? --
https://community.yellowfinbi.com/topic/issues-with-running-yellowfin-on-java-17
Perhaps the same issue? --
https://community.yellowfinbi.com/topic/issues-with-running-yellowfin-on-java-17
Hi there,
Yes, it does seem there is a bug in Java 16 and 17 where some security changes may be causing issue. That is under review for 9.7.3.
In the meantime, my colleague is running Yellowfin with Java 1.8.0_331 on his MacBook with M1 Pro without issue. You may wish to try this instead.
Kind regards,
Chris
Hi there,
Yes, it does seem there is a bug in Java 16 and 17 where some security changes may be causing issue. That is under review for 9.7.3.
In the meantime, my colleague is running Yellowfin with Java 1.8.0_331 on his MacBook with M1 Pro without issue. You may wish to try this instead.
Kind regards,
Chris
Righto.
Gingerly operating a new installation using the Java 1.8.0_331 version. With frequent back-ups.
Will update if there are any issues using this set up.
kc
Righto.
Gingerly operating a new installation using the Java 1.8.0_331 version. With frequent back-ups.
Will update if there are any issues using this set up.
kc
Let me know who goes.
Kind regards,
Chris
Let me know who goes.
Kind regards,
Chris
Hi Kieran,
Just checking in with you on this one, were you able to get Yellowfin running correctly on your laptop with the different Java version?
Kind regards,
Chris
Hi Kieran,
Just checking in with you on this one, were you able to get Yellowfin running correctly on your laptop with the different Java version?
Kind regards,
Chris
I was able to get Yellowfin up and running with v17.The problem was that it would get corrupted or something a few days later. Then all work is lost.
So far using v1.8 it has not occurred yet.
Still feels like I'm walking on a field of and mines.
Time will tell.
kc
I was able to get Yellowfin up and running with v17.The problem was that it would get corrupted or something a few days later. Then all work is lost.
So far using v1.8 it has not occurred yet.
Still feels like I'm walking on a field of and mines.
Time will tell.
kc
Replies have been locked on this page!