-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modelio 4.1.0 fails to start on MacOS #12
Comments
Hello UPDATE 2: Used https://www.modelio.org/forum/8-installation/3962-running-modelio-on-a-macos-x-workstation.html. It works. You just have to copy fixModelio40.sh to fixModelio41.sh (and update Modelio path inside), put it in /Applications and run it from there. You may have a too recent Java version (JAXB not found). |
I tried the script as well as a manual update of the modelio.io file and it did not work for me. I also shared similar information on the modeliol.org forums via the following two links. https://www.modelio.org/forum/8-installation/4797-after-run-modelio-i-get-alert-java-lang-nullpointerexception-java-lang-nullpoint.html#6290 I believe both the info.plist in the Eclipse folder and modelio.io in the MacOS folder are pointing to the java 1.8 jdk location /Library/Java/JavaVirtualMachines/jdk1.8.0_271.jdk/Contents/Home In the modelio.ini it is right after -clearPersistedState as follows -vm In info.plist it is listed in the Eclipse section as follows
In the modelio log file it first starts producing a NullPointerException here: 2021-01-09 04:16:07,610 INFO LogService - Running batch: project=null create=false workspace=null It is not clear to me what to try next. |
Hello @jimjohan what you experienced is interesting. I spent 30 min today with a student of mine, having him install things (JDK 8), set up JAVA_HOME in his .zshenv file, etc. In the end he got the same problem than you (a null pointer exception). |
That procedure is certainly going to be beyond what most of the data modelers in our team could get done. Isn't it possible to download a modelio with the required jre bundled and set up for use? An extra jre isn't that much disc space. |
@retorquere - Your suggestion of having the Mac installer include its own embedded jre is an excellent suggestion and I hope that happens in the future. If there is something I can do to help out on that let me know. I think the embedded jre is what is done for the Windows installer, and I think it may also be the case for the Linux installer (at least the Debian version). |
@pascalpoizat - Thank you for the useful insights. Perhaps we are shaking the tree enough and slowly figuring out what is going on. The fact there seems to be a common issue for several IDEs and a DB manager, may suggest there is something going on with Big Sur. I am not sure how to troubleshoot within the OS or discern what the difference is between Catalina and Big Sur. Doing a search for "big sur java 8 support" I found this post in an apple developer forum: https://developer.apple.com/forums/thread/655774 and I saw a few interesting comments: @swpalmer "Note that Big Sur breaks the previous behaviour of the JAVA_HOME environment variable to pick the Java version used to run the command-line tools. If this matters to you, consider filing an bug report." @etresoft "What directory are you in? Java works fine here, but not in a restricted directory like Downloads. If I move to /tmp, then everything works as expected." If Big Sur changes what JAVA_HOME does there may be a need to do some kind of patch in modelio. If multiple apps experience it there may be a short term fix to get it operational and maybe in a future Big Sur release Apple will provide some better resolution. |
My information quoted here is a bit stale.
JAVA_HOME still works, but the /usr/libexec/java_home tool works differently.
If JAVA_HOME is set to a valid JDK, the java_home tool just returns what it is set to, regardless of the -v option passed. If it is set to an invalid JDK folder, the java_home tool fails. For these reasons, code that uses the java_home tool to pick a value for the JAVA_HOME environment variable may fail on Big Sur when it worked on previous version of macOS. The work-around is to unset JAVA_HOME before using the java_home tool.
Regards,
Scott
… On Jan 14, 2021, at 3:07 PM, jimjohan ***@***.***> wrote:
@pascalpoizat - Thank you for the useful insights. Perhaps we are shaking the tree enough and slowly figuring out what is going on. The fact there seems to be a common issue for several IDEs and a DB manager, may suggest there is something going on with Big Sur. I am not sure how to troubleshoot within the OS or discern what the difference is between Catalina and Big Sur.
Doing a search for "big sur java 8 support" I found this post in an apple developer forum: https://developer.apple.com/forums/thread/655774 and I saw a few interesting comments:
@swpalmer "Note that Big Sur breaks the previous behaviour of the JAVA_HOME environment variable to pick the Java version used to run the command-line tools. If this matters to you, consider filing an bug report."
@etresoft "What directory are you in? Java works fine here, but not in a restricted directory like Downloads. If I move to /tmp, then everything works as expected."
If Big Sur changes what JAVA_HOME does there may be a need to do some kind of patch in modelio. If multiple apps experience it there may be a short term fix to get it operational and maybe in a future Big Sur release Apple will provide some better resolution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@swpalmer - Thank you for the helpful information. If you have enough insight into modelio, is there anyway to adapt the start up routine without rebuilding the whole program to address the java_home issue you flagged? |
In an attempt to try to answer my own question I downloaded the modelio source and looked for all the places jave_home occurred. The only place it comes up is in the Eclipse info.plist file. I deleted the specific location where I had the file and replaced it with grep -lr java_home /Downloads/Modelio-master/* Looking at my log file more carefully and thinking on where java_home might be invoked and cause an error perhaps the issue still is within the use of eclipse. Here is an excerpt from my log file showing that it is running Main.java when it generates an error at org.eclipse.equinox.launcher.Main.run(Main.java:1501) Trying to look around for this file I found this information on the Equinox Framework https://www.eclipse.org/equinox/framework/ Java Launcher (org.eclipse.equinox.launcher)This helps setup the framework classloader and launches the Framework etc. Note: this code used to be included in the startup.jar and has be moved from its old location in the org.eclipse.platform project. See bug 113069 for more details. I will keep exploring, but also appreciate other folk's comments. |
@jimjohan |
My apologies if I referenced the wrong person, this was not my intent. |
After following the instructions at https://www.modelio.org/forum/8-installation/3962-running-modelio-on-a-macos-x-workstation.html it "launches" for me on Big Sur... but then quickly reports a NPE and most actions that I attempted fail with the same NPE message. But the main GUI is showing something, though things are clearly very broken... |
Regarding Big Sur, see my comment here #10 (comment) |
@Phillipus Thank you for your comments and wonderful suggestions. The fact this issue is coming up in multiple threads indicates to me it is coming up for a variety of individuals. Updating the Eclipse dependency and including a self contained jre seems like the way to got, and I believe will make it match the Windows and Linux installers. Do you want to formally suggest the change to the modelio developers (which may include you, but I do not know)? I can help if you like. |
@jimjohan I am not affiliated in any way with Modelio. Perhaps it would be better if the Modelio devs responded to their users rather than me having to explain why their stuff doesn't work on Mac. |
Hello, |
@pascalpoizat, thank you for your innovative workaround. I hope there could be a native fix in the near term, but COVID-19 is slowing things down. I just upgraded to Big Sur 11.2, hoping this might help, but nothing changed. Modelio and other things still do not work. It looks like your optional build isolates modelio to work in a separate X window. This sounds interesting, and XQuartz reminds me of what was required to run a different legacy application in the past. This is something I will try to use, as long as it does not open any vulnerabilities. I will try it first on a test machine. Thank you. |
@pascalpoizat, Over the weekend, I tried your solution you recommended at https://github.com/pascalpoizat/docker-modelio, and it worked perfectly in an X window with Big Sur. I will share this option with students in my class. Thank you. |
Hello @jimjohan , I am happy it works for you. Please note that one of my students told me it did not work on his configuration (I have not investigated more, but maybe the best is to ask your students to try at least 1 week before the beginning of your lectures). Also (for all readers) please note that I only made some updates to an existing docker file + following advices found on the net (references are in the README) so most of the thanks goes to them. |
@pascalpoizat I, unfortunately, had the same thing happen. Modelio worked within the Docker environment, and then it stopped. |
Hello @jimjohan Pascal |
@pascalpoizat |
@pascalpoizat - Thanks for your help here, unfortunately I am getting an error when launching run.sh
This comes up in a pop-up with a "Modelio" header. |
Hi @lalligagger (I have also seen that @jimjohan found that it does not work anymore).
|
I will try running again the process from Setup / step 6 in https://github.com/pascalpoizat/docker-modelio/blob/master/README.md (it takes some time downloading Modelio on my poor Internet connection). |
@pascalpoizat thanks for the quick reply! This is actually my first time getting a Docker container built. If you let me know what to add to the Dockerfile (?) to print logs/ save locally I will attach here. |
I just got as far as the splash screen by rolling back to version 4.0.1 in the download path. I'll count that as progress for now! |
It is unfortunate that the BigSur install of both Modelio Open Source and
Modelo SA do not work and there is no ETA when a fix will be made. On the
other hand Apple created a new Big Sur MacOS that breaks many applications,
and this is just one example.
…On Sat, Apr 17, 2021 at 3:44 PM lalligagger ***@***.***> wrote:
I just got as far as the splash screen by rolling back to version 4.0.1 in
the download path. I'll count that as progress for now!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF4YC4GBWRZXVQM7OLYGSTLTJIFNVANCNFSM4UQTZS4A>
.
|
Hello @lalligagger |
@jimjohan Apple big upgrades are sometimes problematic. Indeed for this one (and Catalina before) our system engineers have warned us at the lab to wait before upgrading. Indeed when I finally moved to Catalina ... I lost my internal Webcam (just before an offline lecture session, very practical indeed). :-( |
Could someone at Modelio comment as to where they are with their Mac efforts and where it fits on their roadmap? (Seeing as last update was April and now it's just about August). |
I'm pretty sure this has nothing to do with Apple and Big Sur. The error message is pretty clear, it can not load a class: java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException I mean: seriously? No one realised it is a "CLASS NOT FOUND!" Error? Obviously the class is not on the CLASSPATH. How can that be? Well, you are running the application under Java > Version 8!! With Version 9, Java introduced the "Module System". The XML modules need to be "imported" to be on the CLASSPATH. There are some -XX (or similar) command line options to the JVM to make it include/import those modules. That is absolutely not Mac specific, it is a problem of the JVM version and the transition to modules. If I figure the option, I update here. I myself want to start Modelio from inside of the IDE: and I can not even figure what the main class is. It seems to be started in a super odd way. If anyone has a hint for that, this would be appreciated. |
Hi, I need to have a version of modelio for my macbook for my thesis project, where can I find an older version? |
I'm on big sur if that matters; I've just downloaded and during start it says "an error has occurred" pointing to a log, which says
The text was updated successfully, but these errors were encountered: