[
https://issues.apache.org/jira/browse/GEODE-9470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522985#comment-17522985
]
Darrel Schneider edited comment on GEODE-9470 at 4/19/22 11:29 PM:
-------------------------------------------------------------------
These setAccessible calls should not be an issue with geode 1.15 since any
domain classes added by the user to the server's class path will need to not be
in named modules so they will automatically be open to geode since both will be
in the unnamed module.
But we need to decide if we want to support user classes that are in named
modules for 1.15. If so then users will need to do an add-opens
was (Author: dschneider):
These setAccessible calls should not be an issue with geode 1.15 since any
domain classes added by the user to the server's class path will need to not be
in named modules so they will automatically be open to geode since both will be
in the unnamed module.
> Some geode queries will fail on java 16 and later
> -------------------------------------------------
>
> Key: GEODE-9470
> URL: https://issues.apache.org/jira/browse/GEODE-9470
> Project: Geode
> Issue Type: Bug
> Components: querying
> Reporter: Darrel Schneider
> Priority: Major
> Labels: Java16, Java17
>
> In some cases a geode query uses reflection to read a field or call a
> function.
> If that happens on java 16 then the query will fail throwing a
> RuntimeException that is an instance of
> java.lang.reflect.InaccessibleObjectException. See:
> https://softwaregarden.dev/en/posts/new-java/illegal-access-in-java-16.
> To workaround this failure set the JVM command line option:
> --illegal-access=permit
> The query code that calls setAccessible is in two places:
> org.apache.geode.cache.query.internal.AttributeDescriptor#getReadMember
> org.apache.geode.cache.query.internal.MethodDispatch#MethodDispatch
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
