java.lang.IllegalArgumentException: Plugin [${elasticsearch.plugin.name}] must be at least a jvm or site plugin

GitHub | linkmancheng | 4 months ago
  1. 0

    ik 1.9.4 加载配置properteis文件报错

    GitHub | 4 months ago | linkmancheng
    java.lang.IllegalArgumentException: Plugin [${elasticsearch.plugin.name}] must be at least a jvm or site plugin
  2. 0

    [JRA-20451] Jira Standalone does not work with IBM JVM 1.6 - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
  3. 0

    Following error was thrown while runing JIRA 4.0.x with JRE 1.6.0 IBM J9 2.4: {noformat} 2010-03-15 15:26:52,343 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked. com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1285) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210) 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.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:630) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:556) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:314) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) 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:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.IllegalArgumentException: The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header at com.atlassian.plugin.osgi.factory.OsgiPluginUninstalledHelper.install(OsgiPluginUninstalledHelper.java:70) at com.atlassian.plugin.osgi.factory.OsgiPlugin.installInternal(OsgiPlugin.java:316) at com.atlassian.plugin.impl.AbstractPlugin.install(AbstractPlugin.java:299) at com.atlassian.plugin.impl.AbstractDelegatingPlugin.install(AbstractDelegatingPlugin.java:203) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:537) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:152) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275) ... 28 more 2010-03-15 15:26:52,349 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked. 2010-03-15 15:26:52,350 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler.... 2010-03-15 15:26:52,350 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Skipping JIRA Scheduler initialisation, JIRA is not ready. {noformat} A similar issue was reported before: http://jira.atlassian.com/browse/JRA-19401 where the problem only happened on Websphere 7.0 and was resolved as "Won't Fix".

    Atlassian JIRA | 7 years ago | Lei Ding [Atlassian]
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JRA-20451] Jira Standalone does not work with IBM JVM 1.6 - Atlassian JIRA

    atlassian.com | 1 year ago
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header
  6. 0

    I'm not sure if this issue is duplication of JRA-19379, but because it is marked as closed and fixed and I still have the problem I've decided to open a new one here. Below is the exception I'm getting trying to start jira standalone on IBM AIX with the IBM JDK 1.6.0 Sr6 (full version info provided at the end of the stack trace). If this is an IBM issue I'll highly appreciate if someone could point me to IBM's PMR# to be able to track the progress there. Or do I need specific IBM JRE version to be able to run jira? TIA, Ilko 2010-02-09 22:25:48,140 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisatio n. JIRA has been locked. com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplu gin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifes t header at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1285) at com.atlassian.jira.ComponentManager.quickStart(ComponentManager.java:224) at com.atlassian.jira.ComponentManager.start(ComponentManager.java:210) 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:3795) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4252) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: java.lang.IllegalArgumentException: The plugin key 'com.atlassian.auiplugin' must either match the OSGi bundle symb olic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifest header at com.atlassian.plugin.osgi.factory.OsgiPluginUninstalledHelper.install(OsgiPluginUninstalledHelper.java:70) at com.atlassian.plugin.osgi.factory.OsgiPlugin.installInternal(OsgiPlugin.java:316) at com.atlassian.plugin.impl.AbstractPlugin.install(AbstractPlugin.java:299) at com.atlassian.plugin.impl.AbstractDelegatingPlugin.install(AbstractDelegatingPlugin.java:203) at com.atlassian.plugin.manager.DefaultPluginManager.addPlugins(DefaultPluginManager.java:530) at com.atlassian.plugin.manager.DefaultPluginManager.init(DefaultPluginManager.java:152) at com.atlassian.jira.plugin.JiraPluginManager.start(JiraPluginManager.java:49) at com.atlassian.jira.ComponentManager$PluginSystem.start(ComponentManager.java:1275) ... 19 more 2010-02-09 22:25:48,149 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked. 2010-02-09 22:25:48,149 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler.... 2010-02-09 22:25:48,150 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Skipping JIRA Scheduler initialisation, JIRA is not ready. 2010-02-09 22:25:49,699 main FATAL [webwork.dispatcher.ServletDispatcher] ****************************************** JIRA startup failed, JIRA has been locked. ****************************************** java version "1.6.0" Java(TM) SE Runtime Environment (build pap6460sr6ifix-20091015_01(SR6+152211+155930+156106)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr6-20091001_43491 (JIT enabled, AOT enabled) J9VM - 20091001_043491 JIT - r9_20090902_1330ifx1 GC - 20090817_AA) JCL - 20091006_01

    Atlassian JIRA | 7 years ago | Ilko Iliev
    com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. The plugin key 'com.atlassian.auiplu gin' must either match the OSGi bundle symbolic name (Bundle-SymbolicName) or be specified in the Atlassian-Plugin-Key manifes t header

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.IllegalArgumentException

      Plugin [${elasticsearch.plugin.name}] must be at least a jvm or site plugin

      at org.elasticsearch.plugins.PluginInfo.readFromProperties()
    2. ElasticSearch
      Node.<init>
      1. org.elasticsearch.plugins.PluginInfo.readFromProperties(PluginInfo.java:107)
      2. org.elasticsearch.plugins.PluginsService.getPluginBundles(PluginsService.java:378)
      3. org.elasticsearch.plugins.PluginsService.<init>(PluginsService.java:128)
      4. org.elasticsearch.node.Node.<init>(Node.java:158)
      4 frames