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

TCP connection not closed even after the association is aborted #979

Open
shoibahamed opened this issue Nov 5, 2024 · 1 comment
Open
Labels

Comments

@shoibahamed
Copy link

The PACS after sending images, does not release the association. Hence the "Network timeout" is triggered.
When the association is timed out and aborted by the scp, the TCP connection remains in the ESTAB state. And it will remain in the ESTAB state until the application is restarted

I see this error on the prod environment and the PACS is STENTOR. However, I could not reproduce on my local

New connections are opened for every association and they remain open and eventually and application hits maximum_associations and then rejects all other associations that are trying to be opened with the error message - "local limit exceeded"

@scaramallion
Copy link
Member

scaramallion commented Nov 6, 2024

Can you post your code, the anonymised output from debug_logger(), details of the production environment and which version of pynetdicom you're using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants