[Netarchivesuite-users] Error creating singleton of class 'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
sara.aubry at bnf.fr
sara.aubry at bnf.fr
Mon Feb 15 10:24:13 CET 2010
Hi Bjarne,
We are using version 3.10.1.
And yes they all failed this morning between 6:35 and 7:07.
Sara
Message de : Bjarne Andersen <bja at statsbiblioteket.dk>
15/02/2010 10:18
Envoyé par :
<netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk>
Veuillez répondre à
<netarchivesuite-users at lists.gforge.statsbiblioteket.dk>
Pour
"netarchivesuite-users at lists.gforge.statsbiblioteket.dk"
<netarchivesuite-users at lists.gforge.statsbiblioteket.dk>
Copie
Objet
Re: [Netarchivesuite-users] Error creating singleton of class
'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
Which version of NS are you running? I think there was a previous bug in
the heritrix integration that could have a harvester instance grab jobs
from the queue and imediately fail them.
Did all your jobs fail in a short time?
Best
bjarne
Sent fra min HTC Touch Pro
----- Oprindelig meddelelse -----
Fra: Jonas Lindberg Frellesen <jolf at kb.dk>
Sendt: 15. februar 2010 10:14
Til: netarchivesuite-users at lists.gforge.statsbiblioteket.dk
<netarchivesuite-users at lists.gforge.statsbiblioteket.dk>
Emne: Re: [Netarchivesuite-users] Error creating singleton of class
'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
Hi Sara
The cause of the error can be found in this line:
Caused by: dk.netarkivet.common.exceptions.IOFailure: Port 8070 already in
use, or port is out of range
It means that another application on the same machine is using the port
8070, and the application you are looking at can therefore not use the
same port as the other application.
You can solve this problem by assigning an unused port to the application
instead of 8070.
I cannot see exactly which port setting it is taking about, but it can
only be one of the following:
settings.common.jmx.port
settings.common.jmx.rmiPort
settings.harvester.harvesting.heritrix.guiPort
settings.harvester.harvesting.heritrix.jmxPort
You can find them in the settings file for the application, or perhaps the
deploy configuration file.
All of these port have to be unique and unused by other applications.
Best regards,
Jonas
-----Oprindelig meddelelse-----
Fra: netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk
[mailto:netarchivesuite-users-bounces at lists.gforge.statsbiblioteket.dk] På
vegne af sara.aubry at bnf.fr
Sendt: 15. februar 2010 09:39
Til: netarchivesuite-users at lists.gforge.statsbiblioteket.dk
Emne: [Netarchivesuite-users] Error creating singleton of class
'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
Hello Everyone,
We are still running a large test crawl at BnF.
Everything went well last week, and just coming back from weekend, I have
361 jobs that failed due to this reason :
Error creating singleton of class
'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
Do you know what could have caused this error ?
Thanks in advance!
Sara
--------------------------
Here is the long stack :
dk.netarkivet.common.exceptions.ArgumentNotValid: Error creating singleton
of class 'dk.netarkivet.harvester.harvesting.JMXHeritrixController':
at
dk.netarkivet.common.utils.SettingsFactory.getInstance(SettingsFactory.java:94)
at
dk.netarkivet.harvester.harvesting.HeritrixControllerFactory.getDefaultHeritrixController(HeritrixControllerFactory.java:54)
at
dk.netarkivet.harvester.harvesting.HeritrixLauncher.doCrawl(HeritrixLauncher.java:200)
at
dk.netarkivet.harvester.harvesting.HarvestController.runHarvest(HarvestController.java:236)
at
dk.netarkivet.harvester.harvesting.distribute.HarvestControllerServer$HarvesterThread.run(HarvestControllerServer.java:650)
Caused by: dk.netarkivet.common.exceptions.IOFailure: Port 8070 already in
use, or port is out of range
at
dk.netarkivet.common.utils.SystemUtils.checkPortNotUsed(SystemUtils.java:91)
at
dk.netarkivet.harvester.harvesting.JMXHeritrixController.<init>(JMXHeritrixController.java:237)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
dk.netarkivet.common.utils.SettingsFactory.getInstance(SettingsFactory.java:92)
... 4 more
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at
java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:141)
at
dk.netarkivet.common.utils.SystemUtils.checkPortNotUsed(SystemUtils.java:88)
... 10 more
Avant d'imprimer, pensez ? l'environnement.
Consider the environment before printing this mail.
_______________________________________________
NetarchiveSuite-users mailing list
NetarchiveSuite-users at lists.gforge.statsbiblioteket.dk
https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users
_______________________________________________
NetarchiveSuite-users mailing list
NetarchiveSuite-users at lists.gforge.statsbiblioteket.dk
https://lists.gforge.statsbiblioteket.dk/mailman/listinfo/netarchivesuite-users
Avant d'imprimer, pensez à l'environnement.
Consider the environment before printing this mail.
More information about the NetarchiveSuite-users
mailing list