lucee-dockerfiles icon indicating copy to clipboard operation
lucee-dockerfiles copied to clipboard

An illegal reflective access operation has occurred

Open fransvanberckel opened this issue 5 years ago • 6 comments

About 5.3.77-nginx: While starting tomcat and lucee as non root.

WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender (file:/usr/local/tomcat/lucee/lucee.jar) to method java.net.URLClassLoader.addURL(java.net.URL) WARNING: Please consider reporting this to the maintainers of org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release ERROR: Error creating bundle cache.

That's resolved with the latest, felix.framework-6.0.3? http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.3/doc/changelog.txt

fransvanberckel avatar Sep 07 '19 04:09 fransvanberckel

Check, today's lucee.jar-5.3.5.3 Snapshot has felix version 6.0.2.

Please update LDEV-2300 as well ;-) https://luceeserver.atlassian.net/browse/LDEV-2300

fransvanberckel avatar Sep 07 '19 05:09 fransvanberckel

Can you try the lucee/lucee:5.3.5.3-SNAPSHOT tag? Each commit has a snapshot build so that you can try the bleeding edge commits :)

On Sat., 7 Sep. 2019, 3:14 pm Frans van Berckel, [email protected] wrote:

Check lucee.jar-5.3.5.3 has felix.version=6.0.2. Please update LDEV-2300 as well ;-)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/lucee/lucee-dockerfiles/issues/56?email_source=notifications&email_token=AACVQDKXAGEPUAVQQ72J6ODQIM2DRA5CNFSM4IUOYJP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6EQPWY#issuecomment-529074139, or mute the thread https://github.com/notifications/unsubscribe-auth/AACVQDJ4RL7EUOETIIJBPFTQIM2DRANCNFSM4IUOYJPQ .

justincarter avatar Sep 07 '19 06:09 justincarter

I am not able to reproduce this issue at local machine. But if i build and check /usr/local/tomcat/logs/catalina.out from lucee:5.3.5.3-SNAPSHOT, it's still there.

fransvanberckel avatar Sep 07 '19 07:09 fransvanberckel

The WARNING is still there in the latest build (5.3.4.77);

10-Feb-2020 23:45:57.054 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.30]
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender (file:/usr/local/tomcat/lucee/lucee.jar) to method java.net.URLClassLoader.addURL(java.net.URL)
WARNING: Please consider reporting this to the maintainers of org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

However the error that you were getting (ERROR: Error creating bundle cache.) isn't present. There doesn't seem to be any negative side effects other than the warning at this time. Do you think there's anything else we should look at to try to resolve this?

justincarter avatar Feb 11 '20 01:02 justincarter

I'd prefer if we could get rid of the warnings; otherwise, one has to keep an inventory of "ignorable" errors/warnings when troubleshooting, updating Lucee, etc.

Otherwise, you have thoughts like:

  • Did my latest release / lucee upgrade cause this error/warning, or was it there before?
  • Does it matter? Let me go spend some cycles researching/remembering if I can ignore this or not.

jamiejackson avatar Mar 13 '20 16:03 jamiejackson

Agreed.

At this time I don't know of a way to remove the warning though, see; https://luceeserver.atlassian.net/browse/LDEV-2300

I'm not sure if Lucee can suppress the Felix warning, but it seems like an upstream issue more than a Docker image issue?

justincarter avatar Mar 23 '20 23:03 justincarter

This happens whether in docker or not. Since there is already a ticket for it in the main lucee repo, we can close this ticket.

cybersonic avatar Feb 29 '24 17:02 cybersonic