ArchivingDataturbine workflow couldn't update the second sensor's lastArchiving time in command line mode
There are two sensors in the dataturbine actor.
When I ran the workflow in command line mode, i found the workflow can't update the second sensor's lastArchiving time. But it can update the first sensor's successfully.
If the same workflow is run under Kepler GUI mode, both sensor's lastArchiving time can be updated successfully.
Updated by Jing Tao almost 12 years ago
This is an issue in HSQL. It has WRITE_DELAY property and its default value is 20 seconds. So the data couldn't be stored before kepler quitted.
I set it up to false and the issue has gone.
See the page: