Slow startup due to plugin jira-welcome-plugin timing out

Yay N' Stuff

Hi All,

I am trying to troubleshoot a problem in Jira 6.4.14 which causes painfully slow startup times.. I realize this is a long EOL'd version of Jira, but we're not able to upgrade right now (planned for the near future once we have better hardware).

The log file is filled with this:

INFO      [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.atlassian.jira.welcome.jira-welcome-plugin]

And it counts down from 300 seconds and eventually gives up. The server is under practically no load while this countdown is occurring. eventually, Jira gives up and continues to load, but I see this in the log before it continues:

1 plugin failed to load during JIRA startup.
        'com.atlassian.jira.welcome.jira-welcome-plugin' - 'JIRA Welcome Plugin'  failed to load.
                Application context initialization for 'com.atlassian.jira.welcome.jira-welcome-plugin' has timed out

                It has the following missing service dependencies :
                         &sampleDataImporter of type (objectClass=com.atlassian.jira.plugins.importer.sample.SampleDataImporter)
                         &sampleDataImporter of type (objectClass=com.atlassian.jira.plugins.importer.sample.SampleDataImporter)

The missing service dependencies is an interesting thing...

 

Any ideas on the best way to fix this problem?

 

Thanks in advance.

Y.

 

Andy Heinzer

I would recommend starting by checking out the Jira Sizing Guide, this can be helpful to understand what kind of resources we expect Jira to have given the size of your environment.  With this info, it might be necessary to also follow Increasing JIRA application memory.

Plugin timeouts like these tend to happen because the server is overloaded or under-resourced.   Usually this happens because of insufficient RAM, or trying to use a system with only a single CPU core.  It's possible that you could have tried to start Jira at one time, and if the system was low on available memory, a plugin in Jira could fail to load on startup.  If this happens, it is possible that Jira can mark plugins as being disabled in the database with a flag.  You can check for these via sql with a command such as

select * from pluginstate;

If all your plugins are enabled, then this table will be blank, but if you have any entries in there, with the values of 'false' for the 'pluginenabled' field, that plugin won't be loaded when Jira starts up.   This will list all user plugins and system plugins alike.   If you can get Jira started, you could also use the UPM manager in Jira to look for disabled plugins and try to reenable them this way.

It is possible that you might have already increased your resources to Jira, but a problem like this can continue until you clear this database entry that flags this system plugin as being disabled.