-
Notifications
You must be signed in to change notification settings - Fork 85
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
Update docs to suggest correct JAVA_HOME configuration for tomcat #2222
Comments
thanks . . . I'll try to get that updated by next week |
but feel free to issue a PR if you want to edit in the doc directly |
fixes #2222 @jasonsydes does this look good?
fixes #2222 @jasonsydes does this look good?
Dear, any other solution? Cheers |
If you type:
what do you see? |
here you are lfaino@ZeusPV: |
I see @lfaino . You need to build with javac 8 You'll need to update your symlinks to use javac 8 version, or simply uninstall java / javac 11 in order to build it. Is it mac or linux? For mac homebrew has some nice workarounds. Conversely, you can also use Docker. |
I tried with docker and it works but how can I run the instance on the server and have it running after I close the terminal? |
@lfaino I would remove java / javac 11 unless you actually are using those features. You need javac version 8 to build it. If you want to run it somewhere else, you need to follow those instructions:
You can do all of this with docker as well, just depends on how many people you're trying to support. If you have still have trouble, if you provide more details on the installation that would be helpful (operation system, number of users, etc.) |
Hi Apollo!
We had recently upgraded to Ubuntu 18.04, and when we did, our longtime Apollo installation stopped working. I just spent the last several days banging my head against the problem, and I finally figured it out. I'm hoping you can make a minor tweak to your docs to help prevent others from experiencing the same.
In the end, it turned out to be conflicting installations of Java that did it in. Probably the Ubuntu upgrade to 18.04 installed Java11 alongside our existing Java8 install.
I was getting errors like the one I copy/pasted at the bottom. After many unsuccessful dead ends, I finally somehow stumbled upon a couple of comments by @nathandunn:
#1521 (comment)
#1521 (comment)
That lead me to try the following:
And that solved the problem.
But it's actually totally ok to have two different versions of Java installed, so long as you configured tomcat to use the correct Java, per Nathan's comments. Unfortunately, your docs here seem to imply that the following is sufficient to do so:
But it's not. On Ubuntu systems at least, you need to configure JAVA_HOME in /etc/default/tomcat8. For me, that looks like the following:
In /etc/default/tomcat8:
If you could update your docs to reflect that requirement, I think it could help many.
Thank you so much for developing Apollo for the community!!
The text was updated successfully, but these errors were encountered: