Unable to access module for descriptor <class> of class
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After performing some significant tasks in the Jira Service Management instance (e.g., License update, Instance upgrade) might happen some errors from multiple apps trying to access some Jira Service Management classes.
Environment
>= 6.0.0
Diagnosis
From the logs, you should see some warnings like the following, where we can see there was a problem connecting some Power Scripts for Jira change handlers to Jira Service Desk directly after the install.
1
2
[c.a.s.p.a.internal.descriptors.EventWhenHandlerModuleDescriptor] Unable to access module for descriptor 'com.keplerrominfo.jira.plugins.jjupin:cprime-issue-field-changed-event-when-handler' of class 'com.atlassian.servicedesk.plugins.automation.internal.descriptors.EventWhenHandlerModuleDescriptor' because of 'io.atlassian.util.concurrent.LazyReference$InitializationException - java.lang.NoClassDefFoundError: com/atlassian/servicedesk/spi/automation/rulewhen/event/EventWhenHandler'. Continuing...
UpmAsynchronousTaskManager:thread-4 ERROR XXXXX 1096x991x4 8fwidi xxx.xxx.xxx.xxx /rest/plugins/1.0/installed-marketplace [c.a.plugin.module.PrefixDelegatingModuleFactory] Detected an error (NoClassDefFoundError) instantiating the module for plugin 'com.keplerrominfo.jira.plugins.jjupin' for module 'cprime-issue-assignee-changed-event-when-handler': com/atlassian/servicedesk/spi/automation/rulewhen/event/EventWhenHandler. This error is usually caused by your plugin using a imported component class that itself relies on other packages in the product. You can probably fix this by adding the missing class's package to your <Import-Package> instructions; for more details on how to fix this, see https://developer.atlassian.com/display/DOCS/NoClassDefFoundError . Cause
From the logs, the issue appears to point to a problem with declaring a component in the plugin's atlassian-plugin.xml file. The problem scope is: The 4x Power Scripts event handlers will not work until the instance is rebooted.
Solution
Restart the Jira instance.
If the issue persists, we strongly recommend reaching out to the app vendor.
Was this helpful?