[jira] [Commented] (AMQ-6000) Pause/resume feature of ActiveMQ not resuming properly

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14999315#comment-14999315
 ] 

ASF subversion and git services commented on AMQ-6000:
--

Commit 078a101cf735ae23ebf96b3bbe3f53003dccc0c7 in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=078a101 ]

https://issues.apache.org/jira/browse/AMQ-6000

Fix and test, wakeup queue dispatch when resume is called.

> Pause/resume feature of ActiveMQ not resuming properly
> --
>
> Key: AMQ-6000
> URL: https://issues.apache.org/jira/browse/AMQ-6000
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JMX
>Affects Versions: 5.12.0
>Reporter: M Rahimi
>  Labels: features
> Fix For: 5.13.0
>
>
> The problem is that, when you *resume* the message delivery,
> # If there is a message entering the queue: the broker will immediately send 
> the pending messages to the consumer which is totally OK.
> # But if no message _enters_ the queue: the pending messages in the queue 
> will not be sent to the consumers until the expiration checking is performed 
> on the queue (which by default is 30 seconds and can be controlled by the 
> _expireMessagesPeriod_ attribute) and non-expired messages will be sent to 
> the consumers afterwards.
> Obviously we can change the _expireMessagesPeriod_ to limit this delay, but 
> when you need a milisec precision, performing the expiration check every 
> milisec will not make sense.
> How is it possible to force the queue to start sending messages immediately 
> after resumption?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6000) Pause/resume feature of ActiveMQ not resuming properly

[Gary Tully (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944885#comment-14944885
 ] 

Gary Tully commented on AMQ-6000:
-

To sort this, I think there should be a call to wakeup() in 
org.apache.activemq.broker.region.Queue#resumeDispatch

> Pause/resume feature of ActiveMQ not resuming properly
> --
>
> Key: AMQ-6000
> URL: https://issues.apache.org/jira/browse/AMQ-6000
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker, JMX
>Affects Versions: 5.12.0
>Reporter: M Rahimi
>  Labels: features
>
> The problem is that, when you *resume* the message delivery,
> # If there is a message entering the queue: the broker will immediately send 
> the pending messages to the consumer which is totally OK.
> # But if no message _enters_ the queue: the pending messages in the queue 
> will not be sent to the consumers until the expiration checking is performed 
> on the queue (which by default is 30 seconds and can be controlled by the 
> _expireMessagesPeriod_ attribute) and non-expired messages will be sent to 
> the consumers afterwards.
> Obviously we can change the _expireMessagesPeriod_ to limit this delay, but 
> when you need a milisec precision, performing the expiration check every 
> milisec will not make sense.
> How is it possible to force the queue to start sending messages immediately 
> after resumption?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)