This is similar to the issue here:

but occurs on shutdown.  Is the resolution the same?


2015-02-24 07:08:24,627 localhost-startStop-2 ERROR [osgi.container.felix.FelixOsgiContainerManager] JarContent: Unable to read bytes.
java.lang.IllegalStateException: zip file closed
at Source)
at Source)
at java.util.jar.JarFile.getEntry(Unknown Source)
at org.apache.felix.framework.util.JarFileX.getEntry(
at org.apache.felix.framework.cache.JarContent.getEntryAsBytes(
at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.findClass(
at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(
at org.apache.felix.framework.ModuleImpl.access$200(
at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.getDeclaringClass0(Native Method)
at java.lang.Class.getDeclaringClass(Unknown Source)
at java.lang.Class.getEnclosingClass(Unknown Source)
at java.lang.Class.getCanonicalName(Unknown Source)
at com.atlassian.threadlocal.BruteForceThreadLocalCleanup.getPrettyClassName(
at com.atlassian.threadlocal.BruteForceThreadLocalCleanup.checkThreadLocalMapForLeaks(
at com.atlassian.threadlocal.BruteForceThreadLocalCleanup.cleanUpThreadImpl(
at com.atlassian.threadlocal.BruteForceThreadLocalCleanup.cleanupThreadLocals(
at com.atlassian.threadlocal.BruteForceThreadLocalCleanup.cleanUp(
at com.atlassian.jira.startup.DefaultJiraLauncher.cleanupThreadLocals(
at com.atlassian.jira.startup.DefaultJiraLauncher.cleanupAfterOurselves(
at com.atlassian.jira.startup.DefaultJiraLauncher.stop(
at com.atlassian.jira.startup.LauncherContextListener.contextDestroyed( <+5> ( ( ( ( (
at Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)
2015-02-24 07:11:14,822 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

2 answers

This widget could not be displayed.

Almost certainly it's the same.

This widget could not be displayed.
Shayne Covey Atlassian Team Feb 24, 2015

The errors do seem to line up between what you're seeing and the knowledge base article, so I would definitely recommend running through the resolutions listed in the article. As Andris said, it's likely that the problem shares a similar root cause, despite the behavior being slightly different than what is described in the article.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

179 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you