poi-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Micich <josh.mic...@gmail.com>
Subject Re: Workbook problems with POI. Exceptions thrown during load
Date Wed, 21 Jan 2009 21:56:13 GMT
Hello Zach,

The "Cannot remove block" errors you are getting look a lot like this
previously fixed bug:
https://issues.apache.org/bugzilla/show_bug.cgi?id=44898

However, I notice that the error message you are getting is from after this
change:
http://svn.apache.org/viewvc?view=rev&revision=653945
And the full fix was very soon after that:
http://svn.apache.org/viewvc?view=rev&revision=658285

POI version 3.1-beta2 came out between these two revisions, so if you have
that version, the fix might be a simple matter of upgrading.

I searched for the message "Unable to process excel record that is larger
than 8224 bytes" in the POI source (and also in 3.0 and 3.1), but I could
not find it.  I can find the other messages "Unable to construct record
instance" - RecordFactory.java:236 and "The content of an excel record
cannot exceed 8224 bytes" - RecordInputStream.java:169, but there is really
not enough information to work on here.  There have been changes in this
area of POI, and the fact that your error message is not present in the
source suggests that those changes might be related to the bug you are
seeing.

I'm guessing that the pairs of messages with the second line indented are
due to nesting of exceptions.  It would be more helpful if the stack trace
frames were included (from the first POI frame onward - your code's frames
can be omitted).

Try a recent POI 3.5beta build (http://encore.torchbox.com/poi-svn-build/).
If the problems are still present, we'll probably need much more than just
stack traces to diagnose them.  For "larger than 8224 bytes" problem, it may
be enough to supply a hex dump of the offending record (and one or two prior
records).  For the "Cannot remove block" problem, the whole file may be
required, but removing private data will probably make the error go away
(because Excel often automatically fixes abnormal file structures).  You may
be stuck with doing all the debugging yourself.


regards,
Josh

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message