activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-3314) FilePendingMessageCursor isFull reports full in error when temp store is full, even if not needing the temp store
Date Tue, 10 May 2011 17:18:47 GMT

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

Gary Tully resolved AMQ-3314.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0

fix in http://svn.apache.org/viewvc?rev=1101544&view=rev

> FilePendingMessageCursor isFull reports full in error when temp store is full, even if
not needing the temp store
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3314
>                 URL: https://issues.apache.org/jira/browse/AMQ-3314
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: block, cursor, memory, temp, topic, usage
>             Fix For: 5.6.0
>
>
> With slow queue consumers of non persistent messages the temp store can be filled and
producers blocked. The default cursor for non persistent is a fileCursor. 
> However topic subs with a pending message limit strategy also use a cursor for pending
messages. If there is sufficient memory resources, the topic consumers should be able to operate
without recourse to the temp store. At the moment this is not the case, as the check to isFull
reports true in error (based on the status of the temp store)
> It should only report full if its memory is exhausted || it is spooling to disk AND the
temp store is exhausted.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message