You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Krzysztof Porebski (Jira)" <ji...@apache.org> on 2019/09/23 15:24:00 UTC

[jira] [Updated] (AMQNET-615) NmsMessageConsumer takes a lock on a static field

     [ https://issues.apache.org/jira/browse/AMQNET-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krzysztof Porebski updated AMQNET-615:
--------------------------------------
    Summary: NmsMessageConsumer takes a lock on a static field  (was: NmsMessageConsumer takes a lock on static field)

> NmsMessageConsumer takes a lock on a static field
> -------------------------------------------------
>
>                 Key: AMQNET-615
>                 URL: https://issues.apache.org/jira/browse/AMQNET-615
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: AMQP
>            Reporter: Krzysztof Porebski
>            Priority: Major
>             Fix For: 1.8.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> NmsMessageConsumer takes a lock on a static field, in order to support serial execution of messages. As a result messages are delivered in serial order even if the consumers do not share the same session. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)