[Netarchivesuite-users] The message limit (maxNumMsgs) of 100000 has been reached

[aponb at gmx.at]

I did read that in the follow up of Bug 1275, but currently we are still 
in the first stage of our domain crawl and I can't change my deployed 
version (3.8.1). But after that we will switch to the latest version.
Yes, I would like to have a copy of that script, as it would be very 
useful for us.
Thanks again for your help
a.
> The current latest stable version (3.8.2) handles some auto-reconnection to the JMS-broker in case of lost connection - but the next stable version should handle such error scenarios much more smoothly. So even a restart of the JMS-broker would make applications auto-reconnect - a scenario that the current version does not fully or always support.
>
> I could say that in Netarchive.dk we have set up a number of very small cronjobs to check different aspects of the JMS-queues
>  - number of listeners on different queues (e.g. number of bitarchive-machines listening, number of listeners on HIGH_PRIORITY harvester queues (must not be 0) - etc. )
>  - number of messages in different queues (e.g. number of messages on the MONITOR_QUEUE should not exeed 5000 messages)
>
> The script counts the expected number of different things from the deploy-xml-file so that we dynamically always e.g. check for the right number of expected bitarchive machines.
>
> If you like a copy of this script I can mail it to you.
>
> -
> Bjarne
> ________________________________________
> Fra: netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk <https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users> [netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk <https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users>] På vegne af aponb at gmx.at <https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users> [aponb at gmx.at <https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users>]
> Sendt: 16. september 2009 08:49
> Til: NetarchiveSuite-users
> Emne: Re: [Netarchivesuite-users] The message limit (maxNumMsgs) of     100000 has been reached
>
> Thanks for your reply!
> I did restart the broker. After that the messages in queue
> ONB_COMMON_MONITOR was empty.
> After that I had to restart all Harvester-Instances because they didn't
> get new scheduled jobs.
> What I tried before restarting the broker was to inspect the queue, but
> without success. With which tool are you doing this? imqcmd doesn't
> offer this possibilty. Probably this has to be done with an own written
> code. The question for me is now, is it normal to get to limit of the
> maximal number of message in the Monitor Queue and should it be a normal
> process to delete this queue?
>
> Thanks for your help
> a.