java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')

Atlassian JIRA | Daniel Leng | 2 years ago
  1. 0

    [JRA-39338] Cannot start up JIRA WAR 6.3.x with Tomcat 7.0.47 due to Running JIRA from a packed WAR is not supported - Atlassian JIRA

    atlassian.com | 1 year ago
    java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')
  2. 0

    In our [Supported Platform docs|https://confluence.atlassian.com/display/JIRA/Supported+Platforms], it is mentioned that JIRA is tested with Apache Tomcat 7.0.47. If you attempt to start up JIRA with Apache Tomcat 7.0.47, you will hit into this error: {noformat} A fatal error occurred during bootstrapping. JIRA has been locked. java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins') at com.atlassian.jira.plugin.PluginFactoryAndLoaderRegistrar.getBundledPluginsLoader(PluginFactoryAndLoaderRegistrar.java:148) at com.atlassian.jira.plugin.BootstrapPluginLoaderFactory.getPluginLoaders(BootstrapPluginLoaderFactory.java:73) at com.atlassian.jira.plugin.JiraPluginManager.<init>(JiraPluginManager.java:72) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.picocontainer.injectors.AbstractInjector.newInstance(AbstractInjector.java:145) at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:342) ... {noformat} According to this [Answers topic|https://answers.atlassian.com/questions/314354/running-jira-from-a-packed-war-is-not-supported], {quote} Tomcat stopped supporting unpacking of war files outside of appBase in version 7.0.12 They then fixed the issue in Tomcat 8 and back ported the fix to 7.0.48 going forward. {quote} Workaround: Use *Apache Tomcat 7.0.50* instead.

    Atlassian JIRA | 2 years ago | Daniel Leng [Atlassian]
    java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')
  3. 0

    In our [Supported Platform docs|https://confluence.atlassian.com/display/JIRA/Supported+Platforms], it is mentioned that JIRA is tested with Apache Tomcat 7.0.47. If you attempt to start up JIRA with Apache Tomcat 7.0.47, you will hit into this error: {noformat} A fatal error occurred during bootstrapping. JIRA has been locked. java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins') at com.atlassian.jira.plugin.PluginFactoryAndLoaderRegistrar.getBundledPluginsLoader(PluginFactoryAndLoaderRegistrar.java:148) at com.atlassian.jira.plugin.BootstrapPluginLoaderFactory.getPluginLoaders(BootstrapPluginLoaderFactory.java:73) at com.atlassian.jira.plugin.JiraPluginManager.<init>(JiraPluginManager.java:72) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.picocontainer.injectors.AbstractInjector.newInstance(AbstractInjector.java:145) at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:342) ... {noformat} According to this [Answers topic|https://answers.atlassian.com/questions/314354/running-jira-from-a-packed-war-is-not-supported], {quote} Tomcat stopped supporting unpacking of war files outside of appBase in version 7.0.12 They then fixed the issue in Tomcat 8 and back ported the fix to 7.0.48 going forward. {quote} Workaround: Use *Apache Tomcat 7.0.50* instead.

    Atlassian JIRA | 2 years ago | Daniel Leng
    java.lang.IllegalStateException: Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Error 500--Internal Server Error -java.lang.IllegalStateException:

    Oracle Community | 7 years ago | 843844
    java.lang.IllegalStateException: Multiple jsfComponents.jar on classpath causes multiple initialization and might cause unwanted side effects - therefore this is not allowed. Please make sure to have jsfComponents.jar only once on the class path. Multiple jsfComponents.jar found: [zip:C:/Apps/......../../..../war/WEB-INF/lib/jsfComponents_lib_jsfLib_3pl.jar]
  6. 0

    Yet Another IllegalStateException Weirdness

    Google Groups | 5 years ago | jtoolsdev
    java.lang.IllegalStateException: The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. [in ListView(16908298, class android.widget.ListView) with Adapter(class android.widget.CalendarView$WeeksAdapter)] Thing is there is no ListView in my code that does this. And what adapter mods are made in my ListViews are in a Handler not in a background thread. Calendar is called to get date information but not in a ListView. Running the original app (for 1.5 and above) does not throw this error. Here is the rest of the trace if it suggests anything:

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalStateException

      Running JIRA from a packed WAR is not supported. Configure your Servlet container to unpack the WAR before running it. (Cannot resolve real path for '/WEB-INF/atlassian-bundled-plugins')

      at com.atlassian.jira.plugin.PluginFactoryAndLoaderRegistrar.getBundledPluginsLoader()
    2. com.atlassian.jira
      JiraPluginManager.<init>
      1. com.atlassian.jira.plugin.PluginFactoryAndLoaderRegistrar.getBundledPluginsLoader(PluginFactoryAndLoaderRegistrar.java:148)
      2. com.atlassian.jira.plugin.BootstrapPluginLoaderFactory.getPluginLoaders(BootstrapPluginLoaderFactory.java:73)
      3. com.atlassian.jira.plugin.JiraPluginManager.<init>(JiraPluginManager.java:72)
      3 frames
    3. Java RT
      Constructor.newInstance
      1. sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      2. sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
      3. sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
      4. java.lang.reflect.Constructor.newInstance(Constructor.java:526)
      4 frames
    4. PicoContainer Core
      ConstructorInjector$1.run
      1. org.picocontainer.injectors.AbstractInjector.newInstance(AbstractInjector.java:145)
      2. org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:342)
      2 frames