You can use the Cache Failure transform to handle exceptions that might occur if a Cache transform fails.
A Cache Failure transform is an optional transform that can be added or removed as required
|ID||The identifying code of the exception. This is the "BIP" code of the
|Message||The message that is associated with the exception. For example:
A duplicate key was encountered while interacting with map 'SYSTEM.BROKER.DEFAULTMAP'. A client attempted operation 'put' with map 'SYSTEM.BROKER.DEFAULTMAP' from grid 'WMB', using key 'MyKey'. This attempt failed because an entry already exists with the same key. This operation requires that a key of the same name does not already exist in the map. : Duplicate key exception
|Inserts||The details that are specific to the exception. For example,
in the previous message, the following entities are the inserts:
Run time behavior
- If the Cache Failure transform is present in the Cache transform group, and is connected to one or more output objects, the exception is caught and processed by the Cache Failure transform.
- If the Cache Failure transform is present in the Cache transform group but is not connected to any output objects, the exception is caught by the Cache Failure transform, and is ignored.
- If the Cache Failure transform is not present in the Cache transform group and the Cache transform generates an exception, the exception is handled by the Mapping node in your message flow in the same way as other message flow exceptions.