I need to calculate the amount I can buy given the capital and the buying price.
The problem is that the amount need to be modified each row, because the previous revenue has to be added to the initial capital. The before example will become something like this:
Maybe I need to itereate the first dataset or is there a faster way to achieve this?
Hi @AndreaM . Does this issue occur when you use one instance of EasyMorph Desktop only? Could it be that for example there is also EasyMorph Launcher that is simultaneously active and is executing some shared memory-involving task? Or, maybe your repo.sqlite database file is used by both Server and Desktop or maybe you access it using network drive, etc?
PS just to be sure, what EasyMorph version are you using?
We use 126.96.36.199 version.
I closed every instance of EM Desktop and this is the first project where we use Shared Memory actions.
I can confirm that the problem depends on the occupation of the server: while I was testing my project with the Shared Memory actions, another user contacted me that something went wrong with another software that launch “ems-cmd.exe run”: this app run the ems-cmd to generate few PDF, 1 for each call, and yesterday it happened that the number of PDF wasn’t correct (something like 14 PDF instead of 16). I don’t have logs about this app, but after I stopped the Shared Memory test, the PDF generator runned perfectly.
To clarify things, are you performing Shared Memory tests on the Server using a dedicated server Task or are you performing them using EasyMorph Desktop (as the Desktop screenshot implies) while both Server and Desktop use the same data connector repository (the repo.sqlite file), or are you using Desktop with Server Link configured and Shared Connectors set up in ‘Server space’ mode (like in the screenshot below)?
Yes, that’s exactly the scenario to cause a database file lock. EasyMorph uses sqlite file-based ‘database’ that is extremely light-weight and reliable, but unfortunately not suitable for concurrent usage by more than one process at the same time.
If you indeed switch your data connector manager to use Server space (like in the screenshot I’ve posted) this will reorient Desktop to use Server space for shared memory too and eliminate locking issues.
It is highly recommended to avoid such configuration in general, not just for Shared Memory. When a repository is managed by the Server, it resolves potential access conflicts of simultaneous access by Server + Desktop or Desktop + Desktop. It’s also more secure, as the repository file remains on the Server and is not exposed to network users.
So, now you’re not using the file repository in Desktop but nothing changed – you still get the same error? No one else (like, Launcher or maybe another lingering Desktop instance) is using repository in File mode?