-
Notifications
You must be signed in to change notification settings - Fork 222
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
Move to Java 8 #419
Comments
heroku, scalingo failing, needs updates on buildpack |
Ok, they still use openjdk 1.6. That's deprecated and potentially unsecure anyways |
@sudheesh001 do you update the build packages? Thanks for testing btw |
Bluemix works. http://loklak-server-dispensary-1744.mybluemix.net/ |
I just added c6450cc Please test heroku and scalingo deployment with this settings. Here is how you find out if the deployed loklak_server is actually running under Java 1.8:
|
@sudheesh001 Bluemix does NOT work, see http://loklak-server-dispensary-1744.mybluemix.net/api/threaddump.txt according to my hint above: this is still running under Java 1.7 |
Yup just noticed, somehow it seems to run whereas the others (heroku/scalingo) crash |
We must have a confirmation from the thread dump, otherwise all peers will crash when we switch to Java 1.8 |
I've moved locally to java8, everything seems to be working but in the
I don't remember seeing them before. The threaddump shows the following
|
@sudheesh001 i also get this in the master branch. Did you compile the java8 branch or master? As the ant buildfile in master is set to compile to source 1.7 (changed to 1.8 in the java8 branch) |
I just rebased this branch to include new commits from master, especially the system.properties file |
compiled the java8 branch. https://loklakjavajvm8.herokuapp.com/api/threaddump.txt here's the heroku deployment. |
heroku log
Uses jdk1.8 |
Bluemix deployment working with java 8 http://loklak-server-dispensary-1427.mybluemix.net/api/threaddump.txt |
Docker cloud http://loklak-1.loklakjava8.23a887be.cont.dockerapp.io:32770/api/threaddump.txt Runs |
ok, can you mark the checkboxes for all things tested? |
@Orbiter can you remove the java 7 buildbot? |
@treba123 i've marked it after testing for heroku, bluemix and docker cloud. Can someone test it for scalingo ideally it should work since it works for heroku but my trial for scalingo expired @daminisatya @shivenmian @jig08 Could any of you host the java8 branch on scalingo ? |
@sudheesh001 Sure, wait. |
@sudheesh001 It works when I went to https://my.scalingo.com/deploy?source=https://github.com/loklak/loklak_server/tree/java8 (i.e used the deploy button, just that I changed the source from master to java8 branch) It didn't work when I pulled the java8 branch, and deployed from my local machine. For the first method: https://loklaksm.scalingo.io/api/threaddump.txt But why should it not work when you deploy this app from your local machine? |
Can i have the scalingo URL deployed please ? |
I'd deployed it, had worked, but it's crashing right now. I'll do it again. |
No worries It says |
Yes it did, just crashed for some reason. I think you can merge the java8 branch to master. |
Thanks guys! I will wait for the buildbot to be java 8 only, as it will give us build errors for every PR |
@treba123 #430 I've removed java7 for automated build on TravisCI |
@sudheesh001 cool, lets merge that one. Do we still have to wait for anything? The docker thing? |
Great work, do we need to redeploy existing servers? |
I don't think so, but we'll have to when #427 gets merged. So maybe wait for that |
Correction: not even then, but as soon as we actually start checking for valid peer hashes |
Done #441 |
Before we can do this, we need to check if all one-click deployments support java 8
Branch: https://github.com/loklak/loklak_server/tree/java8
Please push changes needed for the switch in that branch instead of master, so we have don't have changes at different places.
Does support?
Checked if changes are needed?
Tested?
Other stuff:
The text was updated successfully, but these errors were encountered: