MonitorManipulationException

The MonitorManipulationException is thrown if MicroStrategy Intelligence Server fails to kill jobs, disconnect user or database connections, or perform specified administrative actions on caches. This happens for various reasons, such as an invalid job ID or a session that has timed out. This class has the following method:

• getFailures()

  Returns a set of failures encountered in the batch operation of monitoring activities. Each failure contains an error code and an error message describing the reason for failure.

The MonitorManipulationFailure interface and derived interfaces

The MonitorManipulationFailure interface contains information— error code, error message, and type of failure— about a single failure. In addition, it has four derived interfaces, which can be used to obtain information about the action being taken when the failure occurred.

• JobDeletionFailure

• UserDisconnectionFailure 

• DBDisconnectionFailure
  

• CacheManipulationFailure

The diagram below illustrates how these interfaces interact with each other.

The MonitorManipulationFailure interface has the following methods:

• getErrorCode()

  Returns the error code for the error. 

• getErrorMessage()

  Returns the error message for the error. 

• getType()

  Returns the type of failure (that is, a value from EnumWebMonitorType). The type also specifies into which derived interface the MonitorManipulationFailure object can be cast.

The four derived interfaces give the unique identifier for the object being deleted/disconnected.

• JobDeletionFailure

  Gives the job ID for the job being deleted. 

• UserDisconnectionFailure

  Gives the session ID and the project for the user being disconnected.

• DBDisconnectionFailure

  Gives the connection number for the database being disconnected. 

• CacheManipulationFailure

  Gives the cache ID, the project DSSID, and the project name for the cache being manipulated.