Closed flaix closed 1 year ago
A possible work-around would be to set the --illegal-access=permit
parameter to the JVM command line.
A possible work-around would be to set the
--illegal-access=permit
parameter to the JVM command line.
How did you solve it
Who? The OP is running Gitblit as a WAR in a Tomcat application server, where this problem does not manifest. The posted stack trace is from the stand-alone Gitblit GO version starting up.
The --illegal-access=permit
parameter is not going to cut it, because from Java 17 on it is disabled. So as another workaround, the --add-opens
option could be employed. Maybe. It helps for startup, to get around problems with Guice by setting it for java.base/java.lang=ALL-UNNAMED
. But I found no application for accesses from Lucene when indexing. Which might be solved with dependency updates.
So a fix for this is left for version 1.10 and later.
I am going to close this issue in favour of #1420, because Java 17 is the current LTS release, so that is the one to target for Gitblit.
My java SDK is v16.
When start gitblit,log is
stderr
stdout
When access http://localhost:8090, the browser shows TIMEOUT. This should be gitblit can not working with jave v16.
So, I use gitblit war, with java v16 and Tomcat9, extract gitblit war to tomcat/webapps, it works for me.
Thanks.
Originally posted by @x1244 in https://github.com/gitblit/gitblit/issues/1315#issuecomment-887429686