Pages Occassionally throws Invalid LOC Header (Bad Signature)
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When browsing JIRA, occassionally pages fail with invalid LOC header (bad signature):
1
2
3
4
5
6
com.caucho.java.JavaCompileException: error: error reading /opt/j2ee/domains/atlassian.com/jira/resin/lib/jsdk-24.jar; invalid LOC header (bad signature)
1 error
at com.caucho.java.InternalCompiler.executeInt(InternalCompiler.java)
at com.caucho.java.InternalCompiler.compileInt(InternalCompiler.java:81)
at com.caucho.java.AbstractJavaCompiler.run(AbstractJavaCompiler.java:101)
at java.lang.Thread.run(Thread.java:619)
Cause
The jar in question is perfectly valid. Upon further investigation, we found that JIRA had run out of memory. OutOfMemoryErrors can cause chaos in a JVM as threads are interrupted.
Resolution
Restarting the webapp will fix the problem. For further help on evaluating cause of the memory error please review Jira Server / Data Center crashes with OutofMemory Java heap space error.
Was this helpful?