Sorry for the delay getting back to you.
I'm not clear what delay error messages you're referring to; if you're
still having problems related to them, can you include a sample to help
clarify what you mean?
I got the 70GB by multiplying your 70% JVM percentage by your 100GB store
limit instead of
On 14-12-08 08:57 PM, Tim Bain wrote:
The log line tells you how you're doing against two different limits: the
per-destination limit and the entire-broker limit. The per-destination
limit is first, and the log line says you're using 0% of what you've
allocated per destination, so you're right t
age=0%, usage=0, limit=720791142,
> percentUsageMinDelta=1%;Parent:Usage(default:memory)
> percentUsage=104%, usage=752535801, limit=720791142,
> percentUsageMinDelta=1%: Usage Manager Memory Limit reached. Producer
> (ID:pan-51744-1418069977147-2:2:-1:1) stopped to prevent floodin
queue://hf.response:memory) percentUsage=0%,
usage=0, limit=720791142,
percentUsageMinDelta=1%;Parent:Usage(default:memory) percentUsage=104%,
usage=752535801, limit=720791142, percentUsageMinDelta=1%: Usage Manager
Memory Limit reached. Producer (ID:pan-51744-1418069977147-2:2:-1:1)
stopped to prevent flo
Angelovich wrote:
> We just ran into the warning below indicating that we've exceeded the memory
> available on a Topic.
>
> WARNING: Async error occurred: javax.jms.ResourceAllocationException: Usage
> Manager memory limit reached. Stopping producer
> (ID:hoeplx3764-3410
This should really be a new thread.
take a look at http://activemq.apache.org/message-cursors.html
you have producer flow control set to true, so your producers will be
throttled if there is no space available. using message cursors, you can get
the messages spooled to disk so the slowest consume
We just ran into the warning below indicating that we've exceeded the memory
available on a Topic.
WARNING: Async error occurred: javax.jms.ResourceAllocationException: Usage
Manager memory limit reached. Stopping producer
(ID:hoeplx3764-34102-1345832926291-0:2:2:1) to prevent flooding
Hi,
did you also increase the -XmX parameter in the activemq startup script?
This can also be due to a problem in the client implementation - i.e.
transaction handling.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Usage-Manager-memory-limit-reached-tp4557657p4561328
used?
-
Michael Hayes B.Sc. (NUI), M.Sc. (DCU), SCSA SCNA
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Usage-Manager-memory-limit-reached-tp4557657p4561278.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
;test");
Also, is there a way to have a non durable topic.Even if a durable consumer
tried to subscribe to this topic, the topic itself should discard it.
Thanks,
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Getting-Usage-Manager-Memory-Limit-reached-message-on
> From: manua [mailto:agarwal.m...@gmail.com]
> Sent: 20 April 2011 20:40
> To: users@activemq.apache.org
> Subject: Getting Usage Manager Memory Limit reached message on the
> topic
>
> HI,
>
> I have a topic on which millions of messages are published and there
> was no
> sub
the past the same topic has handled much more messages than
today.Only difference there was no subscriber in the past.
What could be the reason for this.
Thanks,
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Getting-Usage-Manager-Memory-Limit-reached-message-on-the
I have a stomp client that is writing persistent messages (message size
varies from 300 bytes to 2000 bytes) to AMQ.
After around 40-45K messages on the AMQ and no consumers, AMQ gives the
following warning message:
Usage Manager memory limit reached on queue://foo.bar. Producers will be
/topics/etc...) at some stage and you could get a OOM.
Cheers,
Felix
-
Felix Ehm,
www.cern.ch
--
View this message in context:
http://old.nabble.com/Usage-Manager-memory-limit-reached-for-topic.-Producer-hangs-tp26478478p26492167.html
Sent from the ActiveMQ - User mailing list archive at
cSend
- no producerFlowControl configuration
- memoryUsage limit=4gb
- tempUsage limit=2gb
- -Xmx4gb with 64-bit JVM on Windows 2008
MemoryPercentUsage is constantly below 1, but all of a sudden I get a "Usage
Manager memory limit reached for topic", and the producer hangs.
15 matches
Mail list logo