If the Enterprise Message API detects an error condition, the Enterprise Message API might throw an exception. All exceptions in the Enterprise Message API inherit from the parent class OmmException, which provides functionality and methods common across all OmmException types.
TIP: LSEG recommends you use try and catch blocks during application development and QA to quickly detect and fix any Enterprise Message API usage or application design errors.
The Enterprise Message API supports the following exception types:
• OmmInaccessibleLogFileException: Thrown when the Enterprise Message API cannot open a log file for writing.
• OmmInvalidConfigurationException: Thrown when the Enterprise Message API detects an unrecoverable configuration error.
• OmmInvalidHandleException: Thrown when an invalid / unrecognized item handle is passed in on OmmConsumer or OmmProvider class methods.
• OmmInvalidUsageException: Thrown when the Enterprise Message API detects invalid interface usage.
• OmmJsonConverterException: Thrown when the Enterprise Message API fails to perform a RWF/JSON conversion.
• OmmMemoryExhaustionException: Thrown when the Enterprise Message API detects an out-of-memory condition.
• OmmOutOfRangeException: Thrown when a passed-in parameter lies outside the valid range.
• OmmSystemException: Thrown when the Enterprise Message API detects a system exception.
• OmmUnsupportedDomainTypeException: Thrown if domain type specified on a message is not supported.