Moving tomcat with JIRA instance

[EKC IT Support]

I am moving my Tomcat server from a local C:\ drive install to a network share. I'm also changing the Tomcat to run under a domain login. 

So what I did was create said domain login "apachedev". I then copied the entire Tomcat installation directory from the C drive to the server share \\ekcintaws\intaws in a folder EKCMISC_Apache. The same subfolders I had on C (Tomcat9-DEV). I gave full control in the share permissions and in the folders to "apachedev".

I left the JIRA_DATA on the C: drive (C:|Atlassian\JIRA_DATA) but I hope to move that next.

Several other Tomcat applications I have in that server are running fine. Also, I have an Apache24 server in that folder which is working fine. So I think I got Tomcat working correctly.

So below are extracts from the Tomcat log showing how JIRA seems to startup just fine and then eventually  begins to fail when it starts loading plugins. Yes, my version is a little old. Any help is greatly appreciated.

JIRA seems to recognize things just fine:

2019-07-30 11:03:12,815 http-nio-11080-exec-63 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory 'c:\Atlassian\JIRA_DATA' is validated and locked for exclusive use by this instance.

JIRA Build : 7.7.0#77001-sha1:3be31511dfd860a9aedae108fbd5f079b4968c6a
Build Date : Thu Jan 11 00:00:00 CST 2018
Current Working Directory : \\ekcintaws\intaws\EKCMISC_Apache\Tomcat9-DEV
catalina.base : \\ekcintaws\intaws\EKCMISC_Apache\Tomcat9-DEV
catalina.home : \\ekcintaws\intaws\EKCMISC_Apache\Tomcat9-DEV

All these come out in an INFO [c.a.jira.start.JiraStartupLogger]

However, prior to the startup logger message I get:

2019-07-30 11:03:12,503 http-nio-11080-exec-63 ERROR [webwork.config.DefaultConfiguration] Skipping configuration for class 'com.atlassian.jira.config.webwork.JiraPluginsConfiguration'
java.lang.IllegalStateException: Unable to resolve component: interface com.atlassian.plugin.event.PluginEventManager
at com.atlassian.jira.component.ComponentAccessorWorker.getComponentOfType(ComponentAccessorWorker.java:40)
at com.atlassian.jira.component.ComponentAccessor.getComponentOfType(ComponentAccessor.java:255)

2019-07-30 11:03:12,534 http-nio-11080-exec-63 ERROR [webwork.config.DefaultConfiguration] Skipping configuration for class 'com.atlassian.jira.config.webwork.JiraPluginsConfiguration'
java.lang.IllegalStateException: Unable to resolve component: interface com.atlassian.plugin.event.PluginEventManager
at com.atlassian.jira.component.ComponentAccessorWorker.getComponentOfType(ComponentAccessorWorker.java:40)
at com.atlassian.jira.component.ComponentAccessor.getComponentOfType(ComponentAccessor.java:255)

The above two messages come out before the startup logger. Then after a number of info messages I get to:

___ Starting the JIRA Plugin System _________________

2019-07-30 11:03:51,526 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup begun
2019-07-30 11:03:51,541 JIRA-Bootstrap WARN [c.a.plugin.jmx.JmxUtil] Failed to register, instance already exists:
2019-07-30 11:03:54,812 JIRA-Bootstrap ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.plugin.event.events.PluginFrameworkStartingEvent@2d9b99b9] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.onStart(com.atlassian.plugin.event.events.PluginFrameworkStartingEvent), listener=com.atlassian.jira.plugin.JiraOsgiContainerManager@6f2933d9}]
java.lang.RuntimeException: URI has an authority component. Listener: com.atlassian.jira.plugin.JiraOsgiContainerManager event: com.atlassian.plugin.event.events.PluginFrameworkStartingEvent
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:55)
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:38)

2019-07-30 11:03:57,047 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.activeobjects.activeobjects-plugin' from 'Unit: \\ekcintaws\intaws\EKCMISC_Apache\Tomcat9-DEV\webapps\jira\WEB-INF\atlassian-bundled-plugins\activeobjects-plugin-1.5.0.jar (1515697882000)'.
2019-07-30 11:03:57,047 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception:
java.lang.IllegalStateException: Unable to create a tracker when osgi is not running
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:490)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:482)

2019-07-30 11:03:57,078 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Unable to deploy plugin 'com.atlassian.analytics.analytics-client' from 'Unit: \\ekcintaws\intaws\EKCMISC_Apache\Tomcat9-DEV\webapps\jira\WEB-INF\atlassian-bundled-plugins\analytics-client-5.3.1.jar (1515697882000)'.
2019-07-30 11:03:57,078 JIRA-Bootstrap ERROR [c.a.plugin.loaders.ScanningPluginLoader] Because of the following exception:
java.lang.IllegalStateException: Unable to create a tracker when osgi is not running
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:490)
at com.atlassian.plugin.osgi.container.felix.FelixOsgiContainerManager.getServiceTracker(FelixOsgiContainerManager.java:482)
at com.atlassian.plugin.osgi.factory.OsgiPluginFactory$1.create(OsgiPluginFactory.java:116)

[Earl McCutcheon]

Hello,

The Tomcat info is bundled in the application and needs to be located in the default installation location, and cannot be moved.  As covered in the following feature request relocating or swapping out the tomcat versions was something only avaliable in EAR/WAR installations:

https://jira.atlassian.com/browse/JRASERVER-30457

However while it was possible to use an EAR or WAR type installation that would let you install Jira to an existing Tomcat container or remap the install location to a new Tomcat container, Atlassian has deprecated all support for EAR/WAR Jira versions since the beginning of the 7.0.0,  so this only applies to version 6.14.x and earlier and cannot be done in 7.0.0 and later versions.

Regards,
Earl

[EKC IT Support]

Thanks for the info. I added a comment to 30457 in support of the WAR install as I think options are better. 

I clearly need to upgrade my JIRA instance anyway so I'll look into installing it in the new location and see how that goes. I have to do this in my "spare time" so I'll let you know in the future how this works out.