GroupDocs Viewer - ClassNotFound Exception at container level

GroupDocs.Viewer Product Family
1

HI. We are in the process of upgrading groupdocs viewer version from 23.7 to 25.12 and we are seeing an exception when deploying the app in the container. We haven’t seen this exception for 23.7. Dockerfile is pretty simple and no special configuration for groupdocs jar. We do see groupdocs jar within the application jar at the container level, somehow app seems to not get to the groupdocs jar and throws the below error. I have seen other users in this form with similar issue, should there be a special configuration for container to be able to find groupdocs jar and with 25.12 version upgrade? As far the groupdocs usage, its running fine in local environment.

I cannot share code, let me know if there is any specific questions you have to help me resolve this. I also saw this in your documentation ‘Starting from [GroupDocs.Viewer for Java 24.4], the JAR package is signed using a GPG signature.’ (Install GroupDocs.Viewer for Java | GroupDocs) - Do we have to do anything different from the application side?

Caused by: java.lang.ClassNotFoundException: com.groupdocs.viewer.internal.c.a.ms.System.Exception

at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:592)

at org.springframework.boot.loader.net.protocol.jar.JarUrlClassLoader.loadClass(JarUrlClassLoader.java:107)

at org.springframework.boot.loader.launch.LaunchedClassLoader.loadClass(LaunchedClassLoader.java:91)

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)

2

Hello @LINDA_MARTINEZ_FMR_COM ,

We are sorry to hear that you encountered this issue after upgrading from version 23.7 to 25.12.

This type of error usually indicates that a dependency cannot be found in the updated JAR file, which causes the project compilation to fail with a java.lang.ClassNotFoundException. Since you performed an upgrade across multiple major versions (from 23.7 to 25.12), this version gap could indeed be the reason for the issue.

If you are unable to share the entire project for review, perhaps you could provide only the files where our Viewer is directly used? If sharing those files is not possible due to confidentiality restrictions, we can make this forum thread private, or you may send them directly to my email at evgen.efimov@aspose.com.

Alternatively, please provide the full stack trace from your console. We will analyze it on our side, and it may help us identify the root cause of the problem more precisely.

We look forward to your response.