If only the index files are stale you can try to remove all index files
(*.data) and restart the broker to rebuild the index.
The broker will get stopped when IO exception occurs so new messages are
unable to enqueue the broker in fact.
At 2013-03-10 00:59:13,jcamus wrote:
>Thanks for your answe
Yes, you can assume that works.
It seems you want your message flow to be split into two message flows, one
for
the lower priority messages while the other for the higher priority
messages
and you want they are stuck on two 'exclusive' consumers respectively.
For the sparse selector In one word ,
The non-durable retroactive consumer of Topic will do the trick.
http://activemq.apache.org/retroactive-consumer.html
Only one condition is not satisfied,messages can not survive from the
restart of the broker.
2013/5/2 Andrea Arcuri
> Hi,
> I am new to ActiveMQ. Reading documentation and pla
+1
2013/5/7 Yi Pan
> Hi, Christian,
>
> Thanks for the quick response. However, the stats and its explanation is
> still very confusing to me.
>
> The standard explanation of Enqueue Count - the total number of messages
> sent to the queue since the last restart. That's counting the action of
>
haha!
在 2013-9-9 下午9:39，"HellKnight" 写道：
> I feel a little shamed...The problem is actually simple : I am using async
> sending , but I did not register any exception listener for the connection
> I
> used
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Is-there-
Pure master/slave is departed in later releases and wont get supported any
more.
You should consider other cluster topology.
2013/12/3 赵振华 ZhenhuaZhao
> hi,all
> I’m a newbie in activemq.
>I use active-5.5.5 on rhel5.4 X86_64 in pure master/slave mode.
> I leave master’s config
NoSpaceException is also a response come from broker.
when asyn send is used,client will not expect response for request.
You can try to use non-transactional session or enforce sync send and that
should work.
2014-02-20 7:04 GMT+08:00 Gary Tully :
> It looks like you are using async send so th
What's message ack mode you're using?
If your consumer does not acknowledge messages that have been processed,
eg, you may forget to manual ack message when using client ack mode or
forget to commit session when using transaction,
those messages will be redelivered when consumer or broker gets rest
It's hard to enumerate differences between them, even for developers.
You'd better to create a similar test case to see what's up inside broker,
here are some examples,
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob_plain;f=activemq-core/src/test/java/org/apache/activemq/transport/di
Yes,that help performance but once broker gets restarted,it will take
longer time to complete index recovery.
Here is a guide that may help you to tune performance,
https://access.redhat.com/site/documentation/en-US/JBoss_A-MQ/6.0/html/Tuning_Guide/files/PersTuning-KahaDB.html
2014-02-13 19:49 GM
Seems what you really want to solve is to distribute real task messages
evenly between consumers.
As default a consumer has a prefetch to allow broker to push messages to it
in batch manner,
if a consumer is slow to process message then many pending messages will be
accumulated
and other consumers
BTW,AUTO_ACKNOWLEDGE can not guarantee once and only once semantic since
the ack is sent async.
You can image such a case when your consumer has succeeded in processing a
message
while the consumer application is crashed before the ack is sent, you will
receive that message again if your applicatio
Can you try to disable cache consumer option?
Or can you use a plain jms consumer to try to reproduce the issue?
Just guess it's maybe related with cache consumer and spring jms template.
2014-03-29 4:19 GMT+08:00 lookers :
> Just checked the queuesize and it is increasing when it is blocked.
>
If you have existing messages in the broker and add consumers at a later
stage, it is a good idea to delay message dispatch start until all
consumers are present (or at least to give enough time for them to
subscribe). If you don't do that the first consumer will probably acquire
all message groups
14 matches
Mail list logo
