Minyaa JIRA is now upgraded to JIRA 4.3.4 + Minyaa 3.1 !

Minyaa Suite

Error during start-up

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Answered
  • Affects Version/s: 2.4.2
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Labels:
    None
  • Rank:
    304 
  • Workers:

Description

On Jira startup, I see this error:

2011-02-10 11:42:44,830 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] There were problems loading the module 'rest' in plugin 'Minyaa JIRA Plugin Core Gadgets'. The module has been disabled.
2011-02-10 11:42:44,832 main ERROR [atlassian.plugin.parsers.XmlDescriptorParser] Cannot find ModuleDescriptor class for plugin of type 'rest'.
com.atlassian.plugin.PluginParseException: Cannot find ModuleDescriptor class for plugin of type 'rest'.
at com.atlassian.jira.plugin.JiraModuleDescriptorFactory.getModuleDescriptor(JiraModuleDescriptorFactory.java:113)
at com.atlassian.plugin.parsers.XmlDescriptorParser.createModuleDescriptor(XmlDescriptorParser.java:189)
at com.atlassian.plugin.parsers.XmlDescriptorParser.configurePlugin(XmlDescriptorParser.java:141)
at com.atlassian.plugin.loaders.SinglePluginLoader.loadPlugin(SinglePluginLoader.java:135)
at com.atlassian.plugin.loaders.SinglePluginLoader.loadAllPlugins(SinglePluginLoader.java:89)
at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadClassPathPlugins(ClassPathPluginLoader.java:59)
at com.atlassian.plugin.loaders.ClassPathPluginLoader.loadAllPlugins(ClassPathPluginLoader.java:67)
at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:136)
at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:52)
at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1326)
at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:227)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:212)
at com.atlassian.jira.upgrade.ConsistencyLauncher.launchConsistencyChecker(ConsistencyLauncher.java:63)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:42)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)

Attached there is a screen shot.

I haven't done any changing to a configuration.
I have only test to connect Jira to Google smtp server. If I return to default configuration the problem persist.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Thoulé added a comment - 10/Feb/11 6:09 AM

The 2 Jars named jira-plugin-minyaa-core-gadgets-4.2-2.4.jar and jira-plugin-minyaa-time-gadgets-4.2-2.4.jar have to be copied in jira-home\plugins\installed-plugins folder.

They are V2 Plugins.

Vincent

Show
Vincent Thoulé added a comment - 10/Feb/11 6:09 AM The 2 Jars named jira-plugin-minyaa-core-gadgets-4.2-2.4.jar and jira-plugin-minyaa-time-gadgets-4.2-2.4.jar have to be copied in jira-home\plugins\installed-plugins folder. They are V2 Plugins. Vincent
Hide
Permalink
Samuele Pretini added a comment - 10/Feb/11 6:17 AM

Ok.

The plugin jar now is in the correct position.

All plug-in starts correctly.

But during start-up I see this error:

Exception in thread "JiraQuartzScheduler_Worker-2" java.lang.NoClassDefFoundError: org/minyaa/license/util/ProductProvider
at com.minyaa.jira.plugin.licenses.LicenseManagerBuilder.loadLicenseManagers(LicenseManagerBuilder.java:42)
at com.minyaa.jira.plugin.licenses.DefaultLicenseManagerDirectory.refresh(DefaultLicenseManagerDirectory.java:52)
at com.minyaa.jira.plugin.licenses.DefaultLicenseManagerDirectory.getLicenseManagers(DefaultLicenseManagerDirectory.java:36)
at com.minyaa.license.service.ProductConsistencyCheckerService.getConsistencyCheckers(ProductConsistencyCheckerService.java:46)
at com.minyaa.license.service.ProductConsistencyCheckerService.run(ProductConsistencyCheckerService.java:39)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
Caused by: java.lang.ClassNotFoundException: org.minyaa.license.util.ProductProvider
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233)
... 9 more

Why?

Show
Samuele Pretini added a comment - 10/Feb/11 6:17 AM Ok. The plugin jar now is in the correct position. All plug-in starts correctly. But during start-up I see this error: Exception in thread "JiraQuartzScheduler_Worker-2" java.lang.NoClassDefFoundError: org/minyaa/license/util/ProductProvider at com.minyaa.jira.plugin.licenses.LicenseManagerBuilder.loadLicenseManagers(LicenseManagerBuilder.java:42) at com.minyaa.jira.plugin.licenses.DefaultLicenseManagerDirectory.refresh(DefaultLicenseManagerDirectory.java:52) at com.minyaa.jira.plugin.licenses.DefaultLicenseManagerDirectory.getLicenseManagers(DefaultLicenseManagerDirectory.java:36) at com.minyaa.license.service.ProductConsistencyCheckerService.getConsistencyCheckers(ProductConsistencyCheckerService.java:46) at com.minyaa.license.service.ProductConsistencyCheckerService.run(ProductConsistencyCheckerService.java:39) at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:67) at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:48) at org.quartz.core.JobRunShell.run(JobRunShell.java:191) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516) Caused by: java.lang.ClassNotFoundException: org.minyaa.license.util.ProductProvider at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1387) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1233) ... 9 more Why?
Hide
Permalink
Vincent Thoulé added a comment - 10/Feb/11 6:23 AM

When Minyaa state changes from disable to enable, the internal plugin system is refreshed, and but the Job system is not stopped, and if a Job starts during the refresh, it is facing to a not yet available environment.

You can also encounter error around Minyaa Listener and Service.

When Plugin System is refreshed, all comes back to normal.

V.

Show
Vincent Thoulé added a comment - 10/Feb/11 6:23 AM When Minyaa state changes from disable to enable, the internal plugin system is refreshed, and but the Job system is not stopped, and if a Job starts during the refresh, it is facing to a not yet available environment. You can also encounter error around Minyaa Listener and Service. When Plugin System is refreshed, all comes back to normal. V.

People

Vote (0)
Watch (0)

Dates

  • Created:
    10/Feb/11 6:05 AM
    Updated:
    10/Feb/11 6:23 AM
    Resolved:
    10/Feb/11 6:10 AM
Bug tracking and project tracking for software development powered by Atlassian JIRA (v4.3.4#620-r152668) | Report a problem
This JIRA site is for demonstration purposes only. Evaluate JIRA - bug tracking software for your team.