first-time database initialization already-locked file #9984
-
|
Is there a way on an OrientDB server to create a database and initialize it with some classes and instances, the first time the server starts? I have a plugin installed with version 3.2.19 that needs certain things set up. It would be convenient to do this all in one place. I can create the DB (in /OrientDB/databases/) in the plugin in an OServerPlugin.startup override, but there's no listener hook inside which I can then open the created DB; it claims that a file is already locked, so it can't open OSystem. Even OServerLifecycleListener.onAfterActivate sees the conflict. The open() gets the exception: I haven't yet tried spinning off a thread. The stack backtraces look like this: |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 5 replies
-
|
A spun-off thread that runs after the server has become active has the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, yes only one context at time can access the set of databases in a folder, the I hope this help. |
Beta Was this translation helpful? Give feedback.
-
|
I'd tried various combinations with server.getContext before; perhaps I should've stuck with it. This sequence doesn't work: |
Beta Was this translation helpful? Give feedback.
-
|
I can create and initialize the DB as follows, but then when I try connecting in console.sh, it says the DB is locked: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, If you want to use the console to connect to the database opened by the server, you can just use the remote protocol to connect to the database going through the server with the connection url like the |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the workaround. Is it a bug that the created database is left in a locked condition for local connections? I was surprised that there were no users in the created database until I created them. This is contrary to the documentation at https://orientdb.org/docs/3.1.x/security/OrientDB-Security-Guide.html . I suppose this is the reason that I wasn't able to open the created database using user "admin," and had to resort to a no-authorization connection. The roles, however, had been created. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Since 3.2.x we do have a new way to create databases trough a commad, that allow you to specify a set of users and passwords, I think the best way to describe it is trough the test code: https://github.com/orientechnologies/orientdb/blob/develop/core/src/test/java/com/orientechnologies/orient/core/db/OrientDBEmbeddedTests.java#L676 I hope this helps |
Beta Was this translation helpful? Give feedback.
-
|
I might try this later, thanks, although I thought I had to use server.getContext . Shouldn't the call to OrientDB.close on line 687 be redundant? IMHO, OrientDB should be being closed when the session is closed exiting the "try" clause. |
Beta Was this translation helpful? Give feedback.
-
|
The problem with an already-open DB was most likely that I wasn't using try-AutoCloseable for result sets during DB creation. I'm no longer prevented from opening embedded in console.sh . |
Beta Was this translation helpful? Give feedback.
The problem with an already-open DB was most likely that I wasn't using try-AutoCloseable for result sets during DB creation. I'm no longer prevented from opening embedded in console.sh .