[
https://issues.apache.org/jira/browse/QPID-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8482:
-----------------------------
Description:
AMQP 0-10 requires to use a unique session name. If session with a given name
already exists, the attach attempt ends up in detach being sent from broker
with {{session-busy}} detach code. The attach session name is not exposed in
any way via management. Thus, it is not possible to determine what session
names are already used.
Potentially, the name provided in attach can be exposed as a derived
attribute. It will allow to debug and identify such issues like client
disconnects due to session name being already used by other sessions.
was:
AMQP 0-10 requires to use a unique session name. If session with a given name
already exists, the attach attempt ends up in detach being sent from broker
with {{session-busy}} detach code. The attach session name is not exposed in
any way via management. Thus, it is not possible to determine what session
names are already used.
Potentially, the name provided in attach can be used as a model session name.
It will allow to debug and identify such issues like client disconnects due to
session name being already used by other sessions.
A Binary type is used for session name in attach. The broker can try to convert
the given bytes into string. If provided bytes are valid character bytes, we
can create a session name from those bytes. Otherwise, base64 encoding can be
used to create a session name.
> [Broker-J][AMQP 0-10] Derive model session name from the name passed in attach
> ------------------------------------------------------------------------------
>
> Key: QPID-8482
> URL: https://issues.apache.org/jira/browse/QPID-8482
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Alex Rudyy
> Priority: Major
>
> AMQP 0-10 requires to use a unique session name. If session with a given name
> already exists, the attach attempt ends up in detach being sent from broker
> with {{session-busy}} detach code. The attach session name is not exposed in
> any way via management. Thus, it is not possible to determine what session
> names are already used.
> Potentially, the name provided in attach can be exposed as a derived
> attribute. It will allow to debug and identify such issues like client
> disconnects due to session name being already used by other sessions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
