Loading...

Details

Type: Bug
Resolution: Fixed
Priority: High
Fix Version/s: 8.2.0, 8.1.1
Affects Version/s: 8.0.0, 8.1.0, 8.0.1, 8.0.2
Component/s: REST API
Labels:
- highlanders
- warranty

Introduced in Version:
8
Support reference count:
39
Symptom Severity:
Severity 2 - Major
UIS:
417
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:

Hide

Atlassian Update – 30 April 2019

Hi everyone,

Thank you for watching and commenting on this issue. We understand that this bug is crucial to our customers and it is our focus to ship the fix for it in the next release. This will be either the 8.1.1 bugfix release or the 8.2.0 feature release. In the latter case, please mind that there will be an EAP version available earlier, see this documentation for more info.

As Atlassian does not pre-announce release dates, we are not able to share any more details other than that no release will happen this week. On the other hand, as we aim for regularity with the delivery of Jira, one may have a look at the history of its previous versions in order to get a reasonable estimate on the future ones. This history can be found here.

With regard to building a patched version of the affected plugin based on the public repository, we discourage this for reasons other than testing on non-production instances. Such package may differ from the one that will ultimately be included in the official Jira release. This means that it may have never been tested and it will also make for harder investigations when contacting Atlassian Support should any future problems with the plugin occur.

With regards,
Pawel Drygas, Jira Server Bugmaster

Show
Atlassian Update – 30 April 2019 Hi everyone, Thank you for watching and commenting on this issue. We understand that this bug is crucial to our customers and it is our focus to ship the fix for it in the next release. This will be either the 8.1.1 bugfix release or the 8.2.0 feature release. In the latter case, please mind that there will be an EAP version available earlier, see this documentation for more info. As Atlassian does not pre-announce release dates, we are not able to share any more details other than that no release will happen this week. On the other hand, as we aim for regularity with the delivery of Jira, one may have a look at the history of its previous versions in order to get a reasonable estimate on the future ones. This history can be found here . With regard to building a patched version of the affected plugin based on the public repository, we discourage this for reasons other than testing on non-production instances. Such package may differ from the one that will ultimately be included in the official Jira release. This means that it may have never been tested and it will also make for harder investigations when contacting Atlassian Support should any future problems with the plugin occur. With regards, Pawel Drygas, Jira Server Bugmaster

Description

Summary

Calling /rest/ical/1.0/search/filter/events.ics iCalendar plugin endpoint throws an exception and therefore does not return proper iCal feed. This results in Confluence Team Calendar macro not working with Jira 8.0 instances.

Steps to reproduce

Run vanilla Jira 8.0 locally
Call /rest/ical/1.0/search/filter/events.ics endpoint
See atlassian-jira.log for error messages

Actual results

Request returns 404 status code and the following error is seen in logs:

2019-02-18 08:39:24,467 http-nio-8800-exec-16 ERROR admin 519x45x1 9okvtg 0:0:0:0:0:0:0:1 /rest/ical/1.0/search/filter/events.ics [c.a.plugin.servlet.DefaultServletModuleManager] Unable to create new reference LazyLoadedFilterReference{descriptor=com.atlassian.jira.extra.jira-ical-feed:iCalendarResource-filter (RESTful service for exporting JIRA entitites such as issue and versions as iCalendar), filterConfig=com.atlassian.plugin.servlet.filter.PluginFilterConfig@758972f8}
io.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.jira.extra.icalfeed.IcalendarResource': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.extra.icalfeed.IcalendarResource]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/atlassian/jira/ComponentManager
	at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:156)
	at io.atlassian.util.concurrent.LazyReference.get(LazyReference.java:116)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager.getInstance(DefaultServletModuleManager.java:430)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilter(DefaultServletModuleManager.java:423)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager.getFilters(DefaultServletModuleManager.java:288)
	at com.atlassian.plugins.rest.module.servlet.DefaultRestServletModuleManager.getFilters(DefaultRestServletModuleManager.java:127)
	... 39 filtered
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
	... 53 filtered
	at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
	... 1 filtered
	at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
	... 16 filtered
	at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:37)
	... 19 filtered
	at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
	... 10 filtered
	at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
	... 4 filtered
	at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
	... 26 filtered
	at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
	... 24 filtered
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.jira.extra.icalfeed.IcalendarResource': Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.extra.icalfeed.IcalendarResource]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/atlassian/jira/ComponentManager
	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:283)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1266)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1123)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:535)
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:495)
	... 2 filtered
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.atlassian.plugin.osgi.spring.DefaultSpringContainerAccessor.createBean(DefaultSpringContainerAccessor.java:99)
	at com.atlassian.plugins.rest.module.OsgiComponentProviderFactory$ContainerManagedComponentProvider.getInstance(OsgiComponentProviderFactory.java:90)
	... 3 filtered
	at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193)
	... 8 filtered
	at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193)
	... 1 filtered
	at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.initiate(RestDelegatingServletFilter.java:164)
	... 5 filtered
	at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.initServletContainer(RestDelegatingServletFilter.java:89)
	at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.init(RestDelegatingServletFilter.java:62)
	... 1 filtered
	at com.atlassian.plugin.servlet.DefaultServletModuleManager$LazyLoadedFilterReference.create(DefaultServletModuleManager.java:499)
	at com.atlassian.plugin.servlet.DefaultServletModuleManager$LazyLoadedFilterReference.create(DefaultServletModuleManager.java:486)
	at io.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:332)
	at io.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:150)
	... 209 more
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.extra.icalfeed.IcalendarResource]: Constructor threw exception; nested exception is java.lang.NoClassDefFoundError: com/atlassian/jira/ComponentManager
	at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:182)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:117)
	at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:276)
	... 246 more
Caused by: java.lang.NoClassDefFoundError: com/atlassian/jira/ComponentManager
	... 3 filtered
	at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
	at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:170)
	... 248 more

Error message in Confluence:

Expected results

Endpoint correctly returns "text/calendar".

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

image-2019-02-18-08-52-45-820.png
18 kB
21/Feb/2019 1:05 PM

Issue Links

relates to

CONFSERVER-57960 user cant create JIRA issue date event in Team calendar via JQL and saved filter when integrating with JIRA 8

Closed

resolves

CONFSERVER-58112 Customer cannot pull Jira (8.0) issue dates events to Team Calendars

Closed

CONFSERVER-57960 user cant create JIRA issue date event in Team calendar via JQL and saved filter when integrating with JIRA 8

Closed

CONFSERVER-58025 user cant pick custom Jira dates in JIRA issue dates event in Team calendar when integrating with JIRA 8

Closed

is caused by: JSEV-2566 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(6 mentioned in)

iCalendar REST API returns 404 java.lang.NoClassDefFoundError

Details

Description

Summary

Steps to reproduce

Actual results

Expected results

Workaround

Attachments

Attachments

Issue Links

Activity

People

Dates