If you download the binaries or checkout the source for 6.3.1 you get a ./lib folder which contains all the jars that should be on the class path for maximum compatibility with various image types as well as digital signature support.

If your building from source you can add the following maven dependencies to your project.

<dependency>
<groupId>com.twelvemonkeys.imageio</groupId>
<artifactId>imageio-tiff</artifactId>
<version>$

</version>
</dependency>

<dependency>
<groupId>org.apache.pdfbox</groupId>
<artifactId>jbig2-imageio</artifactId>
<version>$

</version>
</dependency>

<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<bouncy.version>1.54</bouncy.version>
<twelve-monkey.version>3.4-SNAPSHOT</twelve-monkey.version>
<jai-imageio.version>1.3.0</jai-imageio.version>
<jbig2.version>3.0.0-SNAPSHOT</jbig2.version>
</properties>

Patrick, thank you for the tests.
I think we can close this issue. Here are the logs for documentation:

I have reproduced this case in my dev env (eclipse OXYgen with jdk1.8.0_112, windows10) and I got the following trace:

10:02:14.427   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
-----------> Document.<clinit>: PDF write support was not found on the class path [16]
10:02:22.033   Document.setDocumentOrigin: MEMFREE: 102806528 of 137363456 [16]
10:02:22.033   Document.setDocumentOrigin: LOADING: null [16]
10:02:22.077 Catalog.<clinit>: ICEsoft ICEpdf Core x.x.x x [16]
10:02:22.640   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
10:02:22.733   Document.setDocumentOrigin: MEMFREE: 84863232 of 137363456 [16]
10:02:22.733   Document.setDocumentOrigin: LOADING: null [16]
10:02:22.765   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
10:02:22.843   Document.setDocumentOrigin: MEMFREE: 80575288 of 137363456 [16]
10:02:22.843   Document.setDocumentOrigin: LOADING: null [16]
10:02:23.015 ImageStream.<clinit>: Levigo JBIG2 image library was not found on classpath [124]
10:02:23.140 CCITTFax.<clinit>: javax.media.jai.JAI could not bef found on the class path [125]

I wonder about the last two messages and why I did not noticed it before. So I add the two jars and got:

10:19:41.132   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
-----------> Document.<clinit>: PDF write support was not found on the class path [16]
10:19:42.314   Document.setDocumentOrigin: MEMFREE: 142586512 of 191365120 [16]
10:19:42.314   Document.setDocumentOrigin: LOADING: null [16]
10:19:42.355 Catalog.<clinit>: ICEsoft ICEpdf Core x.x.x x [16]
10:19:42.792   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
10:19:42.870   Document.setDocumentOrigin: MEMFREE: 124438064 of 191365120 [16]
10:19:42.870   Document.setDocumentOrigin: LOADING: null [16]
10:19:42.917   Attachment.displayContent: Index=0 - 1024458.pdf m_change:false [16]
10:19:42.995   Document.setDocumentOrigin: MEMFREE: 120084560 of 191365120 [16]
10:19:42.995   Document.setDocumentOrigin: LOADING: null [16]
10:19:43.199 ImageStream.<clinit>: Levigo JBIG2 image library was found on classpath [66]

In both tests the file was not shown.

Regards EUGen

Alright, I send you a private message on our forums with my email address if you are able to release the file.

There is a bit of information on our wiki on how to start the viewer RI. http://www.icesoft.org/wiki/display/PDF/Starting+the+Viewer

Hi Patrick,

as I wrote in an application we use icepdf-core-6.2.2.jar + icepdf-viewer-6.2.2.jar - where we notice this problem.
Sure I can try the swing reference viewer or the cmd-line application to test.
But how to get into ? What should I install for the test?

But then I asked the owner of the DOC 1024458.pdf if I can sent you this doc for tests in a closed channel. Waiting for answer ... the answer is no. I'm not allowed to send you the pdf.

regards EUGen

Our online viewer is a little behind our current release is lacking a few Imaging jars. Is there any chance you can try with our swing reference viewer or one of our command line image captures applications. My guess is that this is is a jbig2 or TIFF class path issue.

there is another example pdf - but with business data (and I cannot publish it)

• 1024458.pdf in our internal tracker id 2239

While Wirtschaftsenglich-iceproblem.pdf can be shown in http://icepdf-viewer.icesoft.org/icepdf-viewer/icepdfViewer.jsf
1024458.pdf cannot! see attached screenshot icepdf-b.PNG