Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start Jira after Upgrade from 8.2.0 to 8.3.5 - Illegal use of nonvirtual function call

Stephen Blacketer
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 14, 2020

Hi,

After upgrading and have the installer complete the process, JIRA failed to start.

The error message is as below:

2020-05-14 22:41:42,950 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory 'C:\Program Files\Atlassian\Application Data\JIRA' is validated and locked for exclusive use by this instance.
2020-05-14 22:41:42,967 localhost-startStop-1 ERROR [o.a.c.c.C.[Catalina].[localhost].[/]] Exception sending context initialized event to listener instance of class [com.atlassian.jira.startup.LauncherContextListener]
java.lang.BootstrapMethodError: call site initialization exception
at java.lang.invoke.CallSite.makeSite(CallSite.java:341)
at java.lang.invoke.MethodHandleNatives.linkCallSiteImpl(MethodHandleNatives.java:307)
at java.lang.invoke.MethodHandleNatives.linkCallSite(MethodHandleNatives.java:297)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(LauncherContextListener.java:141)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:101)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.VerifyError: (class: com/atlassian/jira/startup/LauncherContextListener$$Lambda$23, method: run signature: ()V) Illegal use of nonvirtual function call
at sun.misc.Unsafe.defineAnonymousClass(Native Method)
at java.lang.invoke.InnerClassLambdaMetafactory.spinInnerClass(InnerClassLambdaMetafactory.java:326)
at java.lang.invoke.InnerClassLambdaMetafactory.buildCallSite(InnerClassLambdaMetafactory.java:194)
at java.lang.invoke.LambdaMetafactory.metafactory(LambdaMetafactory.java:304)
at java.lang.invoke.CallSite.makeSite(CallSite.java:302)
2020-05-14 22:41:43,013 localhost-startStop-1 ERROR [o.a.c.c.C.[Catalina].[localhost].[/]] Exception sending context destroyed event to listener instance of class [com.atlassian.jira.startup.LauncherContextListener]
java.lang.IllegalStateException: Context destroyed without being initialized first. JIRA launcher is confused.
at com.atlassian.jira.startup.LauncherContextListener.contextDestroyed(LauncherContextListener.java:209)
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4817)
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5474)
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
... 2 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Where abouts do I look to find the cause of the problem?  

1 answer

0 votes
Mike Rathwell
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2020

Hi @Stephen Blacketer 

This is a tough call but it got unhappy real fast in the startup sequence. I would suggest you first, at least, try manually clearing the caches (grabbed the first correct set of instructions after grepping Google for it).

  1. Clear your cache. To do this, first access your JIRA installation directory. There, access the ‘Work’ folder. Delete the contents of the folder. DO NOT DELETE THE WORK FOLDER. Only delete the contents.
  2. Clear your plugin cache. To do this, access your JIRA Home folder. There, access the ‘Plugins’ folder. Delete the ‘.osgi-plugins’ and the ‘.bundled-plugins’ folders. Not to worry, these 2 folders will be rebuilt when JIRA starts

If I may make a recommendation as well; Jira will run fine on Windows. However management of it and overall control is more difficult than when run on Linux. I have run it both environments and now run it containerized on a Linux base. Much of the weirdness like this does tend to evaporate when not on Windows.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.2.0
TAGS
AUG Leaders

Atlassian Community Events