Details
-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: Link Score Report
-
Fix Version/s: None
-
Component/s: Linking Report
-
Labels:None
-
Environment:
production
Description
Production Report ID: 337 - Ted ran a report in production that encountered a failure when attempting to connect to the STAT API. From the log file:
2011-02-17 11:21:38,323 INFO [com.thesearchagency.service.linkscore.util.manager.LinkScoreReportWorkerStatusManager] (http-0.0.0.0-8080-2) Link Targets Processed: 9770 out of 9795.
2011-02-17 11:21:41,764 INFO [com.thesearchagency.service.linkscore.worker.linkscape.LinkScapeWorker] (WorkManager(2)-52) LSR ID: 337 - Count of URLs sent to Linkscape API: 8137
2011-02-17 11:21:41,808 INFO [com.thesearchagency.service.linkscore.worker.stat.StatAPI] (WorkManager(2)-71) Connection URL:http://tsa.getst.at/api/v2/0fa96b714e406a43203a297c78141f743c895396/pagerank/new
2011-02-17 11:21:41,845 INFO [com.thesearchagency.service.linkscore.worker.linkscape.LinkScapeURLMetricsAPI] (WorkManager(2)-52) Connection URL:http://lsapi.seomoz.com/linkscape/url-metrics?AccessID=member-82d81ceb44&Expires=1297970801&Signature=eMbrP7cYyArxoav3%2FSLEzWxgAJ0%3D&Cols=103617121508
2011-02-17 11:21:42,305 ERROR [com.thesearchagency.service.linkscore.worker.stat.StatAPI] (WorkManager(2)-71) STAT api connection attempt 1 failed: java.io.IOException: Server returned HTTP response code: 500 for URL: http://tsa.getst.at/api/v2/0fa96b714e406a43203a297c78141f743c895396/pagerank/new
2011-02-17 11:21:42,305 ERROR [com.thesearchagency.service.linkscore.worker.stat.StatWorker] (WorkManager(2)-71) LSR ID: 337 - StatWorker.process encountered a failure::null
2011-02-17 11:21:42,313 INFO [com.thesearchagency.service.linkscore.worker.stat.StatWorker] (WorkManager(2)-71) LSR ID: 337 - StatWorker.process complete.
Apparently, at the time of accessing the STAT API, the STAT service may have been down.
The problem here is that the failure did not get handled appropriately by indicating with a status of yellow. The fix will require taking a look at the failure flow in this case and figuring out how to update the status of this report worker.