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

STOMP connections are not always cleanly closed #2606

Closed
LionelCons opened this issue May 27, 2019 · 2 comments · Fixed by #4895
Closed

STOMP connections are not always cleanly closed #2606

LionelCons opened this issue May 27, 2019 · 2 comments · Fixed by #4895

Comments

@LionelCons
Copy link

The STOMP specification (https://stomp.github.io/stomp-specification-1.2.html#DISCONNECT) indicates that connections should be closed using the DISCONNECT frame and a receipt.

It seems that there are 4 places where STOMP connections are created but not closed explicitly using stomp.py's disconnect(): lib/rucio/core/trace.py, lib/rucio/core/nongrid_trace.py and lib/rucio/daemons/hermes/hermes.py.

FWIW, disconnect() is used elsewhere: bin/rucio-cache-client, lib/rucio/daemons/cache/consumer.py, lib/rucio/daemons/conveyor/receiver.py and lib/rucio/daemons/tracer/kronos.py.

@bari12
Copy link
Member

bari12 commented May 27, 2019

Hi Lionel,
Thanks for reporting; We will have a look!

tbeerman added a commit to tbeerman/rucio that referenced this issue Jul 5, 2019
bari12 added a commit that referenced this issue Jul 5, 2019
…ermes

Hermes: cleanly close STOMP connections #2606
bari12 added a commit that referenced this issue Jul 5, 2019
…ermes

Hermes: cleanly close STOMP connections #2606
@ericvaandering
Copy link
Contributor

Reopening this issue

@ericvaandering ericvaandering reopened this Oct 6, 2021
@ericvaandering ericvaandering linked a pull request Oct 6, 2021 that will close this issue
@bari12 bari12 added this to the 1.26.6 milestone Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants