# Illegal reflective access by com.headius.backport9.modules.Modules **URL:** \ **Category:** Logstash\ **Created:** [June 17, 2019, 10:06am UTC](https://discuss.elastic.co/t/illegal-reflective-access-by-com-headius-backport9-modules-modules/186035 "2019-06-17T10:06:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![lbarbero](https://avatars.discourse-cdn.com/v4/letter/l/a8b319/32.png) [@lbarbero](https://discuss.elastic.co/u/lbarbero)\ **Post date:** [June 17, 2019, 10:06am UTC](https://discuss.elastic.co/t/illegal-reflective-access-by-com-headius-backport9-modules-modules/186035/1 "2019-06-17T10:06:13Z")
Hello, I am trying to run logstash 7.1 with java 11. I start the service with systemctl start logstash.servise and I get a warning when I check the service status: _● logstash.service - logstash_ - Loaded: loaded (/etc/systemd/system/logstash.service; disabled; vendor preset: enabled)\* - Active: active (running) since Mon 2019-06-17 11:44:41 CEST; 8s ago\* - Main PID: 2669 (java)\* - Tasks: 18 (limit: 4915)\* - CGroup: /system.slice/logstash.service\* - ``` └─2669 /usr/bin/java -Xms4g -Xmx4g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djruby.compile.invokedynamic=true -Djruby.jit.threshold=0 -XX:+HeapDumpOnOutOfMemoryError -Djava.security.egd=file:/dev/urandom -cp /usr/share/logstash/logstash-core/lib/jars/animal-sniffer-annotations-1.14.jar:/usr/share/logstash/logstash-core/lib/jars/commons-codec-1.11.jar:/usr/share/logstash/logstash-core/lib/jars/commons-compiler-3.0.11.jar:/usr/share/logstash/logstash-core/lib/jars/error_prone_annotations-2.0.18.jar:/usr/share/logstash/logstash-core/lib/jars/google-java-format-1.1.jar:/usr/share/logstash/logstash-core/lib/jars/gradle-license-report-0.7.1.jar:/usr/share/logstash/logstash-core/lib/jars/guava-22.0.jar:/usr/share/logstash/logstash-core/lib/jars/j2objc-annotations-1.1.jar:/usr/share/logstash/logstash-core/lib/jars/jackson-annotations-2.9.8.jar:/usr/share/logstash/logstash-core/lib/jars/jackson-core-2.9.8.jar:/usr/share/logstash/logstash-core/lib/jars/jackson-databind-2.9.8.jar:/usr/share/logstash/logstash-core/lib/jars/jackson-dataformat-cbor-2.9.8.jar:/usr/share/logstash/logstash-core/lib/jars/janino-3.0.11.jar:/usr/share/logstash/logstash-core/lib/jars/javassist-3.24.0-GA.jar:/usr/share/logstash/logstash-core/lib/jars/jruby-complete-9.2.7.0.jar:/usr/share/logstash/logstash-core/lib/jars/jsr305-1.3.9.jar:/usr/share/logstash/logstash-core/lib/jars/log4j-api-2.11.1.jar:/usr/share/logstash/logstash-core/lib/jars/log4j-core-2.11.1.jar:/usr/share/logstash/logstash-core/lib/jars/log4j-slf4j-impl-2.11.1.jar:/usr/share/logstash/logstash-core/lib/jars/logstash-core.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.commands-3.6.0.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.contenttype-3.4.100.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.expressions-3.4.300.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.filesystem-1.3.100.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.jobs-3.5.100.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.resources-3.7.100.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.core.runtime-3.7.0.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.equinox.app-1.3.100.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.equinox.common-3.6.0.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.equinox.preferences-3.4.1.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.equinox.registry-3.5.101.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.jdt.core-3.10.0.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.osgi-3.7.1.jar:/usr/share/logstash/logstash-core/lib/jars/org.eclipse.text-3.5.101.jar:/usr/share/logstash/logstash-core/lib/jars/slf4j-api-1.7.25.jar org.logstash.Logstash --path.settings /etc/logstash* ``` _jun 17 11:44:41 logmonitor systemd[1]: Started logstash._ _jun 17 11:44:41 logmonitor logstash[2669]: Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release._ _jun 17 11:44:42 logmonitor logstash[2669]: WARNING: An illegal reflective access operation has occurred_ _jun 17 11:44:42 logmonitor logstash[2669]: WARNING: Illegal reflective access by com.headius.backport9.modules.Modules (file:/usr/share/logstash/logstash-core/lib/jars/jruby-complete-9.2.7.0.jar) to field java.io.FileDescriptor.fd_ _jun 17 11:44:42 logmonitor logstash[2669]: WARNING: Please consider reporting this to the maintainers of com.headius.backport9.modules.Modules_ _jun 17 11:44:42 logmonitor logstash[2669]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations_ _jun 17 11:44:42 logmonitor logstash[2669]: WARNING: All illegal access operations will be denied in a future release_ I have intalled logstash 7.1 in another machine which has java8 instead java 11 and the warning does not show. This second machine just shows that warning when I upgrade java versión to java11. Java 8 has reached end of his live so I want to make it run with java11 if posible. ¿any ideas how could I fix this problem? Regards ---
**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\ **Post date:** [June 17, 2019, 1:16pm UTC](https://discuss.elastic.co/t/illegal-reflective-access-by-com-headius-backport9-modules-modules/186035/2 "2019-06-17T13:16:50Z")
An [issue](https://github.com/headius/backport9/issues/2) has been opened against that code. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 15, 2019, 1:16pm UTC](https://discuss.elastic.co/t/illegal-reflective-access-by-com-headius-backport9-modules-modules/186035/3 "2019-07-15T13:16:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.