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

Robbie Gemmell commented on QPIDJMS-443:
----------------------------------------

No, its unique (at a given point) per-session. I agree it is not explicitly 
stated that way (nor is it stated its per-connection, or anything else), and is 
instead just implicit in how the document outlines things overall. For example 
earlier in the spec it outlines that the session(+link) handles attach and 
detach, plus it is the session begin and not connection open that defines 
'handle-max' which is per-session, plus attempts to concurrently use a handle 
are defined as session-error and not a connection-error. I don't know of an 
implementation that considers things otherwise.

> Wrong handle id in AMQP 1.0 attach transport layer, when using different 
> sessions and producer among different threads
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-443
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-443
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.40.0
>            Reporter: morten
>            Priority: Critical
>         Attachments: qpid.jms.test.zip
>
>
> Hi,
> I found QPID JMS to not set the handle id [1] in the transport layer attach 
> [2] of the AMQP 1.0 specification correctly when using two different sessions 
> in two different threads. I tried to share one connection among two different 
> threads. Within the threads, a new session and a new producer is created (I 
> attached the code to reproduce the issue). If I capture the packets with 
> Wireshark I can see that the handle id is set to 0 for both sender.
> If there is only one session created and shared among the two different 
> threads two the handle id is set correctly.
> Even though for example a RabbitMQ does accept that I think this might be an 
> issue as the AMQP 1.0 specification states the following:
> _The handle MUST NOT be used for other open links. An attempt to attach using 
> a handle which is already associated with a link MUST be responded to with an 
> immediate 
> [close|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-close]
>  carrying a handle-in-use 
> [session-error|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-session-error]_
> I may misunderstand the specification.
> Regards
> Morten
>  
> [1] 
> [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#doc-link-handles]
> [2] 
> [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-attach]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to