New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index Engine error at startup for OrientDB 2.2.0 #6202
Comments
Hi could you download this link and send me stack trace of exception which you see https://drive.google.com/file/d/0B2oZq2xVp841S2RyaFlCd05PTDg/view?usp=sharing |
Sorry, I did not see your message until today. Here is the exception Jun 01, 2016 7:20:29 PM com.orientechnologies.common.log.OLogManager log Jun 01, 2016 7:20:30 PM com.orientechnologies.common.log.OLogManager log Jun 01, 2016 7:20:30 PM com.orientechnologies.common.log.OLogManager log |
This problem should be resolved in next 2.2.1. In the meanwhile, could you try with latests snapshot? |
Thanks so much for the fix. When will 2.2.1 will be released? Thanks, Tai On Thu, Jun 2, 2016 at 4:57 AM, Roberto Franchini notifications@github.com
|
did you have the chance to try it with OrientDB 2.2.2/3? Thanks |
Enrico, Thanks, Tai
|
Do you have some logs / exception? How do you create edges? Do you use Tx or noTX? |
There is no exception at all. I am using Tx (embedded OrientDB instance) and I also made sure that I called shutdown() method on Graph instance. I also noticed that on the same thread I created these vertices, I could see them. However, from other thread I could not see those vertices at all (I already committed changes, before OrientDB 2.2.x official release, it worked. Other thread could see those vertices). If I shut down my application and restart, then no one could see those newly created vertices at all. Thanks, Tai
|
do you have some code snippet? |
@taihu let me know if you need some help. Thanks |
Enrico, Thanks, Tai On Thu, Jun 30, 2016 at 2:10 PM, Enrico Risa notifications@github.com
|
ok @taihu |
I've same problem since insert data to index column... |
I just upgraded to OrientDB 2.2.0 GA release from OrientDB 2.2.0-beta. Now every time I start my application with embeded OrientDB, I see the error message below
SEVERE: $ANSI{green {db=$graphdb}} Index 'expressible.name' cannot be created and will be removed from configuration
Then immediately follow that I will see a warning
WARNING: $ANSI{green {db=$graphdb}} Index engine with name 'expressible.name' already contained in database configuration
OrientDB seems up and running correctly. However, every time I restart my application, I will see the exact same error and warning. Just wondering what it is and I could get rid of it.
Thanks,
Tai
The text was updated successfully, but these errors were encountered: