[QPIDJMS-581] Netty exception upon connect on Linux: io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed: Function not implemented

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Information Provided
• Affects Version/s: 2.0.0
• Component/s: qpid-jms-client
• Assignee: Unassigned
• Reporter: Jiri Daněk
• Created: 27/Sep/22 12:51
• Updated: 27/Sep/22 15:23
• Resolved: 27/Sep/22 15:23

Description

Running qpid-jms (through cli-java, https://github.com/rh-messaging/cli-java) fails

 command:
        - cli-qpid-sender
      image: quay.io/messaging/cli-java
      args:
        - '--broker'
        - >-
          amqp://persistence-ss-0.persistence-hdls-svc.shipshape-broker-bzh7k.svc.cluster.local:5672
        - '--address'
        - /someQueue
        - '--count'
        - '100'
        - '--timeout'
        - '40'
        - '--msg-content'
        - ABCDEFGHIJKLMNOPQRSTUVWXYZ
        - '--log-msgs'
        - json
        - '--on-release'
        - retry

16:07:31,067 WARN Unexpected exception in the selector loop.
io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed: Function not implemented

We suspect the issue is fixed by https://github.com/netty/netty/pull/12345 which is however not included in the version of netty used in 2.0.0 qpid-jms client.

Tim Bish, 2 min
io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed: Function not implemented
that indicates its trying to use Epoll
but appears that either A. the epoll version from netty is not right or it has a bug on whatever platform version you are running on so it thinks epoll is available but then falls over when it actually tries to use it

Tim Bish, Wed 7:14 PM
Checked back through the release and 2.0 uses 4.1.76.Final which doesn't not have the pwait fix so that would likely be the culprit
2.1.0 of Qpid JMS use 4.1.82.Final

Issue Links

• is fixed by: QPIDJMS-570 Update Netty to 4.1.82.Final