Bugzilla – Full Text Bug Listing
| Summary: | NullPointerException while crawling in the wild | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | nils.thieme |
| Component: | Smila | Assignee: | Project Inbox <smila.irms-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | daniel.stucky |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Hi Nils, thanks for your bug report. What exactly do you mean with "crawling in the wild" ? Do you have a sample URL that produces the described behavior and returns a HTTP status code 204 so that I can add a JUnit test ? Anyway, I took a look at the code and added a check if the InputStream is null. This should prevent the NullPointerException to happend. Bye, Daniel "Crawling in the wild" means start crawling from some random seeds and then crawl the web, not a specific web site or topic. Unfortunately I have no url for your :-(. But if one appears I will sent it to you. Thanks for fixing :-). Closing this one since the problem cannot be reproduced. Closing this |
A NullPointerException occurs in the Class "HttpResponse" when crawling in the wild. The error line is 116. It is because the variable "in" is null and access on it occurs. The reason for this is the answer from the server. The answer code is 204 ("No Content"). So the client can't read in content.