Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-19326

LinkageError: loader constraint violation for class io.netty.*

XMLWordPrintable

    • Hide 
      uznip hotrod_query.zip
mvn package
cp ROOT.war <wfly_server>/standalone/deployments
standalone.sh -c standalone-microprofile.xml
curl http://127.0.0.1:8080/hotrod?operation=read&cache=respCache&key=mykey
# exception emitted in server log
      Show
      uznip hotrod_query.zip mvn package cp ROOT.war <wfly_server>/standalone/deployments standalone.sh -c standalone-microprofile.xml curl http: //127.0.0.1:8080/hotrod?operation=read&cache=respCache&key=mykey # exception emitted in server log
    • Workaround Exists
    • Hide

      I was able to overcome that problem by changing war infinispan-client-hotrod dependency from compile scope to provided scope and adding app dependency on module org.infinispan.client.hotrod into jboss-deployment-structure.xml.

      But note, customers who does not have access to app sources (we know such exists) will be not able to apply such workaround.

      Show
      I was able to overcome that problem by changing war infinispan-client-hotrod dependency from compile scope to provided scope and adding app dependency on module org.infinispan.client.hotrod into jboss-deployment-structure.xml. But note, customers who does not have access to app sources (we know such exists) will be not able to apply such workaround.
    • ---
    • ---

      The wildfly-opentelemetry module improperly exports too many modules, which causes the error in issue title if applications are deployed which package those libraries. The module should only expose APIs that users are expected to interact with explicitly as part of the module's contract.:

      "io.smallrye.opentelemetry",
"io.vertx.core",
"io.vertx.grpc-client",
"io.netty.netty-buffer"

              jaslee@redhat.com Jason Lee
              jaslee@redhat.com Jason Lee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: