You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
'sdisconnect()
:lib/rucio/core/trace.py
,lib/rucio/core/nongrid_trace.py
andlib/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
andlib/rucio/daemons/tracer/kronos.py
.The text was updated successfully, but these errors were encountered: