Affects Version/s: qpid-java-broker-7.1.3
Fix Version/s: None
When peer sends a subsequent attach for already active link (the link name is the same but handle is different), the broker ends session with internal error ("Endpoint is already registered with session.").
This behaviour looks not spec complaint to me for the following reasons:
- it is not a broker internal error
- the error is related to the link rather than session. Thus, session ending looks like too radical action
IMHO, the broker can potentially utilize the following behaviour to handle this situation
- apply link stealing functionality (detach active link and attach new one)
- reply with attach followed by detach with error "amqp:link:detach-forced"
The latter looks like more appropriate behaviour to me. Though, we use the former to steal link by a different session.
Here is relevant broker logs for the issue