[
https://issues.apache.org/jira/browse/QPIDJMS-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated QPIDJMS-581:
-------------------------------
Description:
Running qpid-jms (through cli-java, [https://github.com/rh-messaging/cli-java])
fails
{noformat}
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
{noformat}
{noformat}
16:07:31,067 WARN Unexpected exception in the selector loop.
io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed: Function
not implemented
{noformat}
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.
{quote}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
{quote}
{quote}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{quote}
{quote}Mikhail Krutov, 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
{quote}
was:
Running qpid-jms (through cli-java, [https://github.com/rh-messaging/cli-java])
fails
{noformat}
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
{noformat}
{noformat}
16:07:31,067 WARN Unexpected exception in the selector loop.
io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed: Function
not implemented
{noformat}
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.
{quote}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
{quote}
{quote}Mikhail Krutov, 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
{quote}
> Netty exception upon connect on Linux:
> io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed:
> Function not implemented
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPIDJMS-581
> URL: https://issues.apache.org/jira/browse/QPIDJMS-581
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 2.0.0
> Reporter: Jiri Daněk
> Priority: Major
> Fix For: 1.7.0, 2.1.0
>
>
> Running qpid-jms (through cli-java,
> [https://github.com/rh-messaging/cli-java]) fails
> {noformat}
> 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
> {noformat}
> {noformat}
> 16:07:31,067 WARN Unexpected exception in the selector loop.
> io.netty.channel.unix.Errors$NativeIoException: epoll_wait(..) failed:
> Function not implemented
> {noformat}
> 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.
> {quote}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
> {quote}
> {quote}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{quote}
> {quote}Mikhail Krutov, 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
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
