Details
-
Bug
-
Resolution: Fixed
-
High
-
None
-
None
-
Customer: JIRA Enterprise 3.9.3 Standalone on Fedora Linux, JRE 1.6u1
Me: JIRA Enterprise Standalone on Ubuntu Linux and JRA 1.6, versions 3.9.1 through to 3.10 (didn't test earlier than this)
Description
- Install a clean JIRA Enterprise Standalone.
- Go through the setup wizard.
- Enable RPC from General Configuration.
- Go toPlugins > RPC JIRA Plugin and disable either the Admin Service or the Project Role Service (or both). (I didn't test if it also happens with other services.)
- Restart JIRA, or at least try to.
Startup fails with the following error:
com.atlassian.jira.upgrade.ConsistencyLauncher
org.picocontainer.defaults.UnsatisfiableDependenciesException: com.atlassian.jira.rpc.soap.JiraSoapServiceImpl doesn't have any satisfiable constructors. Unsatisfiable dependencies: [[interface com.atlassian.jira.rpc.auth.TokenManager, interface com.atlassian.jira.rpc.soap.service.ProjectService, interface com.atlassian.jira.rpc.soap.service.IssueService, interface com.atlassian.jira.rpc.soap.service.UserService, interface com.atlassian.jira.rpc.soap.service.SchemeService, interface com.atlassian.jira.config.ConstantsManager, interface com.atlassian.jira.rpc.soap.service.AdminService, interface com.atlassian.jira.rpc.soap.service.SearchService, interface com.atlassian.jira.rpc.soap.service.ProjectRoleService, interface com.atlassian.jira.rpc.soap.service.IssueConstantsService]]
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.getGreediestSatisifableConstructor(ConstructorInjectionComponentAdapter.java:138)
at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:193)
at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35)
at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42)
at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:27)
at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstancesOfType(DefaultPicoContainer.java:274)
at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstances(DefaultPicoContainer.java:266)
at com.atlassian.jira.ComponentManager.eagerlyInstantiate(ComponentManager.java:437)
at com.atlassian.jira.ComponentManager.start(ComponentManager.java:340)
at com.atlassian.jira.upgrade.ConsistencyLauncher.contextInitialized(ConsistencyLauncher.java:31)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at org.apache.catalina.core.StandardService.start(StandardService.java:450)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432)
Jul 12, 2007 11:55:04 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Jul 12, 2007 11:55:04 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [] startup failed due to previous errors
A support customer reported this error doing an upgrade from 3.9.1 to 3.9.3 and was subsequently able to isolate it as above. The error is reproducible every time in versions 3.9.1 through to 3.10. I didn't test any versions earlier than 3.9.1.