[ 
https://issues.apache.org/jira/browse/QPID-8482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17237911#comment-17237911
 ] 

ASF GitHub Bot commented on QPID-8482:
--------------------------------------

Dedeepya-T commented on a change in pull request #71:
URL: https://github.com/apache/qpid-broker-j/pull/71#discussion_r529243567



##########
File path: 
broker-core/src/main/java/org/apache/qpid/server/session/AMQPSession.java
##########
@@ -42,6 +42,9 @@
     @Override
     int getChannelId();
 
+    @Override

Review comment:
       Removed!




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> [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]

Reply via email to