ActiveMQ is not a database, and its performance is optimized for use cases
where all messages are consumed relatively soon after they're published.
There's nothing that says a message can't be consumed after some period of
time just because the consumer to whom it is destined isn't online.
You can
Hello Tim,
there is no file older than 3 weeks ...
this is the oldest file (12 days old):
-rw-rw-r-- 1 activemq activemq 33584906 Dez 18 15:22 db-484.log
.. and i have never seen an older file than 3 weeks.
Yes, you understood my experiment correctly. I did the experiment after
midnight on a pr
OK, so I want to recap and make sure I've got everything correct. Please
confirm that there's nothing I'm mis-stating.
Your KahaDB data directory contained lots of files that were older than the
age-off interval that all of your producers are using when they produce
messages, which is unexpected
Hi Tim,
I subscribed every queue with a tool, but I used a selector which never
match a message.
=> no changes in den data folder
Than I used a selector which filters unimportant messages.
=> the server removed about 150 files from the data folder.
I think the activemq server works fine and if
Queue browsing just involves HTTP interactions with the Jetty web server,
and can be scripted if the volume of queues makes manual browsing
impossible.
After you browsed those queues, did any of the very old KahaDB data files
get deleted? That's the second question you're trying to answer by
brow
Hi Tim,
there are about 2500 queues and it is not so easy to browse all queues and
unconsumed messages.
I took a look to a lot of queues with unconsumed messages and all messages
has an (valid = future date) expiration date.
Now 561 files / 17,9 GB
regards
Shine
--
View this message in con
I'm looking forward to your answers to the questions I asked this morning,
and to hearing the results of your browsing the queues and inspecting the
oldest messages on each.
Tim
On Wed, Dec 23, 2015 at 6:32 AM, Shine wrote:
> Hi Tim,
>
> the oldest file has the name db-159.log ... created on th
Hi Tim,
the oldest file has the name db-159.log ... created on the 8th of december.
..
regards
Shine
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Need-help-with-a-message-broker-configuration-tp4705074p4705385.html
Sent from the ActiveMQ - User mailing list archive
Hi Tim,
the folder contains 546 files now; folder size: 17,4 GB. ... 2 files removed
and ~ 40 new files since yesterday.
regards
Shine
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Need-help-with-a-message-broker-configuration-tp4705074p4705384.html
Sent from the Act
Which two files were deleted? Not their filenames, but where did they sit
in the overall order?
When you browse the oldest message on each queue that has no consumers,
look to see if the oldest message in each either has no JMSExpiration
header or has one that's further in the future than your ex
Hi Tim,
in the folder are 512 files now ... and the folder size is about 16,5 GB.
in about 4 hours the server removed 2 files and creates 11 new files, so the
folder grows and grows.
regards
Shine
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Need-help-with-a-message
Your original description said that log directory "grows and grows", and
now you're saying "the activemq server removes log files and creates new
files." Which is it? If you're still looking for help, I think you need
to spend a little time describing exactly what you're seeing happen with
that d
Hi Tim,
thanks for you help.
i monitored the kahadb folder for some days. the activemq server removes log
files and creates new files. The folder contains 503 files currently. I
think thats no problem!?
Maybe I browse all 3000 Queues today and take a look at the kahadb folder
again.
regards
Sh
My primary goal in having you browse every queue with unconsumed messages
was to try to force the broker to evaluate whether those messages should be
expired, which would indicate that the problem was simply that the broker
wasn't evaluating message expiration when no consumer was connected. If
th
Hi Tim
i dont browse the queue .. i click on the "Queues" link in the WebConsole to
refresh the list of queues. You see the enqueued messages and the dequeued
messages .. if the time to live of an message is over, than the counter of
the dequeued messages increase and enqueued messages decrease.
For troubleshooting purposes, I'd recommend you use the web console or a
JMX viewer to find out which queues have unconsumed messages and no
consumers, and browse the messages on each such queue via the web console.
Browsing should (I think) run the messages through the expiration logic, so
once yo
Messages published to a topic are deleted from the message store when they
are consumed by the last subscriber. When there are no subscribers, they
are immediately deleted. So there's nothing for you to worry about there.
Tim
On Fri, Dec 18, 2015 at 11:23 AM, Shine wrote:
> Hi Tim.
>
> no que
Hi Tim.
no queue with that name
In the topic Tab is that entry .. SHINE is a queue name
ActiveMQ.Advisory.Expired.Queue.SHINER
Number Of Consumers: 0
Messages Enqueued: 2<= expired Messages ... automatically remove from
queue
Messages Dequeued: 0
.. but i cant remove via WebConsole .. mayb
It would be in the Queues tab, with a name of DeadLetterQueue.
On Fri, Dec 18, 2015 at 10:40 AM, Shine wrote:
> Hi,
>
> i use queues only. Each client has its own queue. It works like a chat, you
> send a message to queue .. if the client is online, it receives the message
> ... if the client is
Hi,
i use queues only. Each client has its own queue. It works like a chat, you
send a message to queue .. if the client is online, it receives the message
... if the client is offline .. maybe 5 days, than the message(s) still in
the queue (max. 2-3 weeks) until the client goes online.
I cant fi
How is it that those messages are not being consumed? Do you have no
consumers on the queue (or an offline durable topic subscriber)? Do you
have consumers, but with selectors that don't hit those messages?
Something else?
I haven't looked in detail at the message expiration code, but I believe
Hi,
is a Multi kahaDB persistence adapter a good way to get the growing of the
KahaDB folder under control?
best regards
Shine
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Need-help-with-a-message-broker-configuration-tp4705074p4705138.html
Sent from the ActiveMQ - U
Here the current configuration ...
any suggestion for improvement?
How many GB diskspace needs a "normal" kahaDB?
http://activemq.apache.org/schema/core";
brokerName="localhost" dataDirectory="${activemq.data}" useJmx="true"
schedulePeriodForDestinationPurge="60" >
Hi Tim,
For problem #1: there are a lot of unconsumed messages, but each message
havs an expiration time (max 2-3 weeks). Over the time the size of the
KahaDB folder should be nearly constant.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Need-help-with-a-message-broke
For problem #1, do you have any old but unconsumed messages? KahaDB can't
compact its journal files, so a single old message that can't be deleted
can cause KahaDB to keep a large number of files.
For problem #2, why is that a problem? You haven't said anything that
indicates that those advisory
25 matches
Mail list logo
