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

Connection leak in TCP adaptor #927

Closed
ted-ross opened this issue Jan 31, 2023 · 3 comments
Closed

Connection leak in TCP adaptor #927

ted-ross opened this issue Jan 31, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@ted-ross
Copy link
Member

To reproduce: Configure a single router with a tcp listener and a matching tcp connector. The Host/Port of the connector should be invalid (i.e. not referencing a valid server socket).

Use curl or similar to establish a connection to the listener port. This connection hangs (is that correct?). Then ^C the client to force the connection closed.

Now shut down the router. It will assert with a leak-check failure due to the fact that the connector has a too-high reference count. The connection was not cleaned up when the client was forcefully disconnected.

@ted-ross ted-ross added the bug Something isn't working label Jan 31, 2023
@ganeshmurthy ganeshmurthy self-assigned this Jan 31, 2023
@ted-ross
Copy link
Member Author

Configuration used:

router {
    mode: standalone
}

listener {
    host: 0.0.0.0
    port: amqp
    authenticatePeer: no
    saslMechanisms: ANONYMOUS
}

tcpConnector {
    name: echo-1
    host: 10.108.50.177
    port: 9090
    address: echo
}

tcpConnector {
    name: echo-2
    host: 10.108.50.177
    port: 9090
    address: echo
}

tcpListener {
    host: 0.0.0.0
    port: 9000
    address: echo
}

log {
    module: ROUTER_CORE
    enable: debug+
}

@ted-ross
Copy link
Member Author

Command used: curl http://localhost:9000/api

@ganeshmurthy
Copy link
Contributor

Cannot reproduce using the new TCP Adaptor

@ganeshmurthy ganeshmurthy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants