The First MultiModel DBMS with a true Graph Engine
See all
Members (583)
Luca Garulli's profile photo
이장원's profile photo
Ricardo Memoria's profile photo
zainab noor's profile photo
Georg Köster's profile photo
echinopsii - the open source totem's profile photo
Sunil Nagi's profile photo
Alexander Dederer's profile photo
André Barbosa's profile photo
nishank rajvanshi's profile photo
Francesco Bonavita's profile photo
Gianluca Tessarolo's profile photo
Nacho Rodriguez's profile photo
Federico martinez's profile photo
Muthuselvi Saratha Allimuthu's profile photo
Serega CarpOFF's profile photo
nataLINO Lattanzi's profile photo
János Háber's profile photo
Levente György's profile photo
Avi Levi's profile photo
Salvatore Piccione's profile photo
István Nagy's profile photo
Luca Fornili's profile photo
Daniele Madama's profile photo

Stream

Join this community to post or comment

Luca Garulli

Discussione  - 
 
 
We are looking at driver developers for OrientDB database (http://www.orientdb.com) with good knowledge of at least 2 of the following languages: PHP, Python and C# (.NET platform). The candidate will learn the missing language and will contribute in the long term to the development/support of other drivers, like Golang.
Good knowledge of TCP/IP and HTTP protocols is a big bonus. In short term perspective this developer will analyse existing community drivers, fix existing issues and implement new API together with the OrientDB core team.
Furthermore, the candidate has to stay updated with the new trending frameworks and evaluate what to support as a new connector for OrientDB.
So in nutshell we are looking for developers with the insane passion for the polyglot programming and studying of the next cool framework.
Required english level is upper intermediate.
1
Add a comment...

Luca Garulli

Discussione  - 
2
1
Nicolas Embleton's profile photodaniele montagni's profile photo
 
Beautiful!
Add a comment...

OrientDB

Discussione  - 
5
2
Luca Garulli's profile photoLuca Garulli's profile photo
Add a comment...

OrientDB

Discussione  - 
 
Released #OrientDB Distributed #GraphDB v2.1.10 (25 issues resolved) http://orientdb.com/released-orientdb-2-1-10/ #nosql
London, February 4, 2016 The OrientDB Team has just released OrientDB v2.1.10, resolving 25 issues from v2.1.9. This is the last stable release. Please …
4
Add a comment...

OrientDB

Discussione  - 
 
Polyglot Persistence vs Multi-Model Databases - presented in Data Day (Austin, TX) http://www.slideshare.net/lvca/polyglot-persistence-vs-multimodel-databases #nosql #multimodel
4
3
Carlo Pradissitto's profile photoSantiago Stimper's profile photo
Add a comment...

OrientDB

Discussione  - 
 
Join the Data Revolution: #OrientDB is looking for a Senior Support Engineer http://www.linkedin.com/jobs2/view/90353920 #graphdb #multimodel #nosql
Location: Flexible/ Work from Home Policy OrientDB LTD is looking for experienced Support Engineers who have passion for innovative technology and Open Source, along with the right attitude to help others be successful with daunting OrientDB projects. Technical background in Java is required. Experience supporting and contributing to Open Source projects and NoSQL/OrientDB experience is a strong plus. We offer the unique opportunity to work f...
1
Add a comment...

OrientDB

Discussione  - 
 
Released OrientDB v2.1.6. 38 issues resolved. All known bugs related to the distributed architecture have been resolved with this release. -> http://orientdb.com/released-orientdb-v2-1-6/
London, November 23, 2015 The OrientDB Team has just released OrientDB v2.1.6, resolving 38 issues from v2.1.5. This is the last stable release, please upgrade your …
3
1
Nicolas Embleton's profile photo
 
Can't wait to try it. 
Add a comment...

Florian Neiss

Discussione  - 
 
OrientDB graph: How to use Java API to create a new Record?

#orientdb #db #java #help #javaapi #newrecord #graphdatabase  
I know how to create an Record with the Web GUI of OrientDB. How am I able to create a New Record with the Java API? This is what I have done with the GUI so far. You can download the full version...
3
2
Carlo Pradissitto's profile photoRoberto Franchini's profile photo
Add a comment...
 
Congratulations to all of OrientDB team. Very important to present information about raking in DB-Engines site, informing the rise in popularity of position number 65 to 49. Towards the top positions! http://db-engines.com/en/ranking ... http://db-engines.com/en/system/OrientDB
2
Add a comment...

Thomas Knoell

Discussione  - 
 
Issue with closing database connections in multi-thread environment

We are running in an issue when we close a database connection (db.close) as eventually, the following error is displayed: No more resources available in pool. Requested resource: [db location]. Once in this state, the application is effectively dead and needs to be restarted. If the call to db.close is not made, all is running fine, no error is displayed.

Here are some additional details: There are multiple classes that extend a basic database access layer class (which provides basic functions such as close and open operations). The extensions handle different aspects of the application. Each extension implements autocloseable which will enforce a call to the close interface once the resource is out of scope. A typical (simplified) scenario would be like this:

  try (DatabaseLayerExtensionA dleA = new DatabaseLayerExtensionA()) {

      … do something …

     try (DatabaseLayerExtensionB dleB = new DatabaseLayerExtensionB()) {

      … do something …

     }

      … do something …

  }

The nested calls can be fairly deep depending on the action that is required.

When an instance of a class extending the database access layer is created, a connection to the database is established:

       ODatabaseDocumentTx db = new ODatabaseDocumentTx(m_dataset);
       db.open(m_dbUser, m_dbPw);
       return db;

When the instance is out of scope, the close interface is invoked which executes a db.close operation.

There are multiple threads that each require access to the database. To ensure that the thread does have a reference to the database and not causing an exception (Database instance is not set in current thread), a ODatabaseLocalThreadFactory is defined and registered with the Orient instance. 

In the server configuration file (orientdb-server-config.xml) the max pool size is set to 20. 

That is about all there is as far as the context is concerned. We are using version 1.7.9, Java version 8. Like I mentioned before, if the close is not enforced, all works well. We would like to understand why this is the case. Any feedback is welcome.
1
Luca Garulli's profile photoThomas Knoell's profile photo
6 comments
 
If the database would have been closed prematurely code that processes the fetched data would have failed (wouldn't be able to access the data). So, we are fairly sure that this is not the case since we did not see the corresponding error in our logs. And it is not the close that causes the error, it is when a new connection is established that we see it. Like you said, we would have expected it in case we do not close the database but that is not the case.

We did find an entry on the net talking about an OrientDB connection issue when there are nested database references so we thought that this may be a cause here as well. But that entry was some time ago and may no longer be an issue.
Add a comment...

About this community

document graph NoSQL DBMS

Luca Garulli

Discussione  - 
 
#OrientDB Guide, mini episodes in Italian by Giuseppe Maggi (sorry for the rest of the world). http://www.html.it/guide/guida-orientdb/ #nosql #graphdb
 ·  Translate
1
Add a comment...

Luca Garulli

Discussione  - 
2
Carlo Pradissitto's profile photoLuca Garulli's profile photo
5 comments
 
There is an army behind v2.2 ;-)
Add a comment...

OrientDB

Discussione  - 
 
Released #OrientDB Distributed #GraphDB v2.1.11 (12 issues resolved) http://orientdb.com/released-orientdb-2-1-11/ #nosql #multimodel
London, February 15, 2016 The OrientDB Team has just released OrientDB v2.1.11, resolving 12 issues from v2.1.10. This is the last stable release. Please …
3
1
Luca Garulli's profile photo
Add a comment...

OrientDB

Discussione  - 
 
‪#‎OrientDB‬ Experiences Record Growth in 2015. Momentum Paves Way For Transformative 2016 http://orientdb.com/orientdb-experiences-record-growth/ ‪#‎graphdb‬ ‪#‎nosql‬

OrientDB, The World's Leading Multi-Model Database, experiences Record Growth in 2015. Momentum Paves Way For Transformative 2016
3
1
Luca Garulli's profile photo
Add a comment...

Luca Garulli

Discussione  - 
 
Released #OrientDB v2.1.7 with new Graph Consistency to speed up edge creation: http://orientdb.com/docs/last/Graph-Consistency.html
Edit This Page. Graph Consistency. Before OrientDB v2.1.7 the graph consistency could be assured only by using transactions. The problems on using transactions for simple operations like creation of edges are: speed, the transaction has a cost in comparison to non transactional operations ...
5
4
Carlo Pradissitto's profile photoRoberto Franchini's profile photo
Add a comment...

Thomas Knoell

Discussione  - 
 
Hi,

We recently upgraded OrientDB from version 1.7.9 to 2.1.4 (when this was the most recent version) and changed our project code to use a remote database rather than an embedded one. First tests showed positive results but recent stress-tests produced some unexpected results:

(1) Illegal Argument Exception on queries

This happens fairly frequently - here is the output of such an exception

Nov 30 21:10:23 dsegaz java[30593]: 2015-11-30 21:09:47:225 WARNI ->192.168.1.39: Command not found: GET.sqlProfiler/eyeglass [ONetworkProtocolHttpDb]{db=eg
} Error on using index J.name in query 
'SELECT FROM J 
   LET $L1 = (SELECT og.keys() AS oGs 
                FROM S 
                WHERE sg = 'p1' AND 
                      sk LIKE 'key%' AND 
                      ex_pros.z IN ['VALUE'] AND 
                      og IS NOT NULL 
                GROUP BY og), 
       $L2 = (SELECT og.keys() AS oGs 
                FROM S 
                WHERE sg = 'p2' AND 
                      sk LIKE 'key%' AND 
                      (ex_props.zid IN ['c-d-1'] OR 
                       ('zid' NOT IN ex_pros.keys() AND 'System' IN ['c-d-1'])) AND 
                      og IS NOT NULL
                GROUP BY og) 
   WHERE name IN ($L1) OR name IN ($L2)'. 

Probably you need to rebuild indexes. Now executing query using cluster scan
Nov 30 21:10:23 dsegaz java[30593]: java.lang.IllegalArgumentException: Key '($L1' is not valid
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.operator.OQueryOperatorIn.executeIndexQuery(OQueryOperatorIn.java:81)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLSelect.searchForIndexes(OCommandExecutorSQLSelect.java:1883)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLSelect.searchInClasses(OCommandExecutorSQLSelect.java:873)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLResultsetAbstract.assignTarget(OCommandExecutorSQLResultsetAbstrac
t.java:207)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLSelect.assignTarget(OCommandExecutorSQLSelect.java:474)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLSelect.executeSearch(OCommandExecutorSQLSelect.java:456)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLSelect.execute(OCommandExecutorSQLSelect.java:427)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.sql.OCommandExecutorSQLDelegate.execute(OCommandExecutorSQLDelegate.java:90)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.executeCommand(OAbstractPaginatedStorage.jav
a:1452)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.command(OAbstractPaginatedStorage.java:1433)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.core.command.OCommandRequestTextAbstract.execute(OCommandRequestTextAbstract.java:63)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.server.network.protocol.http.command.post.OServerCommandPostCommand.execute(OServerCommandPost
Command.java:81)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.server.network.protocol.http.ONetworkProtocolHttpAbstract.service(ONetworkProtocolHttpAbstract
.java:180)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.orient.server.network.protocol.http.ONetworkProtocolHttpAbstract.execute(ONetworkProtocolHttpAbstract
.java:627)
Nov 30 21:10:23 dsegaz java[30593]: at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:77)

The query is executable in Studio, no problem there.


(2) Connection Problems 

Infrequently we get messages like this:

Reached maximum number of concurrent connections (max=1000, current=1584), reject incoming connection from ... [OServerNetworkListener]

Not consistently reproducible. We did not see this when using 1.7.9.


(3) Error: Reached maximum pool size for given partition 

Like the issue before, this error is happening infrequently. Not consistently reproducible. Also not seen with 1.7.9.


We found references to all of those issues on the internet but did not find answers that seem to work. If those issues cannot be overcome, we have to rollback to 1.7.9 - which, really, we like to avoid. Any suggestions are welcome.

Thanks
1
Add a comment...

Thomas Knoell

Discussione  - 
 
Error when starting server with version 2.1.4

We upgraded from 2.1.2 to 2.1.4 and now get the following error when starting the server with server.bat:

2015-10-28 15:58:47:854 INFO  Installing dynamic plugin 'orientdb-lucene-2.1.4-d
ist.jar'... [OServerPluginManager]
2015-10-28 15:58:47:906 INFO  Lucene index plugin installed and active. Lucene v
ersion: LUCENE_47 [OLuceneIndexPlugin]Error on installing dynamic plugin 'lucene
-index'
java.lang.IllegalStateException: Plugin 'lucene-index' already registered
        at com.orientechnologies.orient.server.plugin.OServerPluginManager.regis
terPlugin(OServerPluginManager.java:131)
        at com.orientechnologies.orient.server.plugin.OServerPluginManager.insta
llDynamicPlugin(OServerPluginManager.java:363)
        at com.orientechnologies.orient.server.plugin.OServerPluginManager.updat
ePlugin(OServerPluginManager.java:202)
        at com.orientechnologies.orient.server.plugin.OServerPluginManager.updat
ePlugins(OServerPluginManager.java:292)
        at com.orientechnologies.orient.server.plugin.OServerPluginManager.acces
s$000(OServerPluginManager.java:59)
        at com.orientechnologies.orient.server.plugin.OServerPluginManager$1.run
(OServerPluginManager.java:100)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)

The error has no impact on database accessibility for us but is annoying since it is a repetitive message, showing up every few seconds. 
1
Thomas Knoell's profile photoLuca Garulli's profile photo
3 comments
 
Cool.
Add a comment...

Albert Avi Alaluf

Discussione  - 
 
I have class project and I stuck on "Reached maximum number of concurrent connections (1000), reject incoming connection from /10.224.176.11:36168 [OServerNetworkListener]" Any suggestions?
1
Add a comment...