[Netarchivesuite-users] JMS-Queues
Bjarne Andersen
bja at statsbiblioteket.dk
Tue Sep 22 22:42:56 CEST 2009
Does imqcmd command for listing numbers of messages, producers, consumers on each queue tell you that there is one (and exactly one) consumer on the COMMON_MONITOR queue ? - the GUIApplication should take messages from that queue all the time meaning that number of messages should not grow. If GUIApplication stopped listening on that queue number of messages will off cause grow.
I only think we experienced problems with that queue very few times when the server running the GUIApplication got very busy and couldn't really cope with keeping up taking messages of the queue. Is your server over loaded when this happens ?
That specific queue is used by all other applications to tell the monitoring system: "I want to be monitored" - you can configure how often each application should send this message - and maybe you could try to raise the setting (I recall it's set as Number Of Seconds between each message about "I want monitoring").
best
Bjarne
________________________________________
Fra: netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk [netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk] På vegne af aponb at gmx.at [aponb at gmx.at]
Sendt: 21. september 2009 15:26
Til: NetarchiveSuite-users
Emne: [Netarchivesuite-users] JMS-Queues
After having Troubles with my JMS-Queue, the Netarchive-Suite couldn't
complete recover. All the harvester-Instances could reconnect and also
it seemed that the Administration Applications could reconnect, because
new Jobs were scheduled but without receiving statistical information
from the completed jobs. That is not really a desired behavior. We
decided to start over again with NAS 3.8.2, which is running since
Wednesday. Now we try to monitor the JMS-Queues, and I already received
a nice script from Bjarne. I also tried out imqadmin which shows all my
Queues and Properties. But I can't inspect the single messages with that
tool. Have I missed something?
And the monitoring also tells us that we have already 5803 messages int
the COMMON_MONITOR queue, get more and more. As Bjarne has written, that
is not normal. At the end of last week I made the expierience that the
queue, which contained already about 500 messages, at a certain point
started to have fewer messages. So that seemed to me normal. But now it
is getting more and more. First of all I would like to know if I could
just clear that queue with the imqadmin tool with Actions->Purge
messages? Would that be the right way to clear the messages? How is NAS
reacting, if there are no more messages in that queue, which should be
deleted by the application? I don't want to have NAS in trouble with the
JMS-Broker, when reaching the 100000 messages limit. And finally the
question what is wrong with my installation when my queue contains that
many messages, if that is not normal?
Thanks for your time
a.
_______________________________________________
NetarchiveSuite-users mailing list
NetarchiveSuite-users at lists.gforge.statsbiblioteket.dk
https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users
More information about the NetarchiveSuite-users
mailing list