Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NullPointerException for RemoteResourceIndex #193

Closed
PsypherPunk opened this issue Jan 2, 2015 · 3 comments
Closed

NullPointerException for RemoteResourceIndex #193

PsypherPunk opened this issue Jan 2, 2015 · 3 comments
Assignees
Labels

Comments

@PsypherPunk
Copy link
Contributor

We've configured a RemoteResourceIndex as follows (in CDXCollection.xml):

<property name="resourceIndex">
    <bean class="org.archive.wayback.resourceindex.RemoteResourceIndex">
        <property name="searchUrlBase" value="http://___.bl.uk:8080/wayback/xmlquery" />
    </bean>
</property>

This correctly returns results (i.e. the calendar is correctly displayed when searching) but when trying to view a resource, a NullPointerException is thrown:

WARNING: Runtime Error
  java.lang.NullPointerException
    at org.archive.wayback.replay.DateRedirectingClosestResultSelector.getClosest(DateRedirectingClosestResultSelector.java:40)
    at org.archive.wayback.replay.SelectorReplayDispatcher.getClosest(SelectorReplayDispatcher.java:71)
    at org.archive.wayback.webapp.AccessPoint.handleReplay(AccessPoint.java:677)
    at org.archive.wayback.webapp.AccessPoint.handleRequest(AccessPoint.java:311)

This seems to be correct as the closest result in the CaptureSearchResults never gets set.

@PsypherPunk PsypherPunk added the bug label Jan 2, 2015
PsypherPunk added a commit to ukwa/openwayback that referenced this issue Jan 2, 2015
PsypherPunk added a commit to ukwa/openwayback that referenced this issue Jan 2, 2015
@PsypherPunk
Copy link
Contributor Author

Tried to fix this in #194—the LocalResourceIndex uses a ClosestResultTrackingFilter which annotates the results and marks the closest. I've tried to duplicate that process here.

@PsypherPunk PsypherPunk added this to the 2.0.1 Bugfix Release milestone Jan 13, 2015
@PsypherPunk PsypherPunk self-assigned this Jan 13, 2015
@anjackson
Copy link
Member

Okay to close this?

@PsypherPunk
Copy link
Contributor Author

Yep, fixed in #194.

kngenie added a commit to kngenie/wayback that referenced this issue Feb 14, 2020
still larger buffer for instagram js character set detection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants