[Netarchivesuite-users] Bug in DeployApplication
Jonas Lindberg Frellesen
jolf at kb.dk
Mon Apr 27 17:20:41 CEST 2009
I have successfully run several different harvests with non-standard jmxUsernames for both the HarvestController and the Monitor.
The problem seem to be a incorrect path to the jmxUsername. The correct path to the jmxUsername for the HarvestController is:
If you want to verify your configuration file use the '-Eyes' argument when running DeployApplication (it means 'Evaluate = yes').
This will notify you of such inconsistency in the settings of your configuration file.
Fra: netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk [mailto:netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk] På vegne af nicolas.giraud at bnf.fr
Sendt: 27. april 2009 13:39
Til: netarchivesuite-users at lists.gforge.statsbiblioteket.dk
Emne: [Netarchivesuite-users] Bug in DeployApplication
I updated the baseline this morning and I noticed that a bug might have been introduced in the DeployApplication. I saw that jmxremote.access is now generated, but jmxremote.password is not anymore generated correctly, it does not append the settings.harvester.harvesting.jmxuserNameanymore, which causes HarvestControllers not to work.
Can you please confirm?
Avant d'imprimer, pensez à l'environnement.
Consider the environment before printing this mail.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NetarchiveSuite-users