Skip to main content

JMX Lifecycle Operations (Legacy)

Note

High Availability Clustering is a legacy feature that only works on the Orient database.

All new deployments should use one of our new high availability or resilient deployment options described in Resiliency and High Availability.

Warning

These operations are intended to be used with the guidance of Sonatype support. Usage without supervision of Sonatype is not supported or recommended.

ManagedLifecycleBean

This JMX bean provides a set of attributes and operations to allow the user to inspect and manipulate the current lifecycle phase of a Nexus Repo Manager instance. The expectation is that these will be used for recovery operations. A Phase is a step in the start up process used to group similar components together and ensure that their dependencies are started before them. In order, the phases are: OFF, KERNEL, STORAGE, RESTORE, UPGRADE, SCHEMAS, EVENTS, SECURITY, SERVICES, CAPABILITIES, and TASKS.

  1. OFF - NXRM is completely off.

  2. KERNEL - The most basic parts of the node are running.

  3. STORAGE - The databases and caches are setup.

  4. RESTORE - Any restoring from backups happens in this phase.

  5. UPGRADE - If any upgrades are needed, they will occur is this phase.

  6. SCHEMAS - This creates any missing schemas in the database.

  7. EVENTS - The framework that lets services communicate events is started.

  8. SECURITY - The parts of NXRM responsible for security are enabled.

  9. SERVICES - The bulk of an instances components are started here.

  10. CAPABILITIES - The capabilities are started, see Nodes#AccessingandConfiguringCapabilities

  11. TASKS - The task scheduler is enabled, and tasks may run.

Attributes

Phase
Java Monitoring and Management Console

Possible Value: Case sensitive string, one of OFF, KERNEL, STORAGE, RESTORE, UPGRADE, SCHEMAS, EVENTS, SECURITY, SERVICES, CAPABILITIES, or TASKS.

This sets NXRM to run in a particular phase. By moving a Nexus Repo manager instance to a new phase, you can start or stop select components. For example, if your instance is running in the TASKS phase and you set the phase to CAPABILITIES, then that instance will not run any scheduled tasks until it is moved back to the TASKS phase.

Operations

Bounce
Java Monitoring and Management Console

Possible Value for phase: Case sensitive string, one of OFF, KERNEL, STORAGE, RESTORE, UPGRADE, SCHEMAS, EVENTS, SECURITY, SERVICES, CAPABILITIES, or TASKS.

This operation takes the instance down to the supplied Lifecycle phase, and then back to the phase in which it was originally running. This effectively restarts the phases.