I just discovered an issue I consider as a bug in the StorageArea plugin Api
When I return the OrthancPluginErrorCode_StorageAreaPlugin value as result of the StorageRemove() method, the Orthanc service obviously restarts (a new Logfile is created and Orthanc shows the normal starting logs as usual)
The last “pre-mortem” log entry before restarting is the following:
E0412 01:03:11.525202 PluginsManager.cpp:164] Cannot rollback a non-existing transaction
This Error only occurs in the StorageRemove() method, the other methods are working as supposed when returning the OrthancPluginErrorCode_StorageAreaPlugin value.
The StorageRemove function just returns the Error Code:
static OrthancPluginErrorCode StorageRemove(const char* uuid,
OrthancPluginContentType type)
{
return OrthancPluginErrorCode_StorageAreaPlugin;
}
If you try to delete an image / patient via the Orthanc Explorer with the plugin running, Orthanc restarts and delivers the Error Message:
E0412 01:03:11.525202 PluginsManager.cpp:164] Cannot rollback a non-existing transaction
In contrast, the StorageRead and the StorageCreate functions are working as supposed and documented. When I return the Error Code Orthanc continues and just documents an “error in the StorageArea plugin”
