Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.4.2, 9.4.3
-
None
-
9.04
-
3
-
Severity 3 - Minor
-
Description
Issue Summary
Jira Time Zone Detection plugin 4.1.0 seems to be affected by the issue described in JRASERVER-74741.
It's probably using an old version of the atlassian-plugin-scanner and it's being impacted on startup by race conditions with other 3rd party apps that don't make use of Atlassian SDK.
This is reproducible on Data Center: (yes) / (no)
Steps to Reproduce
- Install Jira 9.4.2
- Install [Delegated Project Creator https://marketplace.atlassian.com/apps/1211157/delegated-project-creator-for-jira?hosting=datacenter&tab=overview] v.4.8.6
- Confirm the Jira Time Zone Detection plugin's on version 4.1.0
- Repeatedly restart Jira
Expected Results
Jira will consistently startup without any plugin startup failures
Actual Results
Occasionally, the Jira Time Zone Detection plugin may fail because it's being loaded after the Delegated Project Creator:
********************************************************************************************************************************************************************************************************
___ FAILED PLUGIN REPORT _____________________
1 plugin failed to load during Jira startup.
'com.atlassian.jira.jira-tzdetect-plugin' - 'Jira Time Zone Detection plugin' failed to load.
Unexpected exception parsing XML document from URL [bundle://3845c053-3f44-49df-9d9e-7f269e27ff79_91.0:0/META-INF/spring/context.xml]; nested exception is java.lang.NoClassDefFoundError: org/w3c/dom/Element
org/w3c/dom/Element
*** Class 'org.w3c.dom.Element' was not found because bundle com.wittified.jira.project-creator [214] does not import 'org.w3c.dom' even though bundle [org.apache.felix.framework [0](R 0)] osgi.wiring.package; {bundle-symbolic-name=[Ljava.lang.String;@1be9c13b, bundle-version=7.0.3, version=0.0.0.JavaSE_001_008, osgi.wiring.package=org.w3c.dom} does export it. Additionally, the class is also available from the system class loader. There are two fixes: 1) Add an import for 'org.w3c.dom' to bundle com.wittified.jira.project-creator [214]; imports are necessary for each class directly touched by bundle code or indirectly touched, such as super classes if their methods are used. 2) Add package 'org.w3c.dom' to the 'org.osgi.framework.bootdelegation' property; a library or VM bug can cause classes to be loaded by the wrong class loader. The first approach is preferable for preserving modularity. ***
org.w3c.dom.Element not found by com.wittified.jira.project-creator [214]
It was loaded from /opt/atlassian/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-tzdetect-plugin-4.1.0.jar
Workaround
The only workaround available is to restart Jira again until the plugin startup without errors.
Attachments
Issue Links
- relates to
-
-
- Gathering Impact
-
-
RAID-3359 Loading...