https://bz.apache.org/bugzilla/show_bug.cgi?id=65273

            Bug ID: 65273
           Summary: NoClassDefFoundError in Apache POI dependency after
                    upgrading to Tomcat 8.57 in Jira
           Product: Tomcat 8
           Version: 8.5.57
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: Packaging
          Assignee: dev@tomcat.apache.org
          Reporter: angelica.sala...@easesolutions.com
  Target Milestone: ----

Hello,

I am unsure if this is the correct channel to make this report. Let me know
either way. I am from Easesolutions, vendor of R4J - Requirements Management
for Jira. 

In our application, we are using the Apache POI library to support our Word
Export capabilities. Recently, we have been receiving reports from customers
with the same error:
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.poi.openxml4j.opc.internal.marshallers.ZipPackagePropertiesMarshaller
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.poi.openxml4j.opc.internal.marshallers.ZipPackagePropertiesMarshaller
        at org.apache.poi.openxml4j.opc.OPCPackage.init(OPCPackage.java:161)
[?:?]
        at org.apache.poi.openxml4j.opc.OPCPackage.<init>(OPCPackage.java:141)
[?:?]
        at org.apache.poi.openxml4j.opc.ZipPackage.<init>(ZipPackage.java:97)
[?:?]
        at org.apache.poi.openxml4j.opc.OPCPackage.open(OPCPackage.java:324)
[?:?]

This looks like a dependency/classpath issue. The thing is, we have not changed
our POI dependencies since 2017 and have released several versions with no
change and now it's suddenly acting up. And after trying many things, we are
now very lost. Ref to our developer community post:
https://community.developer.atlassian.com/t/class-cannot-be-loaded-when-restarting-jira-software/47421/3

This is being experienced intermittently by customers. For example, some  have
our application with the same version installed in multiple nodes but only
experience the issue in 1 node. We have not been able to reproduce the issue in
our own environments.

It seems that the common action for all these customers before experiencing the
issue was that they upgraded Jira to a version that had Apache version 8.57 and
up. Ref:
https://confluence.atlassian.com/jiracore/bundled-tomcat-and-java-versions-1013854250.html

Hope you can help point us in the right direction.

Thank you and best regards,
Angelica

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to