Why are these warnings a issue for you? On Tue, Jun 3, 2025 at 1:45 AM James Pedersen <james00...@gmail.com> wrote:
> I'm curious about this. > > On Tue, Jun 3, 2025 at 1:45 AM James Pedersen <james00...@gmail.com> > wrote: > >> Did it make the problem go away, though? >> >> On Tue, Jun 3, 2025 at 12:49 AM Roar Brænden <roar.brenden...@gmail.com> >> wrote: >> >>> Hi, >>> >>> I'm using Tomee 10.0.1 with JDK 21. One of my end-points is using Lucene >>> index for some search result. The Lucene jar is version 10.2.1, which is >>> using the new Vector API. >>> When using this library I notice some warnings in the log: >>> >>> >>> WARNING: A restricted method in java.lang.foreign.Linker has been called >>> WARNING: java.lang.foreign.Linker::downcallHandle has been called by the >>> unnamed module >>> WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for >>> this module >>> >>> 03-Jun-2025 09:40:17.597 WARNING [http-nio-8091-exec-2] >>> org.apache.lucene.internal.vectorization.VectorizationProvider.lookup Java >>> vector incubator module is not readable. For optimal vector performance, >>> pass '--add-modules jdk.incubator.vector' to enable Vector API. >>> >>> To avoid these messages, I tried to add args to my tomee-maven-plugin >>> configuration: >>> >>> <args>enable-native-access=ALL-UNNAMED</args> >>> <args>add-modules=jdk.incubator.vector</args> >>> >>> What I noticed is that only the last one will be taken into >>> consideration. Meaning that with these settings I will get the first >>> WARNING, and a message indicating that the Vector API is found. If I switch >>> the args, I will get the last WARNING. >>> Is this a know problem with the plugin configuration? >>> >>> Best regards, >>> Roar Brænden >>> >>>
