On 17 February 2010 16:51, Mats Henrikson wrote:
> When set the broker will just freeze after some number of messages,
> and using JMX/JConsole the queue now doesn't render its attributes,
> you can't connect a consumer etc.
I have logged this bug for this problem:
https://issues.apache.org/acti
Hi Gary,
I checked out your test case and seeing that that worked fine set out
to figure out why my test case didn't.
As it turns out it is because of my :
n(e);
>>>> >>}
>>>> >>
>>>> >>
>>>> >>
>>>> >> Here is a Producer:
>>>> >>
>>>> >> public class Producer implements Runnable{
>>>> >>
>>>> >&
; >> message.writeBytes(new
>>> >>
>>> >>
>>> byte[]{0,0,0,66,0,0,0,5,0,0,0,0,0,0,0,3,0,0,0,49,51,49,51,51,53,53,48,51,51,54,0,0,0,49,50,51,52,53,0,0,0,0,0,0,0,0,0,0,17,116,114,97,99,101,32,109,101,32,112,108,101,97,115,101,32,
MessageProducer producer =
>> >> session.createProducer(destination);
>> >> producer.setDeliveryMode(DeliveryMode.PERSISTENT);
>> >>BytesMessage message = session.createBytesMessage();
>> >>message.writeB
2,50,});
> >>try {
> >>producer.send(message);
> >> } catch (ResourceAllocationException e) {
> >> e.printStackTrace();
> >>}
> >>session.close
Gary,
I've been trying to do pretty much the same thing that Scott is trying
to do, and I can't get it to work either - no matter what I do I seem
to be able to blow the broker up with an OOME.
What I want to do is configure my broker so that it becomes impossible
to run it out of memory or lock
Hi Scott,
>> >
>> > just change the below config to enable flow control - i.e:
>> >
>> >
>> >
>> >
>> > in 5.3 - producerFlowControl is on by default - so just remove the
>> > producerFlowControl entry from your configuration.
>&g
to grow without surpassing the
> >> memory
> >> setting? I am trying to figure out how to do the same thing.
> >>
> >> -Scot
> >>
> >>
> >> Fred Moore-3 wrote:
> >>>
> >>> Hi,
> >>>
> >>&
gt;> ...
>>>
>>> ...can anyone shed some light on the actual role of memoryLimit in:
>>> >> memoryLimit="1mb">
>>> >> memoryLimit="1mb">
>>>
>>> ...moreover: *when* will producerFlowContr
F.
--
View this message in context:
http://old.nabble.com/How-to-configure-5.3-broker-over-KahaDB-to-support-lots-of-unconsumed--persistent-msgs--tp27277849p27569119.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http
ht on the actual role of memoryLimit in:
>
>
>
> ...moreover: *when* will producerFlowControl start slowing down consumers?
>
> Cheers,
> F.
>
>
--
View this message in context:
http://old.nabble.com/How-to-configure-5.3-broker-over-KahaDB-to-support-lots-of-un
ontext:
http://old.nabble.com/How-to-configure-5.3-broker-over-KahaDB-to-support-lots-of-unconsumed--persistent-msgs--tp27277849p27569119.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
the memory limit puts a cap on the amount of memory a given destination can
consume. If 70% of that limit is reached, message enqueue blocks pending
release of some memory. If producerFlowControl is enabled, producers are
blocked pending some memory release.
The difference between the queue blockin
Hi,
going back to Cursors and
http://activemq.apache.org/how-do-i-configure-activemq-to-hold-100s-of-millions-of-queue-messages-.html
...
...can anyone shed some light on the actual role of memoryLimit in:
...moreover: *when* will producerFlowControl start slowing down consumers?
Cheers
nts are similar.
--
View this message in context:
http://old.nabble.com/How-to-configure-5.3-broker-over-KahaDB-to-support-lots-of-unconsumed--persistent-msgs--tp27277849p27277999.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi folks,
we have a 5.3 embedded KahaDB based broker with just a VM connector on it
(see activemq.xml here http://pastebin.com/f492ec856), our producers
continuously send persistent messages while the consumers run intermittently
(because they are bound to the availability of an external
and inter
17 matches
Mail list logo
