Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-2737

[AMQ 7.4, KQUEUE] Unable to check KQueue availability : java.lang.NoClassDefFoundError: io/netty/channel/kqueue/KQueue

    XMLWordPrintable

Details

    • ARTEMIS-2477
    • Hide

      To workaround the issue I downloaded netty-transport-native-kqueue-4.1.32.Final.jar and added it to the "AMQ7.4.0/lib".

      This appears to have resolved the issue.

      I suspect it may be possible to avoid this by setting "useKQueue=false" in the acceptors url BUT I have not tested this on AMQ 7.4.

      Show
      To workaround the issue I downloaded netty-transport-native-kqueue-4.1.32.Final.jar and added it to the "AMQ7.4.0/lib". This appears to have resolved the issue. I suspect it may be possible to avoid this by setting "useKQueue=false" in the acceptors url BUT I have not tested this on AMQ 7.4.
      • create a broker instance using AMQ 7.4.0 GA on MacOS and start.

    Description

      Starting AMQ 7.4 broker instance on MacOS logged a lot of the following warnings.

      2019-08-07 09:57:37,608 WARN  [org.apache.activemq.artemis.core.client] AMQ212073: Unable to check KQueue availability : java.lang.NoClassDefFoundError: io/netty/channel/kqueue/KQueue
	at org.apache.activemq.artemis.core.remoting.impl.netty.CheckDependencies.isKQueueAvailable(CheckDependencies.java:45) [artemis-core-client-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.start(NettyAcceptor.java:357) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.startAcceptors(RemotingServiceImpl.java:308) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.completeActivation(ActiveMQServerImpl.java:2921) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:74) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:600) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:527) [artemis-server-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.integration.FileBroker.start(FileBroker.java:70) [artemis-cli-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.cli.commands.Run.execute(Run.java:85) [artemis-cli-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.cli.Artemis.internalExecute(Artemis.java:150) [artemis-cli-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:98) [artemis-cli-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.cli.Artemis.execute(Artemis.java:125) [artemis-cli-2.9.0.redhat-00002.jar:2.9.0.redhat-00002]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_20]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_20]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_20]
	at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0_20]
	at org.apache.activemq.artemis.boot.Artemis.execute(Artemis.java:129) [artemis-boot.jar:2.9.0.redhat-00002]
	at org.apache.activemq.artemis.boot.Artemis.main(Artemis.java:49) [artemis-boot.jar:2.9.0.redhat-00002]

      In a master/slave replication it was extremely noisy in the logging.

      It seems there where changes in this area - see ARTEMIS-2301

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3100 [AMQ 7.4, KQUEUE] Unable to check KQueue availability : java.lang.NoClassDefFoundError: io/netty/channel/kqueue/KQueue

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-pfox Patrick Fox (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: