Uploaded image for project: 'NetarchiveSuite'
  1. NetarchiveSuite
  2. NAS-1929

BnfHeritrixController does not handle shutdown of Heritrix instance properly

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 3.18.0, I49
    • 3.16.1, 3.17.0
    • None
    • None
    • SB/KB
    • Uncertain
    • Hide

      1) Install netarchiveSuite and deploy.
      2) Make sure, that only one snapshot-harvestserver is running (kill the others).
      3) Go to the install-directory for the remaining snapshot-harvestserver, and change the common.jmx.timeout to 90 secs.
      4) Restart this harvest-server.
      5) Define a rather large snapshot harvest (20 domains, 100 Mbytes), so you have time to logon to the heritrix gui, and shutdown the heritrix instance prematurely - this could also be done by using the kill command from the command-line.
      6) The harvestserver should soon realise that the heritrix has died, and continue with the post-processing.
      7) define and activate a small snapshot-harvest (20 domains, 1Mbytes)
      8) The snapshot-server should receive this job, and complete it as normal.

      Show
      1) Install netarchiveSuite and deploy. 2) Make sure, that only one snapshot-harvestserver is running (kill the others). 3) Go to the install-directory for the remaining snapshot-harvestserver, and change the common.jmx.timeout to 90 secs. 4) Restart this harvest-server. 5) Define a rather large snapshot harvest (20 domains, 100 Mbytes), so you have time to logon to the heritrix gui, and shutdown the heritrix instance prematurely - this could also be done by using the kill command from the command-line. 6) The harvestserver should soon realise that the heritrix has died, and continue with the post-processing. 7) define and activate a small snapshot-harvest (20 domains, 1Mbytes) 8) The snapshot-server should receive this job, and complete it as normal.

    Description

      Aug 18, 2011 3:08:58 PM dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController closeJMXConnection
SEVERE: JMX error while closing connection to Heritrix
java.rmi.ConnectException: Connection refused to host: 130.226.228.7; nested exception is: 
	java.net.ConnectException: Connection refused
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)

	at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
	at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
	at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
	at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
	at javax.management.remote.rmi.RMIConnectionImpl_Stub.close(Unknown Source)
	at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:466)
	at javax.management.remote.rmi.RMIConnector.close(RMIConnector.java:406)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.closeJMXConnection(BnfHeritrixController.java:842)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.getMBeanServerConnection(BnfHeritrixController.java:867)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.jmxCall(BnfHeritrixController.java:776)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.getAttributes(BnfHeritrixController.java:738)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.getMBeanAttributes(BnfHeritrixController.java:685)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixController.getCrawlProgress(BnfHeritrixController.java:350)
	at dk.netarkivet.harvester.harvesting.controller.BnfHeritrixLauncher$CrawlControl.run(BnfHeritrixLauncher.java:66)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
	at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
	at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.ConnectException: Connection refused
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
	at java.net.Socket.connect(Socket.java:519)
	at java.net.Socket.connect(Socket.java:469)
	at java.net.Socket.<init>(Socket.java:366)
	at java.net.Socket.<init>(Socket.java:180)
	at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
	at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
	at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
	... 23 more

      Attachments

        Activity

          People

            svc Søren Vejrup Carlsen (Inactive)
            svc Søren Vejrup Carlsen (Inactive)
            Mikis Seth Sørensen Mikis Seth Sørensen (Inactive)
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 7h
                7h
                Remaining:
                Time Spent - 1h Remaining Estimate - 6h
                6h
                Logged:
                Time Spent - 1h Remaining Estimate - 6h
                1h