Implemented by objects which can describe problems
Implementations of this interface will be able to find a configured jira.home directory in one particular way.
A value object of collected plugin information
This provides information about the plugins in the system.
Immutable collection of PluginInfo.
Represents an individual check to be done on startup.
There are a number of services that should only be started in the active mode, start them here
Launcher responsible for generating start and stop analytic events.
JIRA Home path locator that gets the value from the jira-application.properties file and not the database.
The BootstrapContainerLauncher will bootstrap enough of JIRA during run level 0.
Warm up caches, async in the scheduler by default, but it can be done synchronously by setting a sysprop.
Listens to Web application startup and shutdown events to check that JIRA is valid to startup, and do whatever clean up may be required on shutdown.
Sets up clustered services as appropriate, starts upgrade services and scheduler as needed
Verifies versions in cluster depending on cluster state.
The ComponentContainerLauncher will launch PICO to creates its container of components.
Launcher for the
Loads a startup set ot data into the JIRA database
Configures the JIRA database by configuring transactions and setting up HSQL connection hacks.
This implementation of JiraLauncher contains all of the smarts of what to start in which order to ensure that JIRA starts properly.
Called at the end of JITA to report on what plugins have failed to load
Represents a generic failed StartupCheck.
This class will allow a series of messages to be formated/indented into the one log4j ouput.
ImageIO launcher pre-loads image service providers making the classes available to plugins via VM global.
This class will check for the index and perform minor repairs if required.
Represents the set of sanity checks that must be done as soon as database config is known.
This StartupCheck will check that there is a valid jira.home configured that we can get an exclusive lock on.
Gives the reason why the JiraHome Startup check failed.
This class prints information to the log when JIRA is "about to start" and when it "has started"
Event listener for internal JIRA events that the JiraStartupChecklist cares about.
This will obtain JIRA system information and place it in the specified
This class is the entry point for JIRA; it takes care of initialising the application.
A temporary class to empty the obsolete NotificaionInstance table with a delay.
This provides information about the plugins that are provided in JIRA
Implementation for PluginInfos.
Cleans up reindex requests that were running on this node and then the node was killed.
This is the very FIRST bit of log output that JIRA does.
Checks that all system plugins have been enabled.
Attempts to find a jira.home configured as a system property.
A class which takes a thread dump after a specified time.
Attempts to find a jira-home configured within our web context.
Indicates the reason why the JIRA home check failed.
Thrown when errors occur trying to validate the jira.home.
Copyright © 2002-2019 Atlassian. All Rights Reserved.