[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Updated: (AMQ-1920) MessageAvailableListener doesn't work
From:       "James Strachan (JIRA)" <jira () apache ! org>
Date:       2008-08-29 12:26:52
Message-ID: 875786410.1220012812592.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

James Strachan updated AMQ-1920:
--------------------------------

    Priority: Minor  (was: Critical)

downgraded from critical as this discusses a rare-case optimisation to try avoid \
using a blocking thread when using zero prefetch - an easy workaround is to use \
prefetch of 1 or just use a blocking thread with prefetch of zero

> MessageAvailableListener doesn't work with prefetchSize set to zero
> -------------------------------------------------------------------
> 
> Key: AMQ-1920
> URL: https://issues.apache.org/activemq/browse/AMQ-1920
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.1.1, 5.1.0
> Environment: Broker running ActiveMQ 4.1.1
> Client/Consumer tested with AMQ 4.1.1 and 5.1.0
> Reporter: Sebastian Riedel
> Priority: Minor
> Fix For: 4.1.1, 5.1.0
> 
> 
> The MessageAvailableListener doesn't trigger his event, when prefetchSize is set to \
> zero, although messages are in queue (but because of prefetchSize = zero not \
> dispatched). I understand why the complete asynchronous MessageListener is not \
> allowed to be used with prefetchSize of zero, but in my opinion the \
> AvailableListener should work. Since there is no other possibilty to check for the \
> availability of a new message ( the Queuebrowser is for this aim to slow, because \
> it produces massive traffic) this is a critical issue in my case, also because i \
> can't use JMX to determine e.g. the  QueueSize to trigger a MessageAvailableEvent \
> myself.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]