Dashboard

Issue: MIRTH-1040

Issue: MIRTH-2643

MIRTH-2499

Updated the XStream lib to 1.4.4 on Client and Donkey.

Cleaned up error/exception handling with object serialization and migration. If one or more serialized objects in the database fails to deserialize or migrate to the current version, an error will be logged and the offending object will be ignored (channels, code templates and alerts).

Renamed the previous SerializerException to XmlSerializerException since it is referenced by the XmlSerializer interface. Added a new SerializerException that is intended to be used by implementations of the Serializer interface in Donkey.

ObjectXMLSerializer now throws a SerializerException when serialization/deserialization or migration fails, instead of returning null. This is now consistent with the fact that XStream itself throws a runtime exception when it encounters an error when serializing or deserializing.

Refactored and rearranged code in DefaultMigrationController, Migrate2_0_0 and Migrate3_0_0.

MIRTH-2471

Reverted change to allow cascade deletes in Derby on the donkey message tables, since Derby uses a table-level lock when doing cascade deletes, which increases the risk of deadlocks.

Modified the DataPruner so that when pruning by message ids, it generates two message id lists, one for pruning content and one for pruning messages. That way it does not have to reference the d_mm.received date in the delete where clause, which allows Derby to still delete messages based on the d_mm.received_date instead of d_m.received_date.

Issue: MIRTH-2539

Issue: MIRTH-2479

MIRTH-1699

Changed Derby's donkey schema to allow cascade deletion on foreign keys.

Updated Derby's pruner statements to work with the cascade deletion and support pruning based on d_mm.received_date instead of d_m.received_date.

Refactored DataPruner so that it can delete messages based on a list of message ids even when not archiving. If a pruning strategy has been explicitly defined or if the current database has the "pruneMessagesByIds" query defined, it will automatically prune based on a message id list, rather than a date threshold. This improves performance dramatically in Derby.

Cleaned up code in DataPruner and made it easier to read.

Removed the MessageExportResult class since it is no longer needed.

Cleaned up and fixed problems with the DataPrunerTest unit tests.

Stopping/starting a source connector performs the same action as pausing/resuming the channel.

Destination connectors can only be stopped individually if queueing is enabled. When a destination connector is stopped, its filter and transformer are still executed, but the message is always queued (even if attempt first is enabled). The queue thread is stopped and does not attempt to send.

When a destination connector is stopped, the channel still shows up as Started, but the icon is colored orange instead of green.

Added new task items for startConnector and stopConnector.

Updated popup menu logic to handle stopping individual connectors.

Removed some legacy code in MessageObjectServlet pertaining to temp tables.

Issue: MIRTH-1040