You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Richard Bonneau (JIRA)" <ji...@apache.org> on 2010/09/30 22:46:40 UTC
[jira] Updated: (AMQ-2953) Disk limits not observed when memory
limits exceeded for non-persistent messaging
[ https://issues.apache.org/activemq/browse/AMQ-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Bonneau updated AMQ-2953:
---------------------------------
Description:
When producing non-persistent messages and using the <systemUsage> element to specify memory and disk limits,
it appears that after memory limit is reached that staging incoming messages to disk continues to happen even
past the specified disk limit. More specifically if <memoryUsage> limit is exceeded, we see messages being
stored into files labelled as db_<n>.log. However, even when <tempUsage> element specifies a limit on the
disk space to be used, messages continue to be stored there and the limit is not adhered to.
Attaching the configuration file and simply used the producer/consumer programs in the example folder.
Need to have the limit adhered to and then the producer should be held up until disk or memory is freed up
as expected from the description of handling non-persistent messages.
was:
When producing non-persistent messages and using the <systemUsage> element to specify memory and disk limits,
it appears that after memory limit is reached that staging incoming messages to disk continues to happen even
past the specified disk limit. More specifically if <memoryUsage> limit is exceeded, we see messages being
stored into files labelled as db_<n>.log. However, even when <tempUsage> element specifies a limit on the
disk space to be used, messages continue to be stored there and the limit is not adhered to.
Attaching the configuration file and simply used the producer/consumer programs in the example folder.
Need to have the limit adhered to and then the producer should be held up until disk or memory is freed up.
> Disk limits not observed when memory limits exceeded for non-persistent messaging
> ---------------------------------------------------------------------------------
>
> Key: AMQ-2953
> URL: https://issues.apache.org/activemq/browse/AMQ-2953
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.3.2
> Reporter: Richard Bonneau
>
> When producing non-persistent messages and using the <systemUsage> element to specify memory and disk limits,
> it appears that after memory limit is reached that staging incoming messages to disk continues to happen even
> past the specified disk limit. More specifically if <memoryUsage> limit is exceeded, we see messages being
> stored into files labelled as db_<n>.log. However, even when <tempUsage> element specifies a limit on the
> disk space to be used, messages continue to be stored there and the limit is not adhered to.
> Attaching the configuration file and simply used the producer/consumer programs in the example folder.
> Need to have the limit adhered to and then the producer should be held up until disk or memory is freed up
> as expected from the description of handling non-persistent messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.