Hi,

your producers are slowed down on memory limit reached, not store
limits. See http://activemq.apache.org/producer-flow-control.html for
more information.


Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net



On Wed, Oct 6, 2010 at 3:40 AM, tmane <tm...@stubhub.com> wrote:
>
>
>
> Hi ,
>
>
> Active Mq version :  activemq-all-5.3.0.4
> Operating system: Linux
> Java version :6
> Usage: Queues using persistent messages.
>
> Configuration:
>
>        <!--  The maximum about of space the broker will use before slowing
> down producers -->
>        <systemUsage>
>            <systemUsage sendFailIfNoSpace="true">
>                <memoryUsage>
>                    <memoryUsage limit="800 mb"/>
>                </memoryUsage>
>                <storeUsage>
>                    <!-- create a bean for persistence adapter so that it
> can be reffered to by system usage -->
>                    <storeUsage limit="2 gb" name="foo" store="#store"/>
>                </storeUsage>
>                <tempUsage>
>                    <tempUsage limit="2 gb"/>
>                </tempUsage>
>            </systemUsage>
>        </systemUsage>
>
> Persistance Adaptor has maxFileLength="20 mb" (total data store is 2gb)
>
> Messages are also not too bulky its simple concatenated string of few
> variables.
>
> Seeing this exceptions on producer send:
> org.springframework.jms.ResourceAllocationException: SystemUsage memory
> limit reached; nested exception is javax.jms.ResourceAllocationException:
> SystemUsage memory limit reached
>
> Issue:
> Currently we have a setup where we have very fast producers and slow
> consumers.As per expectation broker is trying to slow down the producer by
> sending out a JMSException as above.
> When this exceptions are happening data store which has 2gb of space is
> still having enough space,also other queues on this broker continue to work
> fine.
>
> I am trying to understand when broker is slowing down producer which space
> its looking at to determine that its out of memory limit.
>
> Any knowledge sharing on this is much appreciated.
>
> Thanks in advace.
> -tm
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/javax-jms-ResourceAllocationException-SystemUsage-memory-limit-reached-Need-to-understand-concept-tp2957136p2957136.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Reply via email to