ok - I'm not sure about the best way to proceed. We do a tremendous amount of high volume processing of very large files in many hundreds of different environments, and have not run into this, so this would seem to point at the problem being caused be a very unusual corner case. Having something fail in production but not in development is, of course, difficult.
Is your development JVM the same version and bitness as the production server? I can't imagine that would make a difference, but who knows. If you are willing to add logging to an itext jar and deploy it to that server we can possibly get more detailed information about exactly where the failure is coming from - chances are nearly 100% that it's happening in MappedChannelRandomAccessSource.open(), though. Do you have any comments on my assertion that the problem PDF itself is partially corrupted? -- View this message in context: http://itext-general.2136553.n4.nabble.com/Rebuild-failed-Map-failed-Original-message-Map-failed-tp4660182p4660199.html Sent from the iText - General mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
