Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve exception message in ManagedSelector #6445

Open
rushalias opened this issue Jun 20, 2021 · 2 comments
Open

Improve exception message in ManagedSelector #6445

rushalias opened this issue Jun 20, 2021 · 2 comments
Assignees
Labels
Bug For general bugs on Jetty side Help Wanted

Comments

@rushalias
Copy link

Jetty version(s)
9.4.42.v20210604

Java version/vendor (use: java -version)
openjdk 11.0.11 2021-04-20 LTS
OpenJDK Runtime Environment Corretto-11.0.11.9.1 (build 11.0.11+9-LTS)
OpenJDK 64-Bit Server VM Corretto-11.0.11.9.1 (build 11.0.11+9-LTS, mixed mode)

OS type/version
In Kubernetes
Ubuntu 20 in userland container
Ubuntu 18 in kernel

Description
The message in the thrown exception is not accurate, there is no timeout involved. The exception is thrown if an attempt is made to use a SocketChannel that is in a pending state.
See: https://github.com/eclipse/jetty.project/blob/jetty-9.4.x/jetty-io/src/main/java/org/eclipse/jetty/io/ManagedSelector.java#L948-L957

        @Override
        public void run()
        {
            if (_selectorManager.isConnectionPending(channel))
            {
                if (LOG.isDebugEnabled())
                    LOG.debug("Channel {} timed out while connecting, closing it", channel);
                failed(new SocketTimeoutException("Connect Timeout"));
            }
        }

How to reproduce?
for reference: https://www.eclipse.org/lists/jetty-users/msg09911.html

@rushalias rushalias added the Bug For general bugs on Jetty side label Jun 20, 2021
@sbordet sbordet self-assigned this Jun 30, 2021
@github-actions
Copy link

github-actions bot commented Jul 1, 2022

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Jul 1, 2022
@sbordet sbordet removed the Stale For auto-closed stale issues and pull requests label Jul 2, 2022
@github-actions
Copy link

github-actions bot commented Jul 3, 2023

This issue has been automatically marked as stale because it has been a
full year without activity. It will be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the Stale For auto-closed stale issues and pull requests label Jul 3, 2023
@sbordet sbordet added Help Wanted and removed Stale For auto-closed stale issues and pull requests labels Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For general bugs on Jetty side Help Wanted
Projects
None yet
Development

No branches or pull requests

2 participants