Database opened by another process, for non-updating queries
Hi, I saw a case today where a Linux cron job was running non-updating queries while a GUI user on Windows 7 was running non-updating queries on the same database. The GUI operation succeeded, but the Linux cron job reported this error: Database 'DocLibrary' is currently opened by another process. Both processes were using BaseX 8.1. I think it would be difficult for me to provide a short, self-contained example that reproduces this phenomenon reliably. However, I wanted to report it as a data point, if that helps at all. If it is expected behavior due to the mix of platforms and operation modes, that would be useful for me to know. Thanks, Amanda
-----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: Friday, March 13, 2015 7:03 AM To: Amanda Galtman Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Can you prevent database modification via GUI?
Hi Amanda,
[snip]
A related question is whether it is problematic for one user of the GUI to have a database open (or to be actively running a query) while another user of the GUI is trying to run a query on the same database.
As long as all queries are read-only, you will be absolutely fine.
Hope this helps, Christian
Hi Amanda, I just checked our code base, and the reported message (which is caused by pinning files on disk) is only raised by updating operations. However, I probably have too less knowledge on all the OS-dependent implications when files are locked, so it could indeed be that the locking semantics of Linux and Windows system differs, and thus causes conflicts that we cannot control on Java level. Best, Christian On Thu, May 7, 2015 at 3:14 PM, Amanda Galtman <Amanda.Galtman@mathworks.com> wrote:
Hi,
I saw a case today where a Linux cron job was running non-updating queries while a GUI user on Windows 7 was running non-updating queries on the same database. The GUI operation succeeded, but the Linux cron job reported this error:
Database 'DocLibrary' is currently opened by another process.
Both processes were using BaseX 8.1. I think it would be difficult for me to provide a short, self-contained example that reproduces this phenomenon reliably. However, I wanted to report it as a data point, if that helps at all. If it is expected behavior due to the mix of platforms and operation modes, that would be useful for me to know.
Thanks, Amanda
-----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: Friday, March 13, 2015 7:03 AM To: Amanda Galtman Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Can you prevent database modification via GUI?
Hi Amanda,
[snip]
A related question is whether it is problematic for one user of the GUI to have a database open (or to be actively running a query) while another user of the GUI is trying to run a query on the same database.
As long as all queries are read-only, you will be absolutely fine.
Hope this helps, Christian
Thanks for checking, Christian. I will try to keep in mind the possibility of cross-platform effects. Regards, Amanda
-----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: Thursday, May 07, 2015 9:44 AM To: Amanda Galtman Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Database opened by another process, for non- updating queries
Hi Amanda,
I just checked our code base, and the reported message (which is caused by pinning files on disk) is only raised by updating operations. However, I probably have too less knowledge on all the OS-dependent implications when files are locked, so it could indeed be that the locking semantics of Linux and Windows system differs, and thus causes conflicts that we cannot control on Java level.
Best, Christian
On Thu, May 7, 2015 at 3:14 PM, Amanda Galtman <Amanda.Galtman@mathworks.com> wrote:
Hi,
I saw a case today where a Linux cron job was running non-updating queries while a GUI user on Windows 7 was running non-updating queries on the same database. The GUI operation succeeded, but the Linux cron job reported this error:
Database 'DocLibrary' is currently opened by another process.
Both processes were using BaseX 8.1. I think it would be difficult for me to provide a short, self-contained example that reproduces this phenomenon reliably. However, I wanted to report it as a data point, if that helps at all. If it is expected behavior due to the mix of platforms and operation modes, that would be useful for me to know.
Thanks, Amanda
-----Original Message----- From: Christian Grün [mailto:christian.gruen@gmail.com] Sent: Friday, March 13, 2015 7:03 AM To: Amanda Galtman Cc: basex-talk@mailman.uni-konstanz.de Subject: Re: [basex-talk] Can you prevent database modification via GUI?
Hi Amanda,
[snip]
A related question is whether it is problematic for one user of the GUI to have a database open (or to be actively running a query) while another user of the GUI is trying to run a query on the same database.
As long as all queries are read-only, you will be absolutely fine.
Hope this helps, Christian
participants (2)
-
Amanda Galtman -
Christian Grün