You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/23 16:06:00 UTC
[jira] [Work logged] (AMQNET-615) NmsMessageConsumer takes a lock
on a static field
[ https://issues.apache.org/jira/browse/AMQNET-615?focusedWorklogId=316761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-316761 ]
ASF GitHub Bot logged work on AMQNET-615:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Sep/19 16:05
Start Date: 23/Sep/19 16:05
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #37: AMQNET-615: NmsMessageConsumer takes a lock on a static field
URL: https://github.com/apache/activemq-nms-amqp/pull/37#issuecomment-534165195
How does this affect ordering guarantees? For message groups for example with multiple consumers on the same session
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 316761)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)