JHOVE

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

The issue of why it sees a bad object number still isn't resolved, but I'll
close this for JHOVE 1.5, since at least the reported bug has been fixed.

What's happening is that a bad object number is being read and then indexed
into an array. I've added bounds checking, so that JHOVE will report the
file as not well-formed and give an appropriate error message; users can
grab the latest PDFModule.java and compile it in their build.

But since I can open the file in Acrobat, I suspect that the PDF module is
doing something else wrong that's causing it to get the bad object number
in the first place, so until I've done more checking I'll leave this bug
open.